From: "Charles Coffing" <ccoffing@novell.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Kevin Tian <kevin.tian@intel.com>,
Yunhong Jiang <yunhong.jiang@intel.com>,
xen-devel@lists.xensource.com,
xen-ia64-devel@lists.xensource.com
Subject: Re: [PATCH] Fix auto-ballooning of dom0 for HVM domains
Date: Mon, 22 May 2006 09:15:49 -0600 [thread overview]
Message-ID: <44718203.D169.003C.0@novell.com> (raw)
In-Reply-To: <6085df031157d9ce198b72191501db21@cl.cam.ac.uk>
>>> On Mon, May 22, 2006 at 9:03 AM, in message
<6085df031157d9ce198b72191501db21@cl.cam.ac.uk>, Keir Fraser
<Keir.Fraser@cl.cam.ac.uk> wrote:
> On 22 May 2006, at 15:51, Charles Coffing wrote:
>
>> HVM domains need some extra memory free for the shadow page tables,
>> otherwise they may crash the entire machine while they are running,
or
>> the HVM domain itself may crash (exact behavior depends on whether
you
>> have Yunhong's patch to change BUGs to domain_crash).
>>
>> This slack space is calculated into the memory size for HVM
domains,
>> but what happens if you then start a PV domain afterwards? Only
the
>> minimally required memory is freed up, then the PV domain takes it
all,
>> leaving the HVM domain with no slack == crash.
>
> Where does the slack from the previous HVM guest startup go? Are you
> saying that dom0 only frees up PV- guest- size minus existing-
slack?
Correct.
Unless, of course, the HVM domain has eaten up some of the slack in the
mean-time, in which case dom0 frees up PV-guest-size minus
remaining-slack.
next prev parent reply other threads:[~2006-05-22 15:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 8:51 [PATCH] Fix auto-ballooning of dom0 for HVM domains Tian, Kevin
2006-05-22 9:06 ` Keir Fraser
2006-05-22 14:51 ` Charles Coffing
2006-05-22 15:03 ` Keir Fraser
2006-05-22 15:15 ` Charles Coffing [this message]
2006-05-22 15:38 ` [Xen-devel] " Keir Fraser
2006-05-22 16:10 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2006-05-22 9:09 Tian, Kevin
2006-05-19 16:29 Jiang, Yunhong
2006-05-19 4:23 Jiang, Yunhong
2006-05-19 15:15 ` Ewan Mellor
2006-05-19 19:59 ` Charles Coffing
2006-05-18 17:04 Charles Coffing
2006-05-18 18:11 ` Charles Coffing
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=44718203.D169.003C.0@novell.com \
--to=ccoffing@novell.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-devel@lists.xensource.com \
--cc=yunhong.jiang@intel.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.