From: Vasiliy G Tolstov <v.tolstov@selfip.ru>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com, Jan Beulich <JBeulich@novell.com>
Subject: Re: memory size inside domU less than memory in domU config
Date: Mon, 20 Jun 2011 18:55:04 +0400 [thread overview]
Message-ID: <1308581704.13237.9.camel@vase> (raw)
In-Reply-To: <20110620143611.GA15251@dumpdata.com>
On Mon, 2011-06-20 at 10:36 -0400, Konrad Rzeszutek Wilk wrote:
> So I tried the same experiment - a physical machine with 'mem=1G' provided
> and an PV guest with 'mem=1G'. The same exact kernel in both cases and got:
>
> Machine with 'mem=1G' on the command line.
> [ 0.000000] Memory: 1022756k/1048576k available (5851k kernel code, 452k absent, 25368k reserved, 2881k data, 688k init)
>
> PV guest:
> [ 0.000000] Memory: 1018888k/1048576k available (5851k kernel code, 448k absent, 29240k reserved, 2881k data, 688k init)
>
> So a DomU guest "eats" an extra 4MB compared to running it under baremetal.
> (Note, the DomU guest has no balloon space in this example).
>
> The memblock=debug does provide the info of what the "other" reserved regions are
> and it looks to be the matter of just going through the numbers to figure out what
> it is.
>
Can You provide pv kernel cmdline and config file ?
--
Vasiliy G Tolstov <v.tolstov@selfip.ru>
Selfip.Ru
next prev parent reply other threads:[~2011-06-20 14:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 18:19 memory size inside domU less than memory in domU config Vasiliy G Tolstov
2011-06-16 18:40 ` Konrad Rzeszutek Wilk
2011-06-16 18:45 ` Vasiliy G Tolstov
2011-06-16 19:12 ` Dan Magenheimer
2011-06-16 19:18 ` Vasiliy G Tolstov
2011-06-16 19:25 ` Konrad Rzeszutek Wilk
2011-06-16 21:32 ` Vasiliy G Tolstov
2011-06-17 9:51 ` Jan Beulich
2011-06-17 10:03 ` Vasiliy G Tolstov
2011-06-20 14:36 ` Konrad Rzeszutek Wilk
2011-06-20 14:55 ` Vasiliy G Tolstov [this message]
2011-06-20 15:07 ` Konrad Rzeszutek Wilk
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=1308581704.13237.9.camel@vase \
--to=v.tolstov@selfip.ru \
--cc=JBeulich@novell.com \
--cc=konrad.wilk@oracle.com \
--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.