qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 14:37:49 +0300	[thread overview]
Message-ID: <49D8980D.1070000@redhat.com> (raw)
In-Reply-To: <803692EA-B562-4D41-A809-7EF552180B8F@suse.de>

Alexander Graf wrote:
>
> On 05.04.2009, at 10:48, Avi Kivity wrote:
>
>> Alexander Graf wrote:
>>>
>>> One idea I had for full virtualization in a Xen environment would be 
>>> an PV vmenter/vmexit framework - either by implementing a completely 
>>> new abstraction or simple traps for privileged operations like VMRUN.
>>>
>>> That way we could have a kvm that talks to xen for the VM, rendering 
>>> kvm useful on Xen dom0s, giving people the best of both worlds.
>>>
>>> That was only one of the ideas that came up while talking to people 
>>> why running kvm on xen isn't as easy as just recompiling :-). Would 
>>> you think of such a thing as useful?
>>>
>>>
>>
>> Why would anyone want to do that?  If you've got Xen running, just 
>> start up a Xen guest.
>
> I'm not saying it's a great idea - that's why I didn't even consider 
> to develop it yet :-).
>
> Basically it would solve two problems:
>
> 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.

>
> 2) Alternative to HVM. That's how this came up from Gerd's mail. We do 
> have KVM support in upstream qemu, but we don't have Xen HVM support. 
> That way you could use the same binary for all your needs. Admittedly, 
> it might make more sense to just implement HVM support :-).

I was under the impression that this is underway.

>
> Again, I just like talking to others about random ideas I have and 
> this was one. I don't think it's worth it - IMHO it'd be more useful 
> to create an in-kernel xen-like module that exposes Xen PV 
> functionality, so you get all the PV benefits without the performance 
> hit from full virtualization and duplication of code.
>

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.


-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2009-04-05 11:37 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 [this message]
2009-04-05 12:10             ` Alexander Graf
2009-04-05 12:33               ` Avi Kivity
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=49D8980D.1070000@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).