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] xm info showing too much free ram

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] xm info showing too much free ram
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Mon, 3 Apr 2006 18:10:38 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Hans-Christian Armingeon <johnny@xxxxxxxxxx>
Delivery-date: Mon, 03 Apr 2006 10:10:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <f39221dc49ae855bd27e0f0b27d00b67@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: <200603302043.06923.johnny@xxxxxxxxxx> <f39221dc49ae855bd27e0f0b27d00b67@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Apr 03, 2006 at 05:45:07PM +0100, Keir Fraser wrote:

> On 30 Mar 2006, at 19:43, Hans-Christian Armingeon wrote:
> >My dom0 has 2g ram allocated, and I have 2.5 G Ram physically in my 
> >machine.
> >I needed more Ram in domU so I did a
> If you don't start your domU with a 'mem=2G' or similar as a boot 
> parameter then the domU will be unable to increase its memory 
> allocation beyond its initial boot-time allocation. In this case, 'xm 
> list' is lying to you -- it tells you what memory target the tools has 
> asked the domU to aim for, not what the domU is currently using. :-)
> That's my guess anyway -- the free memory reported by 'xm info' is 
> definitely the truth, so 'xm list' is lying and that's probably the 
> reason why. Take a look in the domU and see what it thinks. Also in the 
> domU, look at the contents of /proc/xen/balloon.

Yes, that's right -- xm list shows the configured or requested memory, not the
amount it's actually using.  Personally, I'd consider that a bug -- feel free
to file it.


Xen-devel mailing list

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