From: Leszek Urbanski <tygrys@moo.pl>
To: kvm@vger.kernel.org
Subject: BUG - qdev - partial loss of network connectivity
Date: Wed, 22 Sep 2010 13:42:01 +0200 [thread overview]
Message-ID: <20100922114201.GA25638@moo.pl> (raw)
Hi,
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.
--
Leszek "Tygrys" Urbanski, SCSA, SCNA
"Unix-to-Unix Copy Program;" said PDP-1. "You will never find a more
wretched hive of bugs and flamers. We must be cautious." -- DECWARS
http://cygnus.moo.pl/ -- Cygnus High Altitude Balloon
reply other threads:[~2010-09-22 11:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100922114201.GA25638@moo.pl \
--to=tygrys@moo.pl \
--cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox