From: Paul Brook <paul@codesourcery.com>
To: Liraz Siri <liraz@turnkeylinux.org>
Cc: turnkey-discuss@lists.turnkeylinux.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Merging improvements from VirtualBox OSE into qemu?
Date: Wed, 24 Dec 2008 15:02:04 +0000 [thread overview]
Message-ID: <200812241502.04984.paul@codesourcery.com> (raw)
In-Reply-To: <4952484F.6010406@turnkeylinux.org>
On Wednesday 24 December 2008, Liraz Siri wrote:
> Paul Brook wrote:
> > You need root privileges to load the random kernel modules required to d
> > this. Not going to happen for qemu.
>
> There's at least one counter-precedent. qemu takes advantage of kqemu
> which is also a "random kernel module". How would supporting a kernel
> module that simplified a bridged networking be any different?
Well, I'm not a great fan of kqemu to start with. I suspect it may end up
being removed sooner rather than later.
Networking is not a qemu specific feature. The first thing you need to do is
convince the kernel folks that this is a useful feature, and get it
implemented there. Then we can make qemu use that interface.
What you've described sounds a lot like the pcap interface, which has its own
set of problems.
If your main argument is "users are too dumb to configure a bridge" then
you're arguing from a fairly weak position. The answer tends to be that you
need to make your configuration tools suck less.
Paul
next prev parent reply other threads:[~2008-12-24 15:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 12:48 [Qemu-devel] Merging improvements from VirtualBox OSE into qemu? Liraz Siri
2008-12-24 13:17 ` Samuel Thibault
2008-12-24 13:26 ` Alexey Eremenko
2008-12-24 13:31 ` Alexey Eremenko
2008-12-24 13:36 ` Paul Brook
2008-12-24 14:33 ` Liraz Siri
2008-12-24 14:51 ` Jernej Simončič
2008-12-24 15:02 ` Paul Brook [this message]
2008-12-24 15:29 ` Liraz Siri
2008-12-24 15:40 ` Anthony Liguori
2008-12-24 20:52 ` Liraz Siri
2008-12-25 4:37 ` C.W. Betts
2008-12-25 4:37 ` C.W. Betts
2008-12-25 7:06 ` Avi Kivity
2008-12-25 7:07 ` Avi Kivity
2008-12-25 7:08 ` Avi Kivity
2008-12-25 14:51 ` Liraz Siri
2008-12-25 16:14 ` Avi Kivity
2008-12-24 23:18 ` Jamie Lokier
2008-12-25 7:11 ` Avi Kivity
2008-12-24 15:23 ` Anthony Liguori
2008-12-24 20:21 ` Liraz Siri
2008-12-24 20:55 ` Liraz Siri
2009-01-05 21:12 ` Frank Mehnert
2009-01-05 22:03 ` Stefan Weil
2009-01-05 23:58 ` Anthony Liguori
2009-01-06 7:41 ` Frank Mehnert
2009-01-06 15:46 ` Blue Swirl
2009-01-06 17:33 ` Anthony Liguori
2009-01-06 20:40 ` Frank Mehnert
2009-01-06 22:17 ` Jamie Lokier
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=200812241502.04984.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=liraz@turnkeylinux.org \
--cc=qemu-devel@nongnu.org \
--cc=turnkey-discuss@lists.turnkeylinux.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.