Date: Mon, 22 Dec 2008 11:57:38 +0100
From: Max Kellermann <max@duempel.org>
To: Jan Niehusmann <jan@gondor.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: KVM guest lockup
Message-ID: <20081222105738.GA27409@squirrel.roonstrasse.net>
Mail-Followup-To: Jan Niehusmann <jan@gondor.com>, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org
References: <20081219174401.GA2730@squirrel.roonstrasse.net> <20081221115538.GA25958@x61s.gondor.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20081221115538.GA25958@x61s.gondor.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 708
Lines: 17

On 2008/12/21 12:55, Jan Niehusmann <jan@gondor.com> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/