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


Re: [Xen-devel] QEMU upstreaming: status and todo

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] QEMU upstreaming: status and todo
From: Łukasz Oleś <lukaszoles@xxxxxxxxx>
Date: Wed, 5 Jan 2011 18:46:33 +0100
Cc: Anthony.Perard@xxxxxxxxxx, Kamala Narasimhan <Kamala.Narasimhan@xxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Wed, 05 Jan 2011 09:48:36 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:cc:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=owJIjcS16mz6TocyvNpyTv0YnVtKyzCVvaEJwdJE/vY=; b=qq5yKHfNxEtWAss5ZO+C1JdjsKHFLDbY9iU1UUC2goK51udCSfJw9ANExblBfDstXR zHa/BA+XDKeRF4kPHrKyfMNOjjKoiS4JdKcTtHC2yY+q/HbenSnyBmRAwIMwPvDdi1l3 5Ooj1/ym0cMxvoU0dCOfC8T4Mhowt906No1VE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=eK/MI+OxQ22H/Eah71uJrdzKQRh6GZbyEXceLzS2SGsvVdFUeVhUPByyeuHFi180pT hpNqcEK0Aerf95asMoov/596utqNgtowzJRgqBYpRzD8UH5KwzYVq0yZOUmXZIrXEVG9 Jd45FykpINogIg8moksMnTg5U5lJgetJq+0TI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1101051639130.2390@kaball-desktop>
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: <A153211D67C1374D991D3DF43F03BF629CF778A8B2@xxxxxxxxxxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.1101051639130.2390@kaball-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.13.5 (Linux/2.6.32-5-686; KDE/4.4.5; i686; ; )
On Wednesday 05 January 2011 18:03:15 Stefano Stabellini wrote:
> Hi all,
> I would like to spent few words to let people know the current status of
> the Qemu upstreaming work and what is still missing.
> Anthony Perard sent the 8th version of his "Xen device model support"
> patch series to qemu-devel and he has already received an ack from
> Alexander Graf. We are currently waiting for another review by Anthony
> Liguori but we are positive the series is close to be accepted in its
> current form.
> Once the series is upstream we can start using upstream Qemu to do Xen
> development, however before we can actually use it as default device
> model we need to fill some gaps.
> In fact some things are still missing compared to qemu-xen, the
> followings in particular:
> - VGA dirty bits optimization
> This is a performance optimization for the emulated VGA card, Anthony
> Perard is already working on it.
> - switch to SeaBios
> Qemu uses SeaBios, that has several advantages on RomBios, one of them
> is that SeaBios is actually maintained.
> It makes sense to switch from the old Qemu and the old bios to a new
> Qemu and a new bios at the same time in order to reduce the
> compatibility pains to users.
> - stubdom support
> The "Xen device model support" patch series lacks stubdom support.
> This is mainly a matter of compiling upstream Qemu against MiniOS,
> the problem is that MiniOS is not exactly posix compliant so we'll need
> to make some changes.
> - pci passthrough
> The patch series also lacks pci passthrough support.
> The current pci passthrough code in qemu-xen is rather large and doesn't
> integrate very well with the rest of Qemu so it is non-trivial to
> upstream.
> - QMP support in libxl
> upstream Qemu supports an RPC protocol called QMP that is JSON based.
> We need to be able to use it to issue commands to Qemu, replacing the
> current mechanism based on xenstore. For example this would be needed by
> pci passthrough to send the "plug" and "unplug" commands to Qemu.
> Ideally we'll be able to complete these tasks by the end of the Xen 4.2
> release cycle so that we can have the new Qemu as default device model
> by then.

Great job, it sounds really interesting. 

Is it usable in current state? Can I test it on current xen 4.0.x?

Can You write what are the coolest things in upstream qemu?


Łukasz Oleś

Xen-devel mailing list