From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: Houston, we have May 15, 1953 (says guest when host uses
	cpufreq, and dies)
Date: Wed, 18 Feb 2009 15:46:11 -0300
Message-ID: <20090218184611.GG25719@amt.cnet>
References: <499C206A.5050109@wpkg.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: kvm@vger.kernel.org
To: Tomasz Chmielewski <mangoo@wpkg.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx2.redhat.com ([66.187.237.31]:48371 "EHLO mx2.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752692AbZBRSqz (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 18 Feb 2009 13:46:55 -0500
Content-Disposition: inline
In-Reply-To: <499C206A.5050109@wpkg.org>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Wed, Feb 18, 2009 at 03:51:22PM +0100, Tomasz Chmielewski wrote:
> Is using cpufreq (i.e. with ondemand governor) on KVM host safe for guests?
>
> I enabled cpufreq on the host, it scaled down the host CPU (Dual-Core  
> AMD Opteron(tm) Processor 2212) to 1 GHz from 2 GHz.
>
> Guest (using 1 CPU) was still showing that it has a 2 GHz CPU in  
> /proc/cpuinfo (I guess this value is read only once, when booting).
>
> After about 2 hours I started "date" on the guest - it showed that it's  
> year *1953*, after which I couldn't start any other command (the guest  
> was technically alive - SSH connection to it didn't die - but I couldn't  
> do anything).
>
> # date
> Wed Feb 18 13:07:17 CET 2009
>
> [let's wait ~2 hours]
>
>
> # date
> Fri May 15 10:13:14 CET 1953
> # date
> ^C^Z
> [could not interrupt]
>
>
> Is it expected behaviour? Is it correct behaviour?

Whats the output of /proc/cpuinfo on the host? Does it contain the
constant_tsc flag?

Whats the output of
/sys/devices/system/clocksource/clocksource0/current_clocksource
on the guest?