* This is a "RX lockup" condition -- VM still runs, can send traffic (ARP requests, mostly), but cannot receive replies.
* On Lucid, two backports to 2.6.32 are needed, "virtio_net: Make delayed refill more reliable" and "Add limit for socket backlog". I didn't research which mainline versions include them. Debian bugs #576838 and #592187 discuss each of these backports.
* On Karmic, another backport is needed [1]; not to kernel, but to QEMU: ("Fix a race condition where qemu finds that there are not enough virtio ring buffers available and the guest make more buffers available before qemu can enable notifications")
To summarize:
* This is a "RX lockup" condition -- VM still runs, can send traffic (ARP requests, mostly), but cannot receive replies.
* On Lucid, two backports to 2.6.32 are needed, "virtio_net: Make delayed refill more reliable" and "Add limit for socket backlog". I didn't research which mainline versions include them. Debian bugs #576838 and #592187 discuss each of these backports.
* On Karmic, another backport is needed [1]; not to kernel, but to QEMU: ("Fix a race condition where qemu finds that there are not enough virtio ring buffers available and the guest make more buffers available before qemu can enable notifications")
[1] http:// forum.proxmox. com/threads/ 3117-virtio- net-crashing- (stop-sending- traffic) ?p=20247# post20247