From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nikola Ciprich Subject: Re: Re: [kvm] Re: [kvm] Re: [kvm] Re: [kvm] Re: [kvm] Re: tcpdump locks up kvm host for a while. Date: Mon, 3 Oct 2011 07:41:17 +0200 Message-ID: <20111003054117.GT8443@pcnci.linuxbox.cz> References: <20111002173745.GG30948@stodi.digitalkingdom.org> <20111003030303.GH30948@stodi.digitalkingdom.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gX5Hm7FaHdN5aeGl" Cc: Avi Kivity , kvm@vger.kernel.org To: Robin Lee Powell Return-path: Received: from gwu.lbox.cz ([62.245.111.132]:49810 "EHLO gwu.lbox.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755041Ab1JCFli (ORCPT ); Mon, 3 Oct 2011 01:41:38 -0400 Content-Disposition: inline In-Reply-To: <20111003030303.GH30948@stodi.digitalkingdom.org> Sender: kvm-owner@vger.kernel.org List-ID: --gX5Hm7FaHdN5aeGl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > When I run tcpdump on a *guest*, the entire guest completely freezes > up; no response even to hitting enter on the console. "virsh list" > also locks up whenever it tries to print state about that VM (but > the others work fine), as does any other operation that touches the > state of that VM. The VM takes up 100% of CPU on one core while > this is happening. Eventually it gets better. >=20 exactly the same I was describing here some time ago, with the difference I get a lot of ugly backtraces and sometimes the guest doesn't get to usabl= e state at all (filesystems switches to read only due to errors or the whole guest = locks up) n. --gX5Hm7FaHdN5aeGl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk6JSv0ACgkQ3xdJJrLygV4PuwCg3pY4MtkqpUWH0of7qv5FXTfg yhQAoJrGQBLlFOja7rUPDaqEn/uW83/C =wWY2 -----END PGP SIGNATURE----- --gX5Hm7FaHdN5aeGl--