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] question on balloon driver

To: "Josh Triplett" <josht@xxxxxxxxxx>, "Mark Williamson" <mark.williamson@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] question on balloon driver
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Thu, 4 Aug 2005 23:21:38 +0100
Cc: Jonas Appel <jonas.appel@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 04 Aug 2005 22:20:08 +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: AcWZQHg3vXcvzAhiR2aqt6o6fHjiMgAAY2nQ
Thread-topic: [Xen-devel] question on balloon driver
> At least on my machine, with current unstable, I cannot 
> create more than 140 *completely empty* domains (just 
> created, no resources assigned); attempting to create more at 
> that point gives an out-of-memory error (which I believe is 
> referring to the Xen hypervisor kernel memory).
> Perhaps there is some switch I haven't seen which allows 
> increasing the amount of memory allocated to the Xen kernel?  
> It would also be nice if domains had far less overhead until 
> resources were allocated to them.

Sounds like you're running out of Xen heap, which is currently
statically sized.
Each domain 'shell' allocates something like 64KB of storage.

I'm not sure we'll get around to changing this anytime soon on, at least
on x86_32. On x86_64 there's no need for there to be a distinction
between domain and xen heap pages, hence the xen heap can be dynamically
sized (at least in the bottom 4GB)


Xen-devel mailing list

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