From: Jeremy Fitzhardinge <jeremy@goop.org>
To: bderzhavets@yahoo.com
Cc: xen-devel@lists.xensource.com
Subject: Re: dom0_mem with 2.6.29-rc8
Date: Fri, 20 Mar 2009 12:35:09 -0700 [thread overview]
Message-ID: <49C3EFED.7050002@goop.org> (raw)
In-Reply-To: <230226.65275.qm@web56101.mail.re3.yahoo.com>
Boris Derzhavets wrote:
> System loaded with grub entry:-
>
> title Xen 3.4 / Ubuntu 8.10, kernel 2.6.29-tip
> uuid 9efba9a5-9f2b-4bf6-b8b5-7d6d53eb02d9
> kernel /boot/xen-3.4.gz
> module /boot/vmlinuz-2.6.29-rc8-tip root=/dev/sdb14 ro console=tty0
> module /boot/initrd-2.6.29-rc8-tip.img
>
> seems to allocate required amount of memory for DomUs with no problems.
>
Yes. Originally dom0_mem was needed to make sure that the dom0 memory
didn't overlap the pci window in the physical address space, but that's
no longer needed. Ballooning takes care of shrinking dom0 to make space
for domUs (though in a dedicated Xen system, starting dom0 with a
limited amount of memory to leave a well-defined amount of space for domUs.
J
next prev parent reply other threads:[~2009-03-20 19:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 17:58 2.6.29-rc7 pv_ops dom0 BUG / unable to handle kernel paging request Pasi Kärkkäinen
2009-03-08 6:09 ` Jeremy Fitzhardinge
2009-03-08 11:54 ` Pasi Kärkkäinen
2009-03-11 20:52 ` Pasi Kärkkäinen
2009-03-11 21:26 ` Pasi Kärkkäinen
2009-03-11 23:40 ` Jeremy Fitzhardinge
2009-03-12 8:32 ` Pasi Kärkkäinen
2009-03-20 18:10 ` Jeremy Fitzhardinge
2009-03-20 19:04 ` dom0_mem with 2.6.29-rc8 Boris Derzhavets
2009-03-20 19:35 ` Jeremy Fitzhardinge [this message]
2009-03-21 20:16 ` 2.6.29-rc7 pv_ops dom0 BUG / unable to handle kernel paging request Pasi Kärkkäinen
2009-03-21 22:50 ` Pasi Kärkkäinen
2009-03-21 23:13 ` 2.6.29-rc8 " Pasi Kärkkäinen
2009-03-22 4:28 ` Jeremy Fitzhardinge
2009-03-22 11:51 ` Pasi Kärkkäinen
2009-03-22 17:04 ` Pasi Kärkkäinen
2009-03-22 20:40 ` Pasi Kärkkäinen
2009-03-22 21:21 ` Jeremy Fitzhardinge
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=49C3EFED.7050002@goop.org \
--to=jeremy@goop.org \
--cc=bderzhavets@yahoo.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.