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/
Home Products Support Community News


[Xen-devel] Re: [Qemu-devel] [PATCH 0/7] merge some xen bits into qemu

To: Anthony Liguori <anthony@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [Qemu-devel] [PATCH 0/7] merge some xen bits into qemu
From: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Date: Tue, 05 Aug 2008 11:58:55 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, qemu-devel@xxxxxxxxxx, Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>
Delivery-date: Tue, 05 Aug 2008 02:59:40 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48973F8E.8080109@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>
References: <1217865045-10722-1-git-send-email-kraxel@xxxxxxxxxx> <48973F8E.8080109@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20080501)
Anthony Liguori wrote:
> However, I'd like to see agreement within the Xen community that this
>  is the right approach first.  In particular, I would like to see 
> these patches either merged with upstream Xen or for upstream Xen to 
> plan to rebase against QEMU to pick them up and use them for PV 
> support.

Ian Jackson has a qemu git tree at

As far I know it is rebased now and then and the long-term plan is to
get the delta to upstream qemu at least smaller.  Dunno whenever it ever
will be zero due to stuff like mapcache.

There are a few compatibility issues to be solved somehow before
upstream qemu is able to completely replace xen's qemu-dm:

(1) my patches use -domid to specify the domain id.  xen uses (used?) -d
instead.  Which isn't going to work because upstream qemu uses that
switch for something else.  Ian's tree supports both -d and -domid, with
a comment saying -d is deprecated.  So I think we have an agreement to
use -domid here ;)

(2) xen added a -domain-name switch.  upstream qemu has a -name switch.
my patches do not implement -domain-name, I use the name set via -name
instead.  IMHO xen should pick up the upstream way to do things here,
i.e. switch over to -name.

(3) vnc configuration is different.  This one is not so easy due to
xenstore being involved.  So the way things work are pretty xen specific
and don't make that much sense for upstream qemu.  The differences are:

Setting the vnc password:  qemu uses a monitor command.  xen reads it
from xenstore (set by xend).  I think we can just support both ways here.

xen has a -vncunused switch which makes qemu scan for a free vnc
display.  The tcp port actually used is written to xenstore.  Dunno how
to handle that one best.  First, I think should be a -vnc switch option
instead of a separate command line switch.  Second, propagating the used
port via xenstore doesn't make sense at all for upstream qemu ...



Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>