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


[Xen-users] Re: xm balloon problems

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: xm balloon problems
From: Charles Duffy <cduffy@xxxxxxxxxxx>
Date: Fri, 18 Nov 2005 07:35:01 -0600
Delivery-date: Fri, 18 Nov 2005 13:40:27 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200511181141.32503.e.bachmann@xxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <484a4e240511172256p59ec340ev216179906b3f13b9@xxxxxxxxxxxxxx> <200511181141.32503.e.bachmann@xxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.6 (X11/20050716)
Ernst Bachmann wrote:
Balloon works by having a kernel driver inside the dom allocate a chunk of memory and releasing that chunk back to xen. Ballooning a domain to more memory than it initially had would require the balloon driver to allocate a negative ammount of memory, which simply isn't possible.

I'd think there'd be some way to expose extra memory allocated at runtime, even if it's not exactly an efficient one.

At a minimum, one could expose extra memory through a MTD driver and add it as high-priority swap -- and I'm sure better options are available as well.

Xen-users mailing list

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