From mboxrd@z Thu Jan 1 00:00:00 1970 From: aq Subject: Re: lowest limit for balloon? Date: Tue, 19 Jul 2005 00:44:59 +0900 Message-ID: <9cde8bff05071808441a5f2907@mail.gmail.com> References: <9cde8bff05071803571388e532@mail.gmail.com> <3f5bbf036ea5085e752235233f8760dd@cl.cam.ac.uk> Reply-To: aq Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <3f5bbf036ea5085e752235233f8760dd@cl.cam.ac.uk> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On 7/18/05, Keir Fraser wrote: > It's probably a job for higher-level management tools. Maybe a safety > catch should be placed on 'xm balloon', but the intra-VM > /proc/xen/balloon interface is definitely not intended for the casual > user. >=20 fine, but how about the balloon level to set the limit? i prefer to calculate it based on the domain configuration, instead of specifying it in the domain config file. but that is probably a tough job. do you have any idea on how to determine the limit ? regards, aq > -- Keir >=20 >=20 > On 18 Jul 2005, at 11:57, aq wrote: >=20 > > urrently 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 > > level. > > > > there are few choices to do this: > > - each domain has a configurable option for this (for example: > > balloon-level in domain config file) >=20 >=20 --=20 regards, aq