From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] qemu, kvm, xen
Date: Fri, 6 Apr 2007 09:29:07 -0700 [thread overview]
Message-ID: <13426df10704060929m22cec0b0x81aa5b8fac68a44e@mail.gmail.com> (raw)
In-Reply-To: <a4e6962a0704060752t1592bc0cy94d8e8ec93c262d7@mail.gmail.com>
On 4/6/07, Eric Van Hensbergen <ericvh@gmail.com> wrote:
> kvm will catch up as soon as better paravirtualization interfaces are
> integrated (particularly for I/O) -- this is why I wanted to push 9p
> as the KVM paravirtualized I/O interface -- its clear they need to
> close that gap.
I think this is correct. We will keep the THX name however when we
move to kvm, since it's much nicer.
This is a window in time, folks. Anyone who has time to work on
paravirt I/O for kvm that uses 9p could probably get somewhere with
the kvm guys, and avoid the problems of the xen I/O device interface.
I think, overall, given its much simpler setup, kvm is going to win in
the long term. It's in the kernel, it's a piece of cake to set up and
use, you don't need python, xml-rpc, and tons of config files. There
are almost fewer lines of code in kvm than there are files in xen. OK,
so I'm exaggerating, but not by much.
One thing I'm finding is that linux is a very tolerable device driver
layer for Plan 9. This T60, with Plan 9 as a guest OS, is a far better
Plan 9 platform than a T23 with Plan 9 native.
thanks
ron
next prev parent reply other threads:[~2007-04-06 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 14:36 ron minnich
2007-04-06 14:46 ` Anthony Sorace
2007-04-06 14:52 ` Eric Van Hensbergen
2007-04-06 16:29 ` ron minnich [this message]
2007-04-06 16:32 ` Paweł Lasek
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=13426df10704060929m22cec0b0x81aa5b8fac68a44e@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=9fans@cse.psu.edu \
/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).