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-devel] GPLPV memory ballooning and x32

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] GPLPV memory ballooning and x32
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Sun, 23 May 2010 19:11:02 +1000
Delivery-date: Sun, 23 May 2010 02:11:57 -0700
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acr6V92rFAkNlE8LRFKIrcdQAdP+oA==
Thread-topic: GPLPV memory ballooning and x32
Are there any known reasons why ballooning might not work under Xen
3.1.x for a 32 bit Windows DomU?

I've implemented ballooning in GPLPV and it works under Windows 2008 x32
in my testing, but one user is reporting problems. I don't know much
about the details yet but if it just doesn't work under 3.1.x then
upgrading is the only outcome.

I'm using XENMEM_decrease_reservation to give pages back to xen, and
XENMEM_populate_physmap to fill the 'holes' back in with real memory
when the domU wants to balloon up again.



Xen-devel mailing list