From: Vladimir Zidar <mr_w@mindnever.org>
To: xen-devel@lists.xensource.com
Subject: Re: hypervisor memory usage
Date: Wed, 28 Oct 2009 10:53:51 +0100 [thread overview]
Message-ID: <4AE814AF.3020800@mindnever.org> (raw)
In-Reply-To: <20091028094543.GX1434@reaktio.net>
What bothers me with this issue is that memory is 'lost' just after
boot, without any of domUs running.
Also, 8kb per 1MB would add up to 64MB per 8GB of ram, then I add 1
more MB for dom0 (when counted as guest).
Global hypervisor memory, that is question now, can it use 384MB
straight after boot? - memory loss is detected at very first lines of
dom0 dmesg.
Is there a way to show more xen debugging before dom0 kicks in?
Pasi Kärkkäinen wrote:
> On Wed, Oct 28, 2009 at 10:29:37AM +0100, Vladimir Zidar wrote:
>
>> Hi,
>>
>> ** I sent this mail originally to xen-users, but after seeing other
>> subjects posted on that list I felt that it was kind of wrong place to
>> ask **
>>
>>
>> I'm wondering why hypervisor itself uses so much memory? Is it normal?
>>
>> I have several servers with 8GB of ram, all of them running x86_64
>> centos 5.4 (latest) and when running under xen, dom0 has
>> [root@palmae ~]# head -4 /proc/meminfo
>> MemTotal: 7661568 kB
>> MemFree: 6550044 kB
>> Buffers: 37400 kB
>> Cached: 303480 kB
>>
>> Which is 440MB less than what I get without xen.
>> It comes down to what amount of memory kernel gets either from Xen or
>> from BIOS. Please note the differences:
>>
>>
>
> First of all you should limit the amount of memory visible to dom0 by
> specifying dom0_mem=512M (or so) parameter for xen.gz in grub.conf.
>
> After that reboot and then you can check the Xen hypervisor free memory with
> "xm info" and list the guest/domain mem usage with "xm list".
>
> Xen has some memory overhead (just like every virtualization solution).
>
> I think the formula for Xen memory overhead is: 8kB per 1MB of guest
> memory, plus 1MB per guest virtual cpu.
>
> I think this also applies to dom0, since basicly it is just a guest
> (with some more privileges).
>
> And in addition of course there is the "global" hypervisor memory
> usage.. not sure if those will add up to 440 MB though.
>
> -- Pasi
>
>
next prev parent reply other threads:[~2009-10-28 9:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 9:29 hypervisor memory usage Vladimir Zidar
2009-10-28 9:45 ` Pasi Kärkkäinen
2009-10-28 9:53 ` Vladimir Zidar [this message]
2009-10-28 10:40 ` Keir Fraser
2009-10-28 11:19 ` Vladimir Zidar
2009-10-28 11:58 ` Pasi Kärkkäinen
2009-10-28 12:02 ` Vladimir Zidar
2009-10-28 13:12 ` Pasi Kärkkäinen
2009-10-28 13:18 ` Chris Lalancette
2009-10-28 14:13 ` Vladimir Zidar
2009-10-29 11:07 ` Vladimir Zidar
2009-10-29 11:19 ` Vladimir Zidar
2009-10-29 12:05 ` 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=4AE814AF.3020800@mindnever.org \
--to=mr_w@mindnever.org \
--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.