From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Guest Hang Bugs Date: Thu, 15 Jan 2009 17:27:39 +0200 Message-ID: <496F55EB.6040506@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: James Thomason Return-path: Received: from mx2.redhat.com ([66.187.237.31]:35372 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753228AbZAOP1o (ORCPT ); Thu, 15 Jan 2009 10:27:44 -0500 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: James Thomason wrote: > Hello, > > I am able to reliably reproduce a condition where a guest goes into a tight > loop or spinlock on all running cores. The scenario is exactly as described > in bug 2351676, though my environment differs as detailed below. My > observation is that the issue is correlated to the number of VCPUs assigned > to the guest and CPU load. The higher the number of VCPUs and CPU > utilization, the more easily it is triggered. If a KVM developer is > interested in debugging live, I might be able to arrange getting the system > in question into a DMZ. A review of the kvm tracker leads me to believe > that the following bugs are possibly related: > > [ 2351676 ] Guests hang periodically on Ubuntu-8.10 > [ 2353811 ] Solaris 10 guest unstable > > [ 2494730 ] Guests "stalling" on kvm-82 > [ 2138079 ] kvm locks up system > [ 2113643 ] guests AND host still getting stuck under CPU load > > Cam you try adding clocksource=acpi_pm to the _guest_ kernel command line? -- error compiling committee.c: too many arguments to function