[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH] enforce dom0 cpus and balloon out memory

  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
  • From: aq <aquynh@xxxxxxxxx>
  • Date: Fri, 29 Jul 2005 12:04:27 +0900
  • Delivery-date: Fri, 29 Jul 2005 03:02:58 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=kI+TGpVVRfzEm7240y8FG64wJKq+07OIAYuMf/DsAVj5FKXpdhYiFm/izxBqspDrdhyZgaDTIrDArSgm02g1P5/QREA7Q7AGp8vBap1PSYQA2Mm/kE6a6ehQpjfQSkF3j7daOXTnvJTjnYyPVQUjAo3QE+3kY5B0mESuj91bFB0=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

This patch does 2 jobs:

- Enforce the number of CPUs dom0 will take. See the new variable
"dom0-cpus" in xend-config.sxp (you will want to set this variable to
1 on SMP systems)

- Balloon out dom0 memory when creating domU, if there is not enough
free memory. The lowest level we will balloon out is configured via
the new variable "dom0-min-mem" in xend-config.sxp

I still have a doubt: where to put the code to enforce dom0-cpus. At
the moment I put it into
python/xen/xend/server/SrvDaemon.py, and hopefully that is resonable
enough. Any comment?

Signed-off-by: Nguyen Anh Quynh <aquynh@xxxxxxxxx>

$ diffstat enforce_resource.patch 
 examples/xend-config.sxp            |    8 +++++++
 python/xen/xend/XendRoot.py         |   10 +++++++++
 python/xen/xend/server/SrvDaemon.py |   30 +++++++++++++++++++++++++++-
 python/xen/xm/create.py             |   38 ++++++++++++++++++++++++++++++++++++
 4 files changed, 85 insertions(+), 1 deletion(-)

Attachment: enforce_resource.patch
Description: Binary data

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.