From: Arnd Bergmann <arnd@arndb.de>
To: Gerhard Wiesinger <lists@wiesinger.com>
Cc: Jan Kiszka <jan.kiszka@web.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Network bridging without adding bridge with brctl, possible?
Date: Sun, 20 Feb 2011 22:28:55 +0100 [thread overview]
Message-ID: <201102202228.55959.arnd@arndb.de> (raw)
In-Reply-To: <alpine.LFD.2.02.1102201058010.31275@bbs.intern>
On Sunday 20 February 2011, Gerhard Wiesinger wrote:
> >
> > Not sure if this is by design or due to internals of the networking
> > stack, but it looks unintuitive from user perspective. Maybe Arnd can
> > shed a light on this.
The lower device cannot be in bridge mode, because that would make the
logic in the kernel awfully complex. I agree that it's a bit unfortunate,
but it simplified the design a lot.
>
> > Of course, you could also simply offload all that setup to libvirt.
>
> http://wiki.libvirt.org/page/Networking
> But that still needs a bridge on ethernet level and break up the existing
> interface, right?
No. macvtap is a tap that sits on an external interface, you don't
need a bridge if you use it.
> BTW: From: http://virt.kernelnewbies.org/MacVTap
> As of QEMU 0.12:
> qemu -net nic,model=virtio,addr=1a:46:0b:ca:bc:7b -net tap,fd=3 3<>/dev/tap11
> Is there a newer Syntax with tap interfaces possible (QEMU GIT) without
> bash redirects?
I made some suggestions how to integrate it with qemu, but they never got in.
Libvirt makes it a lot easier, though. We discussed that it should be cleaned
up when the networking helper scripts make it into qemu. Not sure if that
ever happened.
Arnd
next prev parent reply other threads:[~2011-02-20 21:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 19:32 [Qemu-devel] Network bridging without adding bridge with brctl, possible? Gerhard Wiesinger
2011-02-20 9:44 ` [Qemu-devel] " Jan Kiszka
2011-02-20 10:19 ` Gerhard Wiesinger
2011-02-20 11:19 ` Jan Kiszka
2011-02-20 21:28 ` Arnd Bergmann [this message]
2011-02-21 6:12 ` Gerhard Wiesinger
2011-02-20 12:49 ` Gerhard Wiesinger
2011-02-20 14:15 ` Jan Kiszka
2011-02-20 15:19 ` Gerhard Wiesinger
2011-02-20 17:39 ` Jan Kiszka
2011-02-20 20:03 ` Gerhard Wiesinger
2011-02-20 21:33 ` Arnd Bergmann
2011-02-21 6:40 ` Gerhard Wiesinger
2011-02-21 8:44 ` Jan Kiszka
2011-02-21 12:07 ` Arnd Bergmann
2011-02-23 6:38 ` Gerhard Wiesinger
2011-02-23 12:53 ` Jan Kiszka
2011-02-24 6:49 ` Gerhard Wiesinger
2011-02-24 7:50 ` Jan Kiszka
2011-02-24 8:00 ` Arnd Bergmann
2011-02-23 14:47 ` Arnd Bergmann
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=201102202228.55959.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=jan.kiszka@web.de \
--cc=lists@wiesinger.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).