From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: tcpdump locks up kvm host for a while. Date: Wed, 05 Oct 2011 20:21:53 +0200 Message-ID: <4E8CA041.1090709@redhat.com> References: <20111002173745.GG30948@stodi.digitalkingdom.org> <20111003030303.GH30948@stodi.digitalkingdom.org> <4E8B4D30.9030304@redhat.com> <20111004194033.GL30164@stodi.digitalkingdom.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Nikola Ciprich , kvm@vger.kernel.org To: Robin Lee Powell Return-path: Received: from mx1.redhat.com ([209.132.183.28]:38749 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932812Ab1JESWE (ORCPT ); Wed, 5 Oct 2011 14:22:04 -0400 In-Reply-To: <20111004194033.GL30164@stodi.digitalkingdom.org> Sender: kvm-owner@vger.kernel.org List-ID: On 10/04/2011 09:40 PM, Robin Lee Powell wrote: > > >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. > > > > You can use 'perf kvm' to figure out where the guest is spinning. > > OK, gathered with: > > sudo perf kvm --guest --host record -o /tmp/kvm_perf -a > > I don't know how to read it at all, so it's at > http://users.digitalkingdom.org/~rlpowell/media/public/kvm_perf > Not accessible. Please post the output of 'perf kvm report > log'. -- error compiling committee.c: too many arguments to function