From: Chris Webb <chris@arachsys.com>
To: qemu-devel@nongnu.org, netdev@vger.kernel.org
Subject: Re: [Qemu-devel] How to use macvtap/macvlan correctly
Date: Sun, 2 Oct 2011 20:46:17 +0100 [thread overview]
Message-ID: <20111002194616.GM14562@arachsys.com> (raw)
In-Reply-To: <20110930084935.GC12879@arachsys.com>
Chris Webb <chris@arachsys.com> writes:
> I'm trying to get bridge-mode communication between a macvtap and a host
> macvlan working correctly, but I think I must be doing something wrong as
> the host macvlan and guest macvtap apparently can't communicate. I'm aware
> that the underlying eth0 interface can't communicate with the macvtap, but I
> thought that creating a host macvlan device and configuring that was the
> standard work-around?
This turns out to be a bug in the kernel I'm using, 3.0.4, fixed by this
patch:
http://patchwork.ozlabs.org/patch/115273/
Cheers,
Chris.
prev parent reply other threads:[~2011-10-02 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 11:43 [Qemu-devel] [PATCH, RESEND] Fix SIGFPE race for vnc display resize Chris Webb
2011-09-30 8:49 ` [Qemu-devel] How to use macvtap/macvlan correctly Chris Webb
2011-10-02 19:46 ` Chris Webb [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=20111002194616.GM14562@arachsys.com \
--to=chris@arachsys.com \
--cc=netdev@vger.kernel.org \
--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).