From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark McLoughlin Subject: Re: virtio_net hang Date: Thu, 13 Nov 2008 15:12:33 +0000 Message-ID: <1226589153.19068.7.camel@blaa> References: <20081113122709.GB14254@easter-eggs.com> Reply-To: Mark McLoughlin Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Emmanuel Lacour Return-path: Received: from mx2.redhat.com ([66.187.237.31]:39230 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751052AbYKMPNm (ORCPT ); Thu, 13 Nov 2008 10:13:42 -0500 In-Reply-To: <20081113122709.GB14254@easter-eggs.com> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, 2008-11-13 at 13:27 +0100, Emmanuel Lacour wrote: > 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. 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 the interface has hung, try: - tcpdump on both eth0 in the guest and the tap device on the host (tap5 in your example) - look for anything unusual in the stats for both those interfaces, e.g. /proc/net/dev, netstat -s etc. - strace the /usr/bin/kvm process What you're looking for e.g. is whether a guest->host ping is failing because the request packet isn't getting to the host or because the reply packet isn't getting to the guest, and where exactly the packet is being blocked. Cheers, Mark.