On Fri, Aug 02, 2013 at 11:28:45AM +0000, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=60620 > > --- Comment #9 from Folkert van Heusden <folk...@vanheusden.com> --- > Good news! > If I > > - bring down all interfaces in the guest (ifdown eth0...) > - rmmod virtio_net > - modprobe virtio_net > - bring up the interfaces again > + it all works again! > > So hopefully this helps the bug hunt?
Hi Folkert, Please post the QEMU command-line on the host (ps aux | grep qemu) and the output of lsmod | grep vhost_net. Since reinitializing the guest driver "fixes" the issue, we now need to find out whether the guest or the host side got stuck. I think I asked before, but please also post any relevant lines from dmesg on the host and from the guest. Examples would include networking error messages, kernel backtraces, or out-of-memory errors. Thanks, Stefan -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
