From: Arnd Bergmann <arnd@arndb.de>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Gerhard Wiesinger <lists@wiesinger.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Network bridging without adding bridge with brctl, possible?
Date: Mon, 21 Feb 2011 13:07:38 +0100 [thread overview]
Message-ID: <201102211307.38714.arnd@arndb.de> (raw)
In-Reply-To: <4D622602.7070009@web.de>
On Monday 21 February 2011, Jan Kiszka wrote:
> > Now I think I tried all useful possible combinations:
> > 1.) macvtap0 and macvlan0 in bridged and non bridge mode
> > 2.) macvlan0 based on eth0 or based on macvtap0
> > 3.) Using and ip address on macvlan0 or not (tried both for 7b mac and
> > 7c mac)
> > 4.) Using 7b and 7c mac address in KVM (MAC in KVM is always the command
> > line configured) and used tap interface from macvtap0 (as no second tap
> > devices shows up)
> >
> > Summary:
> > 1.) Using macvtap0 only with 7b mac on interface and also at qemu works
> > well in bridged mode as well as non bridged mode but with limitation no
> > guest/host communication possible, used interface in KVM is tap
> > interface created by macvtap0. Quite logically that it doesn't work with
> > guest/host because of missing hairpin mode on the switch. But according
> > to http://virt.kernelnewbies.org/MacVTap bridge mode should work even
> > without hairpinning available on the switch.
> > 2.) macvlan0 doesn't create any tap interface therefore it can't be used
> > as a device on KVM.
> > 3.) Using 7c mac address in KVM doesn't work at all regardsless of
> > setting ip addresses on macvlan0 or any other setup.
> >
> > @Arnd: Can you explain a setup in detail which should work also with
> > host/guest communication. Thnx.
> >
> > Any further ideas?
> > Which kernel is needed to work?
> > (current: 2.6.34.7-56.fc13.x86_64)
>
> Actually, I tried this successfully over a 2.6.38-rcX, but I have no
> idea what changes related to macvlan/tap went in since .34 and if this
> is required for this.
We had a few bugs in .34, but it should work in general.
One thing to make sure is that the host has connectivity through the
macvlan interface and the lower interface (eth0) has no IP address assigned
but is 'up'.
It could also be a bug in the NIC, you could try to set the NIC into
promiscious mode using ethtool to work around that.
Also, the lower interface must not be connected to a bridge device.
Arnd
next prev parent reply other threads:[~2011-02-21 12:08 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
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 [this message]
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=201102211307.38714.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 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.