Re: [Xen-devel] [PATCH 0 of 4] videoram allocation and stdvga improvements

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

On 13/01/2009 14:31, "Samuel Thibault" <samuel.thibault@xxxxxxxxxxxx> wrote:

>> That's what it was doing before I made hvmloader do it.  The reason was
>> to make save/restore work fine with stubdomains dirty log, etc.
> 
> Ah, now I remember the precise reason, written in the 18383 changelog:
> 
> When creating an HVM domain, if e.g. another domain is created before
> qemu allocates video memory, the extra 8MB memory ballooning is not
> available any more, because it got consumed by the other domain.

That explains why HVM guests were starting up with an 8MB memory overhead
and yet were allocating video memory out of their ordinary RAM allocation.
:-)

Hmmm then perhaps it makes sense to have hvmloader continue to allocate the
framebuffer. It can attempt to allocate fresh memory, and it can fall back
to relocating ordinary RAM pages if allocations fail (hvmloader has the
capability to relocate pseudophys pages now!).

I'll talk to Stefano some more about it....

 Thanks,
 Keir



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