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 1/2] Introduce support for upstream qemu in the x

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 1/2] Introduce support for upstream qemu in the xen-unstable build system
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Wed, 7 Sep 2011 17:54:01 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "keir@xxxxxxx" <keir@xxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Wed, 07 Sep 2011 09:46:35 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1315412504.3180.20.camel@xxxxxxxxxxxxxxxxxxxxxx>
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>
References: <1315406398-8987-1-git-send-email-stefano.stabellini@xxxxxxxxxxxxx> <1315412504.3180.20.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Wed, 7 Sep 2011, Ian Campbell wrote:
> On Wed, 2011-09-07 at 10:39 -0400, stefano.stabellini@xxxxxxxxxxxxx
> wrote:
> > In order to distinguish between upstream qemu and qemu-xen I am
> > introducing a new variable named "QEMU" that only if is equal to
> > "upstream" switches the build system to the new qemu.
> 
> Thanks Stefano, this integrated support is overdue.
> 
> Ultimately though I expect we will need a "both" mode since people will
> want old qemu for compatibility with their existing installed guests and
> new qemu for new ones. The allegation (and I don't really know how true
> it is or if it is pessimism or realism) is that some OSes don't cope
> with having the platform components etc changed under them.

Yes. At that point we'll probably have to always build them both,
including two hvmloader...


> > Users that want to try the new qemu just have to export QEMU=upstream
> > before calling make in the xen-unstable top level directory.
> 
> In xl/libxl we call them "qemu-xen-traditional" and "qemu-xen". Perhaps
> we should mirror that nomenclature here?

I looked at libxl but I thought that QEMU=qemu-xen would be confusing for
users/developers.
Like you said, considering that we already have
device_model_version=qemu-xen in VM config files, maybe we should go for
DEVICE_MODEL=qemu-xen?

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