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

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Pasi Kärkkäinen <pasik@xxxxxx>
Subject: RE: [Xen-devel] GPLPV memory ballooning and x32
From: Aravindh Puthiyaparambil <aravindh@xxxxxxxxxx>
Date: Tue, 25 May 2010 14:27:32 -0700
Accept-language: en-US
Acceptlanguage: en-US
Cc: James Harper <james.harper@xxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 25 May 2010 14:28:36 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=january; d=gogrid.com; h=Received:Received:From:To:CC:Date:Subject:Thread-Topic:Thread-Index:Message-ID:References:In-Reply-To:Accept-Language:Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage:Content-Type:Content-Transfer-Encoding:MIME-Version; b=FEzNmoYjAX1r9cPsjcj79XJCPNwEpSHBtUeWlILp8q3sACHh3v3JigM6mRnZ4jFLAS3NS+cATctOTH6Zrl1PwQyjaM7HIY4QYzngiGwmD1tFkuUKOGJTg9IBpBOdr9Ok;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C8213256.150CE%keir.fraser@xxxxxxxxxxxxx>
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>
References: <D83C13F0C853364EB226DBEE584BBE614DAB25F830@xxxxxxxxxxxxxxxxxxxxxxxxxx> <C8213256.150CE%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acr7Eln9C5XzuBeXS+KSV/Yrq0icfAAdxdPgABNdRaMAHl3M4A==
Thread-topic: [Xen-devel] GPLPV memory ballooning and x32
> > Any idea why this is occurring?
> Perhaps a bug in populate-on-demand, which I guess is what gets enabled
> when
> you specify maxmem parameter for an HVM domain. It gets allocated its
> basic
> memory parameter initially, and extra memory gets allocated when the
> guest first writes to it, up to maxmem limit. Or that's the intent
> anyway.
> This is not a regression from 3.1 presumably (3.1 does not implement
> populate-on-demand at all)?

No, this is not a regression from 3.1. With 3.1 the domHVM would come up but 
you would only be able to balloon up and down between N and what was specified 
in the memory option. The maxmem option had no effect. However, as you pointed 
out ballooning was only kind of working with 3.1.

Is there a work around for this issue in 3.4.2?


Xen-devel mailing list