From: "James Harper" <james.harper@bendigoit.com.au>
To: "Daniel Kiper" <dkiper@net-space.pl>
Cc: "Andi Kleen" <andi@firstfloor.org>, <jeremy@goop.org>,
<xen-devel@lists.xensource.com>, <linux-kernel@vger.kernel.org>
Subject: RE: [Xen-devel] Re: GSoC 2010 - Migration from memory ballooning tomemory hotplug in Xen
Date: Sat, 10 Jul 2010 15:17:57 +1000 [thread overview]
Message-ID: <AEC6C66638C05B468B556EA548C1A77D01A0A5F4@trantor> (raw)
In-Reply-To: <20100709173455.GD8696@router-fw-old.local.net-space.pl>
>
> On Fri, Jul 09, 2010 at 08:58:01AM +1000, James Harper wrote:
> > > While you can do that the value is not very large because you
> > > could just start the guests with more memory, but ballooned in
> > > the first place (so that they don't actually use it)
> >
> > I think hotplug is a better method for adding memory for Windows.
>
> Maybe in the future I write somthing for Windows...
>
For Windows, I believe you would need to emulate actual hotplug of
memory like a physical machine, using ACPI. It's only supported on
Enterprise versions of Windows too.
James
next prev parent reply other threads:[~2010-07-10 5:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 19:45 GSoC 2010 - Migration from memory ballooning to memory " Daniel Kiper
2010-07-08 22:32 ` Andi Kleen
2010-07-08 22:58 ` [Xen-devel] Re: GSoC 2010 - Migration from memory ballooning tomemory " James Harper
2010-07-09 17:34 ` Daniel Kiper
2010-07-10 5:17 ` James Harper [this message]
2010-07-10 12:36 ` Daniel Kiper
2010-07-08 23:12 ` [Xen-devel] Re: GSoC 2010 - Migration from memory ballooning to memory " Dan Magenheimer
2010-07-09 15:53 ` Daniel Kiper
2010-07-08 23:51 ` Jeremy Fitzhardinge
2010-07-09 0:34 ` Andi Kleen
2010-07-09 17:32 ` Daniel Kiper
2010-07-08 23:16 ` [Xen-devel] " Jeremy Fitzhardinge
2010-07-09 17:11 ` Daniel Kiper
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=AEC6C66638C05B468B556EA548C1A77D01A0A5F4@trantor \
--to=james.harper@bendigoit.com.au \
--cc=andi@firstfloor.org \
--cc=dkiper@net-space.pl \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®