From: Anthony Liguori <anthony@codemonkey.ws>
To: Leszek Urbanski <tygrys@moo.pl>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] BUG - qdev - partial loss of network connectivity
Date: Wed, 22 Sep 2010 12:41:03 -0500 [thread overview]
Message-ID: <4C9A3FAF.9090503@codemonkey.ws> (raw)
In-Reply-To: <20100922171832.GA28721@moo.pl>
On 09/22/2010 12:18 PM, Leszek Urbanski wrote:
> Hi,
>
> This is a qemu-kvm (i.e. not qemu) bug report. I've been told on IRC (#kvm)
> that this bug report should go to this list anyway.
>
>
> host and guest kernel: 2.6.32.22
> arch: amd64
> qemu-kvm: 0.12.5 and 0.13.0-rc1
>
> How to reproduce: copy a large (few hundred MB) file to an NFS mount
> (guest is the client), using qdev syntax for virtio:
>
> -device virtio-net-pci,netdev=tap1,mac=ab:cd:ef:01:23:45 \
> -netdev type=tap,id=tap1,ifname=tap1
>
> all NFS mounts immediately stall and processes go into D state and are stuck
> on nfs_wait_bit_uninterruptible. There is no further communication between
> the client and the server. It occurs with UDP and TCP mounts.
>
> That same guest, when switched to the old -net/-net syntax:
>
> -net nic,vlan=0,model=virtio,name=eth0,macaddr=ab:cd:ef:01:23:45 \
> -net tap,vlan=0,ifname=tap1
>
> works fine. It also works fine on bare metal.
>
> I can reproduce the problem every time within 10 minutes with qdev.
>
Is the guest kernel vanilla 2.6.32.22 or is it a distro kernel? If the
later, what distro?
The difference in the two invocations is that with the -device syntax,
you're getting offload features enabled.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-09-22 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 17:18 [Qemu-devel] BUG - qdev - partial loss of network connectivity Leszek Urbanski
2010-09-22 17:41 ` Anthony Liguori [this message]
2010-09-22 18:20 ` Leszek Urbanski
2010-09-22 18:35 ` Anthony Liguori
2010-09-23 14:04 ` Leszek Urbanski
2010-09-26 15:43 ` [Qemu-devel] " Michael S. Tsirkin
2010-09-27 21:32 ` Leszek Urbanski
2010-09-28 9:50 ` Michael S. Tsirkin
2010-10-05 21:29 ` Leszek Urbanski
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=4C9A3FAF.9090503@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=tygrys@moo.pl \
/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).