qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Thomas <nick@bytemark.co.uk>
To: Peter Lieven <pl@dlhnet.de>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	netdev@vger.kernel.org, qemu-devel@nongnu.org,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] tap devices not receiving packets from a bridge
Date: Wed, 15 May 2013 12:00:03 +0100	[thread overview]
Message-ID: <1368615603.15129.1471.camel@eboracum.office.bytemark.co.uk> (raw)
In-Reply-To: <1368542949.15129.354.camel@eboracum.office.bytemark.co.uk>

Hi again,

On Tue, 2013-05-14 at 15:49 +0100, Nicholas Thomas wrote:
> /sys/devices/virtual/net/t100/tun_flags is 0x5002 - so it looks like
> IFF_ONE_QUEUE was indeed unset by qemu (which is lacking the patch). It
> surprises me, but that's probably my fault, rather than qemu's.


I've rebuilt 1.4.1 with the IFF_ONE_QUEUE patch and tun_flags is now
0x7002; unfortunately, I'm still seeing this bug, twice in five trials.
Symptoms in `ifconfig t100` now differ; overruns stays at 0, and
"dropped" increases monotonically as I send packets. Those packets do
appear if I tcpdump t100 on the host, but not if I tcpdump t100 on the
guest.

I've turned off gro in the guest, which makes no difference, and tried
changing the queue sizes (post-hoc) in both guest and host, in the hope
of causing them to be emptied out, clearing the condition; again to no
effect.

The VMs in question are bridged to a large (and busy) VLAN with no
ingress filtering to speak of; I guess what's happening is that the
transmit queue is filled up by that traffic while the guest is in ipxe,
and it never gets out of that state when it happens... so maybe there is
still an underlying problem?

/Nick

  reply	other threads:[~2013-05-15 11:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22 14:29 [Qemu-devel] tap devices not receiving packets from a bridge Peter Lieven
2012-11-23  7:02 ` Stefan Hajnoczi
2012-11-23  9:41   ` Peter Lieven
2012-11-23 11:01     ` Michael S. Tsirkin
2012-11-23 11:02       ` Peter Lieven
     [not found]       ` <50FE5607.9020405@dlhnet.de>
     [not found]         ` <20130123100312.GA8108@redhat.com>
     [not found]           ` <5119E9DC.3000505@dlhnet.de>
2013-05-14 14:21             ` Nicholas Thomas
2013-05-14 14:28               ` Peter Lieven
2013-05-14 14:49                 ` Nicholas Thomas
2013-05-15 11:00                   ` Nicholas Thomas [this message]
2013-05-16  6:24                     ` Michael S. Tsirkin
2013-05-16  6:27                       ` Michael S. Tsirkin
2013-05-16  8:20                         ` Nicholas Thomas
2013-05-16  8:40                           ` Michael S. Tsirkin
2013-05-16  8:47                             ` Peter Lieven
2013-05-16 11:27                             ` Nicholas Thomas
2013-05-16 12:09                               ` Michael S. Tsirkin
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=1368615603.15129.1471.camel@eboracum.office.bytemark.co.uk \
    --to=nick@bytemark.co.uk \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pl@dlhnet.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).