Re: [Xen-devel] HVM dynamic physical memory

To:	David Pilger <pilger.david@xxxxxxxxx>
Subject:	Re: [Xen-devel] HVM dynamic physical memory
From:	Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date:	Sun, 31 Dec 2006 13:08:35 +0000
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Sun, 31 Dec 2006 05:08:03 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<280848580612310503i2283c5f7ub13f6697c4387c42@xxxxxxxxxxxxxx>
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	Accs3Mc2BdudqJjQEduBDQANk04WTA==
Thread-topic:	[Xen-devel] HVM dynamic physical memory
User-agent:	Microsoft-Entourage/11.3.2.061213

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.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel