From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ewan Mellor Subject: Re: xm info showing too much free ram Date: Mon, 3 Apr 2006 18:10:38 +0100 Message-ID: <20060403171038.GD21335@leeni.uk.xensource.com> References: <200603302043.06923.johnny@wh-netz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com, Hans-Christian Armingeon List-Id: xen-devel@lists.xenproject.org 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. Ewan.