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: tap devices not receiving packets from a bridge
Date: Tue, 14 May 2013 15:49:09 +0100 [thread overview]
Message-ID: <1368542949.15129.354.camel@eboracum.office.bytemark.co.uk> (raw)
In-Reply-To: <519249F6.3000900@dlhnet.de>
Hi,
On Tue, 2013-05-14 at 16:28 +0200, Peter Lieven wrote:
> Please check the tunnel mode in sysfs after your VM is started. It is likely
> that qemu overwrites the settings you made in the ruby script.
>
> Please check if the patch
>
> tap: set IFF_ONE_QUEUE per default
>
> is in your qemu 1.4.1 version.
That didn't even cross my mind!
/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.
Sorry for the noise, and thanks for the quick response :)
/Nick
WARNING: multiple messages have this Message-ID (diff)
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: Tue, 14 May 2013 15:49:09 +0100 [thread overview]
Message-ID: <1368542949.15129.354.camel@eboracum.office.bytemark.co.uk> (raw)
In-Reply-To: <519249F6.3000900@dlhnet.de>
Hi,
On Tue, 2013-05-14 at 16:28 +0200, Peter Lieven wrote:
> Please check the tunnel mode in sysfs after your VM is started. It is likely
> that qemu overwrites the settings you made in the ruby script.
>
> Please check if the patch
>
> tap: set IFF_ONE_QUEUE per default
>
> is in your qemu 1.4.1 version.
That didn't even cross my mind!
/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.
Sorry for the noise, and thanks for the quick response :)
/Nick
next prev parent reply other threads:[~2013-05-14 14:49 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
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 [this message]
2013-05-14 14:49 ` 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=1368542949.15129.354.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 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.