This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] lowest limit for balloon?

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] lowest limit for balloon?
From: aq <aquynh@xxxxxxxxx>
Date: Tue, 19 Jul 2005 00:44:59 +0900
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 18 Jul 2005 15:43:55 +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:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=flhC8P54CezujnHbX5dFhMEQt6ak9suuWLZgwsHnE/Kvp2UfI5Qan4BUCtwZQDuB3NsAZhMsYIPI5maGYERL5JujCvm3myAb3rPoa10PWwkQ7PImWvAkfz6WXzgPdrruTnK8Utm8nF5Pz5EAGoBNxhE6b9S9kdL0kCRPiTvoBTU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <3f5bbf036ea5085e752235233f8760dd@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <9cde8bff05071803571388e532@xxxxxxxxxxxxxx> <3f5bbf036ea5085e752235233f8760dd@xxxxxxxxxxxx>
Reply-to: aq <aquynh@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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 ?


>   -- 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)


Xen-devel mailing list