From mboxrd@z Thu Jan 1 00:00:00 1970 From: Max Kellermann Subject: Re: KVM guest lockup Date: Mon, 22 Dec 2008 11:57:38 +0100 Message-ID: <20081222105738.GA27409@squirrel.roonstrasse.net> References: <20081219174401.GA2730@squirrel.roonstrasse.net> <20081221115538.GA25958@x61s.gondor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org To: Jan Niehusmann Return-path: Received: from smtp4.netcologne.de ([194.8.194.137]:57546 "EHLO smtp4.netcologne.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752731AbYLVK5k (ORCPT ); Mon, 22 Dec 2008 05:57:40 -0500 Content-Disposition: inline In-Reply-To: <20081221115538.GA25958@x61s.gondor.com> Sender: kvm-owner@vger.kernel.org List-ID: On 2008/12/21 12:55, Jan Niehusmann wrote: > As I observed such behaviour only when the host has frequency > scaling activated: Could it be that in this case, > clocksource_read(clock) on the guest is misbehaving? Indeed, the host had governor=ondemand. After the switch to "performance", the guest seems to run stable. So this is a bug in the guest kernel, by making wrong assumptions on the clock values retrieved from the host, right? Max