All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Peter Lieven <pl@dlhnet.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, netdev@vger.kernel.org
Subject: Re: [Qemu-devel] tap devices not receiving packets from a bridge
Date: Fri, 23 Nov 2012 08:02:11 +0100	[thread overview]
Message-ID: <20121123070211.GC22787@stefanha-thinkpad.hitronhub.home> (raw)
In-Reply-To: <50AE36E0.8000307@dlhnet.de>

On Thu, Nov 22, 2012 at 03:29:52PM +0100, Peter Lieven wrote:
> is anyone aware of a problem with the linux network bridge that in very rare circumstances stops
> a bridge from sending pakets to a tap device?
> 
> My problem occurs in conjunction with vanilla qemu-kvm-1.2.0 and Ubuntu Kernel 3.2.0-34.53
> which is based on Linux 3.2.33.
> 
> I was not yet able to reproduce the issue, it happens in really rare cases. The symptom is that
> the tap does not have any TX packets. RX is working fine. I see the packets coming in at
> the physical interface on the host, but they are not forwarded to the tap interface.
> The bridge itself has learnt the mac address of the vServer that is connected to the tap interface.
> It does not help to toggle the bridge link status,  the tap interface status or the interface in the vServer.
> It seems that problem occurs if a tap interface that has previously been used, but set to nonpersistent
> is set persistent again and then is by chance assigned to the same vServer (=same mac address on same
> bridge) again. Unfortunately it seems not to be reproducible.

Not sure but this patch from Michael Tsirkin may help - it solves an
issue with persistent tap devices:

http://patchwork.ozlabs.org/patch/198598/

Stefan

WARNING: multiple messages have this Message-ID (diff)
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Peter Lieven <pl@dlhnet.de>
Cc: netdev@vger.kernel.org, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] tap devices not receiving packets from a bridge
Date: Fri, 23 Nov 2012 08:02:11 +0100	[thread overview]
Message-ID: <20121123070211.GC22787@stefanha-thinkpad.hitronhub.home> (raw)
In-Reply-To: <50AE36E0.8000307@dlhnet.de>

On Thu, Nov 22, 2012 at 03:29:52PM +0100, Peter Lieven wrote:
> is anyone aware of a problem with the linux network bridge that in very rare circumstances stops
> a bridge from sending pakets to a tap device?
> 
> My problem occurs in conjunction with vanilla qemu-kvm-1.2.0 and Ubuntu Kernel 3.2.0-34.53
> which is based on Linux 3.2.33.
> 
> I was not yet able to reproduce the issue, it happens in really rare cases. The symptom is that
> the tap does not have any TX packets. RX is working fine. I see the packets coming in at
> the physical interface on the host, but they are not forwarded to the tap interface.
> The bridge itself has learnt the mac address of the vServer that is connected to the tap interface.
> It does not help to toggle the bridge link status,  the tap interface status or the interface in the vServer.
> It seems that problem occurs if a tap interface that has previously been used, but set to nonpersistent
> is set persistent again and then is by chance assigned to the same vServer (=same mac address on same
> bridge) again. Unfortunately it seems not to be reproducible.

Not sure but this patch from Michael Tsirkin may help - it solves an
issue with persistent tap devices:

http://patchwork.ozlabs.org/patch/198598/

Stefan

  reply	other threads:[~2012-11-23  7:02 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22 14:29 tap devices not receiving packets from a bridge Peter Lieven
2012-11-22 14:29 ` [Qemu-devel] " Peter Lieven
2012-11-23  7:02 ` Stefan Hajnoczi [this message]
2012-11-23  7:02   ` Stefan Hajnoczi
2012-11-23  9:41   ` Peter Lieven
2012-11-23  9:41     ` Peter Lieven
2012-11-23 11:01     ` Michael S. Tsirkin
2012-11-23 11:02       ` Peter Lieven
2012-11-23 11:02         ` Peter Lieven
2013-01-22  9:04       ` Peter Lieven
2013-01-22  9:43         ` Peter Lieven
2013-01-23 10:03         ` [Qemu-devel] " Michael S. Tsirkin
2013-02-12  7:06           ` Peter Lieven
2013-02-12  9:08             ` [Qemu-devel] " Michael S. Tsirkin
2013-02-12  9:10               ` Peter Lieven
2013-02-12  9:29                 ` Michael S. Tsirkin
2013-02-12  9:39                 ` Michael Tokarev
2013-02-12  9:54                   ` Michael S. Tsirkin
2013-02-12 10:11                     ` [Qemu-devel] " Peter Lieven
2013-02-12 10:43                       ` Michael S. Tsirkin
2013-05-14 14:21             ` Nicholas Thomas
2013-05-14 14:21               ` [Qemu-devel] " Nicholas Thomas
2013-05-14 14:28               ` Peter Lieven
2013-05-14 14:28                 ` [Qemu-devel] " Peter Lieven
2013-05-14 14:49                 ` Nicholas Thomas
2013-05-14 14:49                   ` [Qemu-devel] " Nicholas Thomas
2013-05-15 11:00                   ` Nicholas Thomas
2013-05-15 11:00                     ` Nicholas Thomas
2013-05-16  6:24                     ` Michael S. Tsirkin
2013-05-16  6:24                       ` Michael S. Tsirkin
2013-05-16  6:27                       ` Michael S. Tsirkin
2013-05-16  6:27                         ` Michael S. Tsirkin
2013-05-16  8:20                         ` Nicholas Thomas
2013-05-16  8:20                           ` Nicholas Thomas
2013-05-16  8:40                           ` Michael S. Tsirkin
2013-05-16  8:40                             ` Michael S. Tsirkin
2013-05-16  8:47                             ` Peter Lieven
2013-05-16  8:47                               ` Peter Lieven
2013-05-16 11:27                             ` Nicholas Thomas
2013-05-16 11:27                               ` Nicholas Thomas
2013-05-16 12:09                               ` Michael S. Tsirkin
2013-05-16 12:09                                 ` Michael S. Tsirkin
2012-11-29 18:58   ` Peter Lieven
2012-11-29 18:58     ` Peter Lieven

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=20121123070211.GC22787@stefanha-thinkpad.hitronhub.home \
    --to=stefanha@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pl@dlhnet.de \
    --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.