On 7/18/05, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> 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.
>
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
>
>
> On 18 Jul 2005, at 11:57, aq wrote:
>
> > 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)
>
>
-- 
regards,
aq
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel