From mboxrd@z Thu Jan 1 00:00:00 1970 From: rek2 Subject: Re: network shutdown under heavy load Date: Thu, 17 Dec 2009 13:15:46 -0500 Message-ID: <4B2A7552.4010102@binaryfreedom.info> References: <4B265E84.3070008@binaryfreedom.info> <4B28CFC0.4030800@redhat.com> <20091216131911.GA18327@gondor.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Avi Kivity , kvm@vger.kernel.org, Misha Pivovarov To: Herbert Xu Return-path: Received: from mail.binaryfreedom.info ([216.75.30.35]:38428 "EHLO libre.binaryfreedom.info" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932222AbZLQSPs (ORCPT ); Thu, 17 Dec 2009 13:15:48 -0500 In-Reply-To: <20091216131911.GA18327@gondor.apana.org.au> Sender: kvm-owner@vger.kernel.org List-ID: > What's the exact guest kernel version? When the network is down, > please get onto the guest console to determine which direction > (if not both) of the network is not functioning. > > You can run tcpdump in the guest/host and execute pings on both > sides to see which direction is blocked. > > Cheers, > on the hosts: uname -a Linux XXXX 2.6.31-16-server #53-Ubuntu SMP Tue Dec 8 05:08:02 UTC 2009 x86_64 GNU/Linux I been told that today the network when down again and one of the guys here had to log using the console and restart it for that particular guests.. on the guest: uname -a Linux XXXX 2.6.27.25-170.2.72.fc10.x86_64 #1 SMP Sun Jun 21 18:39:34 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux Next time it goes down I will try to run a sniffer and try both sides.