From: Mark Clarkson <mark.clarkson-Sphq+rzYrv710XsdtD+oqA@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: White screen
Date: Tue, 19 Dec 2006 10:53:44 +0000 [thread overview]
Message-ID: <1166525624.13369.37.camel@localhost> (raw)
In-Reply-To: <45864C31.8080907-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Mon, 2006-12-18 at 10:07 +0200, Avi Kivity wrote:
> We intend, at first, to improve fully virtualized performance as far
> as
> we are able, without resorting to paravirtualized drivers.
>
> Should performance not be satisfactory to our needs, we may write
> paravirtualized devices and drivers. If we do so, I can't commit as
> to
> whether the paravirtualized Windows drivers will be open or not (I'm
> not
> saying the drivers will be closed -- just that no decision has been
> made).
>
> However, if you (or anyone) is interested in writing paravirtulized
> drivers, we will work with you towards merging them into the kernel
> and
> into the kvm distribution. We welcome such contributions and will
> cooperate fully.
Unfortunately the slow network performance and the fact that, on my
setup at least, network io takes 100% of a single core means that kvm is
not currently useful for server use.
I really like the idea of kvm over Xen as it's a much 'cleaner' solution
and would dearly love to see paravirtualised network drivers, at least
for Linux guests, which would allow me to consider moving from Xen to
kvm.
Do you think it possible/probable for someone with around 10 years
knowledge of Linux and C programming but with no kernel module writing
experience to be able to write a paravirtualised network driver for
linux in under 6 months (in his/her spare time)? Is there any example
code around for this? Would it be a case of say, modifying an ne2k
driver? In fact, I've literally just seen that paravirtualised drivers
exist for xen for linux 2.6 kernels and I presume these are open source
- could these be used in some way?
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-12-19 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 1:49 White screen Mark Clarkson
2006-12-18 8:07 ` Avi Kivity
[not found] ` <45864C31.8080907-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-12-18 8:16 ` Dor Laor
2006-12-19 10:53 ` Mark Clarkson [this message]
2006-12-19 11:08 ` Avi Kivity
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=1166525624.13369.37.camel@localhost \
--to=mark.clarkson-sphq+rzyrv710xsdtd+oqa@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox