[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:03:04 +0200
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sun, 31 Dec 2006 05:02:52 -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=csW/v/lsZkOyFKXehfjBiqSAcrjWbT/vcJ79owIjehYB8cMStdvvFOyFORGzlGRfPw6HJUryG+MP6522N8EErd4rf5ohrjvtH0aae3i5QIDakydbEuTjSuhpMyyH1/bV1K1pFP2UeWhGlNoXuHXxvOsIU1X1t9YUCaSr9MVNnxU=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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?


Xen-devel mailing list



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