From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Or Gerlitz <ogerlitz@voltaire.com>,
Arnd Bergmann <arndbergmann@googlemail.com>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH-updated] qemu/net: add raw backend
Date: Wed, 14 Oct 2009 18:20:00 +0200 [thread overview]
Message-ID: <20091014161959.GA30367@redhat.com> (raw)
In-Reply-To: <4AD5E449.9070301@codemonkey.ws>
On Wed, Oct 14, 2009 at 09:46:33AM -0500, Anthony Liguori wrote:
> 1) slirp does not behave how they think it should (icmp doesn't work,
> guest isn't accessable from host)
> 2) it's difficult to figure out which backend behaves the way they want
> (socket vs. vde vs. tap)
> 3) when they figure out they need tap, tap is difficult to setup
This is more or less what we have with sound too, by the way: multiple
backends, not one of which works well in all situations. Yes, it would
be nice to have a single backend solving all problems, and people are
working on it, but I don't think this is an argument that new partial
solutions are unacceptable.
--
MST
prev parent reply other threads:[~2009-10-14 16:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 14:34 [Qemu-devel] [PATCH-updated] qemu/net: add raw backend Or Gerlitz
2009-10-14 14:46 ` [Qemu-devel] " Anthony Liguori
2009-10-14 15:14 ` Jamie Lokier
2009-10-14 15:58 ` Anthony Liguori
2009-10-14 16:14 ` Michael S. Tsirkin
2009-10-14 16:54 ` Jamie Lokier
2009-10-14 17:20 ` Michael S. Tsirkin
2009-10-14 18:36 ` Anthony Liguori
2009-10-14 19:37 ` Michael S. Tsirkin
2009-10-15 7:48 ` Or Gerlitz
2009-10-14 15:58 ` Michael S. Tsirkin
2009-10-14 15:24 ` Michael S. Tsirkin
2009-10-14 15:33 ` Gleb Natapov
2009-10-15 7:29 ` Or Gerlitz
2009-10-15 7:44 ` Gleb Natapov
2009-10-15 7:50 ` Or Gerlitz
2009-10-14 16:20 ` Michael S. Tsirkin [this message]
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=20091014161959.GA30367@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=arndbergmann@googlemail.com \
--cc=ogerlitz@voltaire.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).