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] problem to balloon memory beyond initial allocation

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] problem to balloon memory beyond initial allocation
From: xuehai zhang <hai@xxxxxxxxxxxxxxx>
Date: Mon, 11 Jul 2005 11:19:57 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 11 Jul 2005 19:29:28 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <a1ce686f79096f507f10d2a4a92e2a55@xxxxxxxxxxxx>
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>
References: <Pine.LNX.4.58.0507100759290.22485@xxxxxxxxxxxxxxxxxxxx> <a1ce686f79096f507f10d2a4a92e2a55@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)

Thanks for your reply.

On 10 Jul 2005, at 14:00, Xuehai Zhang wrote:

My above experiment is not very successful. I will appreciate if you can
point out what I did wrong. Thanks in advance!

maxmem will default to initial allocation to the domain (128MB in this case). The 'mem=' parameter is parsed by the guest -- it does not inform Xen. To do that you would need to add 'maxmem=256' to your config file.

I tried to add "maxmem=256" to the domain's config file, but it is not very helpful. I still can not use "xm balloon vm1 200" to increase the memory to 200MB after "vm1" is booted up.

The lowmem/highmem balloon lines show how big the balloon is in terms of low memory (that is 1:1 mapped by the guest) and high memory (the area that needs to be kmapped by the kernel to access it). 'Hard limit' is the maximum reservation being enforced by Xen. In your case it is probed as 128MB, meaning that your 'xm maxmem' invocation had no effect. Sounds like it is broken. :-)

Thanks again.


Xen-devel mailing list

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