[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] HVM dynamic physical memory

  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
  • From: "David Pilger" <pilger.david@xxxxxxxxx>
  • Date: Sun, 31 Dec 2006 15:26:32 +0200
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sun, 31 Dec 2006 05:26:17 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jmMUYEhmd5h1mIFFhkvUtpvBiZs+v+3tLYvF09lUkb8F05wwG8tO3JcZQi8HGylOYo+vuPOxdOMPq2Uy0A0u5mbDNZ9SPJBS0s5Gx28ujg8+qeJP4cPsCljJIIYffRnLh/rQHbsqOFK7J0DHtZeyqarBod+6fyP09EhZTe0WllM=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 12/31/06, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
On 31/12/06 1:03 pm, "David Pilger" <pilger.david@xxxxxxxxx> wrote:

> On 12/31/06, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
>> All that's missing is the balloon driver itself (but the PV Linux one could
>> be used as a basis), support for using the memory-reservation hypercall from
>> HVM context, and a way to blow away qemu's memory-mapping cache when memory
>> is given back to Xen from the HVM guest.
> If you plan to not modify the HVM, Is there a way to make portions of
> physical memory unusable for a HVM windows from the hypervisor in a
> dynamic way?

In a way that is detectable by the guest OS in a way that causes it to react
in a reasonable way? Unlikely, since there is no equivalent of this on a
native x86 platform.

Pretty conclusive :)

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.