WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0 of 4] videoram allocation and stdvga improvements
From: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>
Date: Wed, 14 Jan 2009 23:19:47 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 14 Jan 2009 14:20:20 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <496E3656.7000206@xxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
References: <496C866B.1010307@xxxxxxxxxxxxx> <20090113140108.GH5033@xxxxxxxxxxxxxxxxxxxxxxx> <20090113143136.GI5033@xxxxxxxxxxxxxxxxxxxxxxx> <496E3656.7000206@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.12-2006-07-14
Stefano Stabellini, le Wed 14 Jan 2009 19:00:38 +0000, a écrit :
> Samuel Thibault wrote:
> 
> > Samuel Thibault, le Tue 13 Jan 2009 15:01:08 +0100, a écrit :
> >> Stefano Stabellini, le Tue 13 Jan 2009 12:17:47 +0000, a écrit :
> >>> In order to simplify the codepath and the libxc API, this patch series
> >>> removes the videoram allocation code from hvmloader and lets qemu do the
> >>> job, using xc_domain_memory_populate_physmap.
> >> 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.
> > 
> 
> The current design of the autoballoner is limited, as a consequence the
> autoballoner is racy and it should not be used at all if the user plans
> to start multiple domains at the same time.

The problem is that with stubdomain-based qemu you _always_ start
multiple domains at the same time.

Samuel

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