All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Lieven <pl@dlhnet.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Nicholas Thomas <nick@bytemark.co.uk>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, netdev@vger.kernel.org
Subject: Re: [Qemu-devel] tap devices not receiving packets from a bridge
Date: Thu, 16 May 2013 10:47:02 +0200	[thread overview]
Message-ID: <51949D06.1060109@dlhnet.de> (raw)
In-Reply-To: <20130516084021.GA28125@redhat.com>

Am 16.05.2013 10:40, schrieb Michael S. Tsirkin:
> On Thu, May 16, 2013 at 09:20:55AM +0100, Nicholas Thomas wrote:
>> Hi,
>>
>> On Thu, 2013-05-16 at 09:27 +0300, Michael S. Tsirkin wrote:
>>> On Thu, May 16, 2013 at 09:24:05AM +0300, Michael S. Tsirkin wrote:
>>>> Is this with or without vhost-net in host?
>>>
>>> never mind, I see it's without.
>>> Try to enable vhost-net (you'll have to switch to -netdev syntax
>>> for that to work) and see if this help.
>>> If it does it's likely a qemu bug if not probably a guest bug.
>>
>> Switching to -netdev is non-trivial for me, unfortunately.
> 
> Interesting. Why is that?
> 
>> Anyway, it's
>> definitely a qemu bug - it happens on kernels 3.2 and 3.9 with 1.4.1,
>> but doesn't happen with qemu 0.15.0 or 1.5.0rc1.
>>
>> I'll have a dig through git to see if I can identify the patch that
>> resolves it. It feels-like qemu sometimes stops reading from the tap
>> file descriptor between ipxe exiting and the linux kernel bringing up
>> the network interface, and never recovers from that.
>>
>> /Nick
> 
> You can try to bisect, yes.
> 

It would be good to bisect this. I would appreciate it. I have a similar problem with rtl8139 (without vhost-net), but I was unable
to reproduce yet.

Thanks,
Peter

WARNING: multiple messages have this Message-ID (diff)
From: Peter Lieven <pl@dlhnet.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	netdev@vger.kernel.org, qemu-devel@nongnu.org,
	Nicholas Thomas <nick@bytemark.co.uk>
Subject: Re: [Qemu-devel] tap devices not receiving packets from a bridge
Date: Thu, 16 May 2013 10:47:02 +0200	[thread overview]
Message-ID: <51949D06.1060109@dlhnet.de> (raw)
In-Reply-To: <20130516084021.GA28125@redhat.com>

Am 16.05.2013 10:40, schrieb Michael S. Tsirkin:
> On Thu, May 16, 2013 at 09:20:55AM +0100, Nicholas Thomas wrote:
>> Hi,
>>
>> On Thu, 2013-05-16 at 09:27 +0300, Michael S. Tsirkin wrote:
>>> On Thu, May 16, 2013 at 09:24:05AM +0300, Michael S. Tsirkin wrote:
>>>> Is this with or without vhost-net in host?
>>>
>>> never mind, I see it's without.
>>> Try to enable vhost-net (you'll have to switch to -netdev syntax
>>> for that to work) and see if this help.
>>> If it does it's likely a qemu bug if not probably a guest bug.
>>
>> Switching to -netdev is non-trivial for me, unfortunately.
> 
> Interesting. Why is that?
> 
>> Anyway, it's
>> definitely a qemu bug - it happens on kernels 3.2 and 3.9 with 1.4.1,
>> but doesn't happen with qemu 0.15.0 or 1.5.0rc1.
>>
>> I'll have a dig through git to see if I can identify the patch that
>> resolves it. It feels-like qemu sometimes stops reading from the tap
>> file descriptor between ipxe exiting and the linux kernel bringing up
>> the network interface, and never recovers from that.
>>
>> /Nick
> 
> You can try to bisect, yes.
> 

It would be good to bisect this. I would appreciate it. I have a similar problem with rtl8139 (without vhost-net), but I was unable
to reproduce yet.

Thanks,
Peter

  reply	other threads:[~2013-05-16  8:47 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
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 [this message]
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=51949D06.1060109@dlhnet.de \
    --to=pl@dlhnet.de \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nick@bytemark.co.uk \
    --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.