From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: kvm linux guest hanging for minutes at a time Date: Tue, 09 Aug 2011 17:49:35 +0300 Message-ID: <4E4148FF.4010503@redhat.com> References: <201108070806.59194.thomas@fjellstrom.ca> <201108090831.48423.thomas@fjellstrom.ca> <4E414615.8030201@redhat.com> <201108090846.14525.thomas@fjellstrom.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" To: thomas@fjellstrom.ca Return-path: Received: from mx1.redhat.com ([209.132.183.28]:2951 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752295Ab1HIOtj (ORCPT ); Tue, 9 Aug 2011 10:49:39 -0400 In-Reply-To: <201108090846.14525.thomas@fjellstrom.ca> Sender: kvm-owner@vger.kernel.org List-ID: On 08/09/2011 05:46 PM, Thomas Fjellstrom wrote: > > > Does it matter that I have several vms running? Is there a way to limit > > > it to tracing the single kvm process that's been locking up? > > > > You can use "trace-cmd record -F ... qemu ..." but that misses out on > > events the run from workqueues. > > > > Best to stop those other guests. > > I would prefer not to do that, those other guests are my web server, mail > server, and database server. I have no idea if I can reproduce the problem in > a reasonable time frame. > Okay then, please use -F. Note, please be sure to note the time the guest hangs so we can correlate it with the trace. -- error compiling committee.c: too many arguments to function