virtio_net hang

2008-11-13 Thread Emmanuel Lacour
Dear kvm users/developpers, I have a problem here where the network interface of a guest hang 2 or 3 times a day. No more packets can be sent out or received, no error in guest or host logs. I have to stop networking, remove module, then modprobe again and start the network to get back connection.

Re: virtio_net hang

2008-11-13 Thread Emmanuel Lacour
On Thu, Nov 13, 2008 at 01:04:05PM +, Daniel P. Berrange wrote: > > Many of the KVM developers don't use libvirt, so probably best if you > post the actual KVM command line libvirt spawned - you can get it from > the logfile in /var/log/libvirt/qemu/$NAME.log, where $NAME is your > guest's nam

Re: virtio_net hang

2008-11-13 Thread Emmanuel Lacour
On Thu, Nov 13, 2008 at 03:12:33PM +, Mark McLoughlin wrote: > The fact that re-loading the virtio_net driver fixes things up makes me > suspect you've found a bug in the virtio_net driver, rather than e.g. a > bug in the kvm-userspace side. > > To try and narrow down what's happening, when th

Re: virtio_net hang

2008-11-14 Thread Emmanuel Lacour
On Thu, Nov 13, 2008 at 04:24:52PM +0100, Emmanuel Lacour wrote: > On Thu, Nov 13, 2008 at 03:12:33PM +, Mark McLoughlin wrote: > > The fact that re-loading the virtio_net driver fixes things up makes me > > suspect you've found a bug in the virtio_net driver, rather than e

Detect guest panic

2008-11-18 Thread Emmanuel Lacour
Dear users/developers, i have a guest which freeze 2 or 3 times per weeks (nothin in the logs, blank vnc screen). I'm going to try to fix this by testing upgrade to more recnt kernel/kvm, but I would like in the meantime to make a script which restart the guest domain in case it freezes. Is there

Re: Detect guest panic

2008-11-18 Thread Emmanuel Lacour
On Tue, Nov 18, 2008 at 09:39:35AM -0700, David Mair wrote: >> > If the guest has a reachable IP address the simplest way might be to > ping the guest from the host every so often and, if it stops responding > for long enough to make you believe it has frozen, kill the qemu process > and r

Re: virtio_net hang

2008-11-18 Thread Emmanuel Lacour
On Fri, Nov 14, 2008 at 06:26:44PM +, Mark McLoughlin wrote: > > Right, the tap device tx queue is full because kvm-userspace isn't > reading packets from it. > > This could be because kvm-userspace has just stopped noticing that > there's data available from the tapfd or because virtio_net i

Re: virtio_net hang

2008-11-18 Thread Emmanuel Lacour
On Tue, Nov 18, 2008 at 07:37:57PM +0100, Emmanuel Lacour wrote: > > I made the test, putting link down then up fix it. > > So what can I do next time to help fixing this ? > I had the problem one more time, I made an strace of the kvm process which start with non working networ

Re: virtio_net hang

2008-11-20 Thread Emmanuel Lacour
On Wed, Nov 19, 2008 at 01:13:52PM +, Mark McLoughlin wrote: > > Is it possible for you to try a newer guest kernel? > The guest will be rebooted today on 2.7.27.6. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo

Re: virtio_net hang

2008-11-20 Thread Emmanuel Lacour
On Wed, Nov 19, 2008 at 07:03:09PM +, Mark McLoughlin wrote: > > I had a look at Emmanuel's strace log and it shows that qemu isn't > selecting on the tapfd, presumably because virtio_net_can_receive() sees > that we've exhausted all available receive buffers. > > When qemu does poll the tapf

Re: virtio_net hang

2008-11-21 Thread Emmanuel Lacour
On Thu, Nov 20, 2008 at 12:36:50PM +0100, Emmanuel Lacour wrote: > The difficulty is that I can not always reproduce the bug. > > But another interesting think is that I switched to e1000 and I had > another lock after that with same symptoms :( > > Like answered a few minutes

Re: virtio_net hang

2008-11-22 Thread Emmanuel Lacour
On Fri, Nov 21, 2008 at 09:38:23AM +0100, Emmanuel Lacour wrote: > > I continue to have this problem with this setup: > > - host 2.6.27.4, kvm-78, intel, debian etch 64bits > - guest 2.6.27.6, debian sarge 32 bits, e1000, 2 vcpus > > up/down of interface is enough to recove