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] Re: [Xen-changelog] fail domU creation if memory need co

To: "Anthony Liguori" <aliguori@xxxxxxxxxx>
Subject: RE: [Xen-devel] Re: [Xen-changelog] fail domU creation if memory need couldn't be succeed after ballooning out dom0
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Thu, 18 Aug 2005 17:03:36 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 18 Aug 2005 16:01:45 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcWkDNEpjdlZTtisTLCIrPtUJ/mFYQAACA+Q
Thread-topic: [Xen-devel] Re: [Xen-changelog] fail domU creation if memory need couldn't be succeed after ballooning out dom0
> >However, this timeout is different: its something we expect 
> may fail (as
> >opposed to an internal failure of the tools).
> >
> Is it really possible to fail?  I just did:
> echo 42 > /proc/xen/balloon

Right now, its not, but we can't leave it that way.

The balloon driver is supposed to be hooked into the low memory path
(way before oomkiller runs) so that the domain can try requesting more
memory to avoid crashing.
> How about when we fix the balloon driver, we have it write a 
> node in the 
> store that indicates whether the balloon has succeeded or failed and 
> then the tools can simply set a watch and wait for something 
> to happen?

There's not really a concept of the balloon driver failing. It just has
a memory target which its trying to hit, and will potentially fluctuate
around it.

I'm quite happy with the timeout. When we're creating a domain we don't
really care whether the ballon succeeds in hitting its target or not,
just whether there's enough free memory on the domain heap to start the
domain. An entirely different domain could have just exited freeing up

We should rename /proc/xen/balloon to /proc/sys/xen/mem_target (or


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>