From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: Houston, we have May 15, 1953 (says guest when host uses cpufreq, and dies) Date: Thu, 19 Feb 2009 11:27:10 +0100 Message-ID: <499D33FE.4030106@redhat.com> References: <499C206A.5050109@wpkg.org> <499C3131.3030601@codemonkey.ws> <499C3327.3090207@wpkg.org> <499C3E6E.4050807@redhat.com> <499C7196.7050001@codemonkey.ws> <499D232A.7040206@redhat.com> <499D2460.60201@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , Avi Kivity , kvm@vger.kernel.org To: Tomasz Chmielewski Return-path: Received: from mx2.redhat.com ([66.187.237.31]:56364 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751559AbZBSK1Q (ORCPT ); Thu, 19 Feb 2009 05:27:16 -0500 In-Reply-To: <499D2460.60201@wpkg.org> Sender: kvm-owner@vger.kernel.org List-ID: Tomasz Chmielewski wrote: > So with Linux virtio guests I may have luck, but not so with Windows, > which can't (yet?) use kvm-clock. Correct? tsc isn't the only clocksource, there are also hpet and acpi (pm timer), they shouldn't have trouble with tsc freq changes. Dunno what windows uses by default. cheers, Gerd