From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: why guests show "Clocksource tsc unstable" on bootup?
Date: Sun, 15 Mar 2009 15:31:25 +0200
Message-ID: <49BD032D.80004@redhat.com>
References: <49B5050B.9050204@wpkg.org> <49BCFB0D.2000901@redhat.com> <49BCFD43.9010604@wpkg.org> <49BD00A6.20400@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Michael Tokarev <mjt@tls.msk.ru>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx2.redhat.com ([66.187.237.31]:42112 "EHLO mx2.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752061AbZCONbh (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sun, 15 Mar 2009 09:31:37 -0400
In-Reply-To: <49BD00A6.20400@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Avi Kivity wrote:
>
> This cpu indeed has unstable tsc, but disabling cpufreq should have 
> fixed it.
>
> Maybe we need to disable C-states as well?
>
>

Can you try idle=poll on the host kernel command line?  Note that this 
will run the cpu hot, so remove it after the test.

-- 
error compiling committee.c: too many arguments to function