From: Keir Fraser Subject: Re: [PATCH 0 of 4] videoram allocation and stdvga improvements Date: Tue, 13 Jan 2009 14:45:42 +0000 Message-ID: References: <20090113143136.GI5033@const.bordeaux.inria.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090113143136.GI5033@const.bordeaux.inria.fr> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Samuel Thibault , Stefano Stabellini , xen-devel List-Id: xen-devel@lists.xenproject.org On 13/01/2009 14:31, "Samuel Thibault" 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