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

Re: [Xen-devel] Is: PVH - how to solve maxmem != memory scenario? Was:Re: [PATCH] libxl: create PVH guests with max memory assigned

At 16:05 +0100 on 05 Aug (1407251128), David Vrabel wrote:
> The first is the PV-like approach.
>   The toolstack shall construct an e820 memory map including all
>   appropriate holes for MMIO regions.  This memory map will be well
>   ordered, no regions shall overlap and all regions shall begin and end
>   on page boundaries.
>   The toolstack shall issue a XENMEM_set_memory_map hypercall for this
>   memory map.
>   The toolstack shall issue a XENMEM_set_maximum_reservation hypercall.
>   Xen (or toolstack via populate_physmap? I can't remember) shall
>   populate the guest's p2m using the provided e820 map.  Frames shall
>   be added starting from the first E820_RAM region, fully
>   populating each RAM region before moving onto the next, until the
>   initial number of pages is reached.

This, please.  The tools should tell the guest what memory it has and
the guest should use that memory.  There's _far_ too much messing
about in PVH memory allocation as it is.


Xen-devel mailing list



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