All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ewan Mellor <ewan@xensource.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com,
	Hans-Christian Armingeon <johnny@wh-netz.de>
Subject: Re: xm info showing too much free ram
Date: Mon, 3 Apr 2006 18:10:38 +0100	[thread overview]
Message-ID: <20060403171038.GD21335@leeni.uk.xensource.com> (raw)
In-Reply-To: <f39221dc49ae855bd27e0f0b27d00b67@cl.cam.ac.uk>

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.

  reply	other threads:[~2006-04-03 17:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-30 18:43 xm info showing too much free ram Hans-Christian Armingeon
2006-04-03 16:45 ` Keir Fraser
2006-04-03 17:10   ` Ewan Mellor [this message]
2006-04-04 10:44     ` Hans-Christian Armingeon
2006-04-04 12:41       ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060403171038.GD21335@leeni.uk.xensource.com \
    --to=ewan@xensource.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=johnny@wh-netz.de \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.