From: Peter Lieven <pl@dlhnet.de>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] Lost network with rtl8139 / qemu-kvm 1.2.0
Date: Thu, 11 Apr 2013 08:13:17 +0200 [thread overview]
Message-ID: <5166547D.1090805@dlhnet.de> (raw)
Hi all,
I have a strange problem with a few old VMs running with Windows XP (and in this case a Win2008 R2 Server) that occasionally loose network connectivity.
The tap device shows increasing drops:
tap36 Link encap:Ethernet HWaddr b2:84:23:c0:e2:c0
inet6 addr: fe80::b084:23ff:fec0:e2c0/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:5816096 errors:0 dropped:0 overruns:0 frame:0
TX packets:3878744 errors:0 dropped:13775 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:5161769434 (5.1 GB) TX bytes:380415916 (380.4 MB)
I see this kinf of error only with Windows XP. All other VMs running fine. If I live migrate the VM to another
Node connectivity is restored. Rebooting the VM does not help.
The vServer still uses qemu-kvm-1.2.0, but all recent fixes to rtl8139 have been backported. The tap device
is also already running with IFF_ONE_QUEUE.
Any ideas?
Thank you,
Peter
reply other threads:[~2013-04-11 6:13 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=5166547D.1090805@dlhnet.de \
--to=pl@dlhnet.de \
--cc=mst@redhat.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.