From: David Ahern <dsahern@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] networking stalls in the guest -- backlog in the host
Date: Thu, 27 Mar 2014 16:13:15 -0600 [thread overview]
Message-ID: <5334A27B.2000002@gmail.com> (raw)
We are hitting a networking problem and hoping someone has an idea --
perhaps a known bug.
After a couple of hours of runtime with low level traffic (e.g., 1 sec
pings) the VM stops receiving packets. In the host running tc on the tap
device shows a full backlog and packets getting dropped:
tc -s qdisc show dev vnet0
qdisc pfifo_fast 0: root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1
1 1 1 1 1
Sent 5806496634 bytes 4163358 pkt (dropped 116079, overlimits 0 requeues 4)
backlog 33834b 500p requeues 4
The tap device is passed to qemu as fd=24. Running strace on the IO
thread does not show the fd in the list passed to select. e.g.,
select(55, [7 8 11 18 52 53 54], [], [], {1, 0}) = 1 (in [8], left {0,
872402})
That would explain why the packets are not pulled from the tap device
into the VM. When networking is functioning properly, you do see fd=24
in the list followed by read(24, ...).
Why would qemu stop adding the fd to the list passed to select?
This is qemu-kvm-1.0 (upgrading is not an option), started by libvirt
(libvirt 1.0.2). The command line is rather long. Snippets:
/usr/bin/kvm -M pc-1.0 -cpu host -enable-kvm -m 4096 -smp 4
...
-netdev tap,fd=24,id=hostnet0 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:3e:ba:55:60,bus=pci.0,addr=0xa
...
Host kernel: 3.2.0-60-generic
Guest kernel: 3.8.0-29-generic
Thanks,
David
next reply other threads:[~2014-03-27 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 22:13 David Ahern [this message]
2014-04-01 15:09 ` [Qemu-devel] networking stalls in the guest -- backlog in the host Stefan Hajnoczi
2014-04-01 15:43 ` David Ahern
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=5334A27B.2000002@gmail.com \
--to=dsahern@gmail.com \
--cc=qemu-devel@nongnu.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 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.