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

[Xen-devel] lowest limit for balloon?

  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: aq <aquynh@xxxxxxxxx>
  • Date: Mon, 18 Jul 2005 19:57:33 +0900
  • Delivery-date: Mon, 18 Jul 2005 10:56:10 +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:content-transfer-encoding:content-disposition; b=Xn1Nq7iRfd3C7SqcD65wOUWQLUdJdxWp8Sxi3D47wA9MpefGeUatZq5+S0MjpeJMjjyHYHd7YKGAMahUKAz/Ra0REWWY1XT97PlU/tROiJZSRBXAdBB1N6WW1x6ATetk0Aoukla+fieuflSdDE/JYGhATUyLFJuXVuZ9aTOWORU=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


currently there is one problem with balloon: if we specify too little
memory for a domain, that domain might crash with OOM error. even in
that case, balloon still happily do what we request. i just
accidentally balloon dom0 to 0M, and must reboot the machine ;-)

so i guess it is better to enforce a certain limit, so balloon will
not bring the amount of memory for a domain to be lower than that

there are few choices to do this:
- each domain has a configurable option for this (for example:
balloon-level in domain config file)

- xen automatically determine this level for each domain (but how?)

any idea?


Xen-devel mailing list



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