From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel <qemu-devel@nongnu.org>,
xen-devel@lists.xensource.com, Gerd Hoffmann <kraxel@redhat.com>,
Laurent Vivier <Laurent@vivier.eu>
Subject: Re: [Qemu-devel] [PATCH 00/10] xen: pv domain support.
Date: Sun, 05 Apr 2009 15:33:43 +0300 [thread overview]
Message-ID: <49D8A527.3080204@redhat.com> (raw)
In-Reply-To: <B05BB230-B60E-4B54-BE92-D918600E820A@suse.de>
Alexander Graf wrote:
>>>
>>> 1) Migration path. If you could already use KVM on a Xen host, you
>>> could have Xen PV guests and KVM guests in parallel, easing
>>> migration to KVM for customers.
>>
>> I like this, of course, but we have a path through Xenner. Maybe
>> this (kvm-on-xen) path will be easier to take.
>
> Oh, I thought Xenner was semi on hold? Is it still actively developed?
> I thought Gerd's main goal for now was to get qemu-dm into upstream
> qemu for now.
I understood that Xenner is the next thing on the list.
>> With npt/ept pv performance might be higher running under kvm+xenner
>> than with software-only Xen by letting the guest kernel access
>> pagetables directly. Though Gerd had some issues with 64-bit guests
>> IIRC, which is a pity since it's there that the pv performance hit is
>> greatest.
>
> Well that might be true, but I'm not fully convinced yet :-). Either
> way with "current" hardware (pre-Nehalem, pre-Barcelona) PV is still
> faster.
Right, but every day this is becoming less important.
> Also, FWIW IO performance on PV Xen is still way superior to KVM.
> Please correct me if I stand wrong there.
We still have some work some work to do on virtio, but bandwidth should
be comparable. And it has nothing to do with pv-vs-fv.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-04-05 12:33 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 21:39 [Qemu-devel] [PATCH 00/10] xen: pv domain support Gerd Hoffmann
2009-04-01 21:39 ` [Qemu-devel] [PATCH 01/10] xen: groundwork for xen support Gerd Hoffmann
2009-04-02 16:37 ` Blue Swirl
2009-04-03 19:58 ` Gerd Hoffmann
2009-04-01 21:39 ` [Qemu-devel] [PATCH 02/10] xen: backend driver core Gerd Hoffmann
2009-04-02 16:49 ` Blue Swirl
2009-04-03 19:59 ` Gerd Hoffmann
2009-04-01 21:39 ` [Qemu-devel] [PATCH 03/10] xen: add console backend driver Gerd Hoffmann
2009-04-01 21:39 ` [Qemu-devel] [PATCH 04/10] xen: add framebuffer " Gerd Hoffmann
2009-04-02 16:57 ` Blue Swirl
2009-04-01 21:39 ` [Qemu-devel] [PATCH 05/10] xen: add block device " Gerd Hoffmann
2009-04-02 17:02 ` Christoph Hellwig
2009-04-03 20:11 ` Gerd Hoffmann
2009-04-05 13:49 ` Anthony Liguori
2009-04-06 12:38 ` Christoph Hellwig
2009-04-07 10:22 ` Gerd Hoffmann
2009-04-07 15:51 ` Christoph Hellwig
2009-04-01 21:39 ` [Qemu-devel] [PATCH 06/10] xen: add net " Gerd Hoffmann
2009-04-01 21:39 ` [Qemu-devel] [PATCH 07/10] xen: blk & nic configuration via cmd line Gerd Hoffmann
2009-04-01 21:39 ` [Qemu-devel] [PATCH 08/10] xen: pv domain builder Gerd Hoffmann
2009-04-02 17:06 ` Blue Swirl
2009-04-01 21:39 ` [Qemu-devel] [PATCH 09/10] simplify vga selection Gerd Hoffmann
2009-04-01 21:39 ` [Qemu-devel] [PATCH 10/10] xen: add -vga xenfb option, configure xenfb Gerd Hoffmann
2009-04-01 23:41 ` [Qemu-devel] [PATCH 00/10] xen: pv domain support Anthony Liguori
2009-04-02 15:32 ` Ian Jackson
2009-04-02 21:14 ` Laurent Vivier
2009-04-03 20:24 ` Gerd Hoffmann
2009-04-03 23:04 ` Alexander Graf
2009-04-05 8:48 ` Avi Kivity
2009-04-05 11:17 ` Alexander Graf
2009-04-05 11:37 ` Avi Kivity
2009-04-05 12:10 ` Alexander Graf
2009-04-05 12:33 ` Avi Kivity [this message]
2009-04-06 7:39 ` Gerd Hoffmann
2009-04-06 13:56 ` [Xen-devel] " Stefano Stabellini
2009-04-06 7:10 ` Gerd Hoffmann
2009-04-06 6:53 ` Gerd Hoffmann
2009-04-06 20:44 ` [Xen-devel] " Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2009-04-07 14:44 Gerd Hoffmann
2009-04-07 17:30 ` Blue Swirl
2009-04-08 14:08 ` Gerd Hoffmann
2009-04-21 12:19 Gerd Hoffmann
2009-04-22 15:52 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49D8A527.3080204@redhat.com \
--to=avi@redhat.com \
--cc=Laurent@vivier.eu \
--cc=agraf@suse.de \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).