From: Jan Kiszka <jan.kiszka@web.de>
To: Ed Swierk <eswierk@aristanetworks.com>
Cc: kvm@vger.kernel.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH][RFC] Xen PV-on-HVM guest support
Date: Thu, 15 Oct 2009 09:17:15 +0200 [thread overview]
Message-ID: <4AD6CC7B.6070200@web.de> (raw)
In-Reply-To: <9ae48b020910141249v12154451uc515b283ccfbd47e@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]
Ed Swierk wrote:
> Thanks for the feedback; I'll post a new version shortly.
>
> On Tue, Oct 13, 2009 at 11:45 PM, Jan Kiszka <jan.kiszka@web.de> wrote:
>> Interesting stuff. How usable is your work at this point? I've no
>> immediate demand, but the question if one could integrate Xen guests
>> with KVM already popped up more than once @work.
>
> So far I've managed to boot CentOS 5.3 (both i386 and x86_64) and use
> the Xen PV block and net devices, with pretty good performance. I've
> also booted FreeBSD 8.0-RC1 (amd64 only) with a XENHVM kernel and used
> the Xen PV block and net devices, but the performance of the net
> device is significantly worse than with CentOS. Also some FreeBSD
> applications use a flag that's not yet implemented in the net device
> emulation, but I'm working on fixing that.
>
> Overall it seems pretty solid for Linux PV-on-HVM guests. I think more
> work is needed to support full PV guests, but I don't know how much.
> Have folks been asking about PV-on-HVM or full PV?
Not all requests weren't that concrete /wrt technology, but some had
older setups and were definitely using full PV.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-10-15 7:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 4:52 [PATCH][RFC] Xen PV-on-HVM guest support Ed Swierk
2009-10-14 6:45 ` Jan Kiszka
2009-10-14 19:49 ` Ed Swierk
2009-10-15 7:17 ` Jan Kiszka [this message]
2009-10-15 7:30 ` Gerd Hoffmann
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=4AD6CC7B.6070200@web.de \
--to=jan.kiszka@web.de \
--cc=eswierk@aristanetworks.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.