From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Fjellstrom Subject: Re: kvm linux guest hanging for minutes at a time Date: Tue, 9 Aug 2011 08:54:03 -0600 Message-ID: <201108090854.03516.thomas@fjellstrom.ca> References: <201108070806.59194.thomas@fjellstrom.ca> <201108090846.14525.thomas@fjellstrom.ca> <4E4148FF.4010503@redhat.com> Reply-To: thomas@fjellstrom.ca Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" To: Avi Kivity Return-path: Received: from mail.tomasu.net ([64.85.170.232]:54171 "EHLO mail.tomasu.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750773Ab1HIOyK (ORCPT ); Tue, 9 Aug 2011 10:54:10 -0400 In-Reply-To: <4E4148FF.4010503@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On August 9, 2011, Avi Kivity wrote: > 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. The fun part is the last thing to cause a hang was a 'aptitude dist-upgrade', which updated the kernel, and removed the running kernel, so if it has to be restarted, I won't be able to run again with the same kernel, unless I can find the package for the old kernel some place. -- Thomas Fjellstrom thomas@fjellstrom.ca