From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Treutner <thomas@scripty.at>
Subject: Re: Timedrift in KVM guests after livemigration.
Date: Thu, 22 Apr 2010 09:40:44 +0200
Message-ID: <201004220940.44920.thomas@scripty.at>
References: <4BC6C1B1.5010206@monsternett.no> <4BCACF6E.4010108@redhat.com> <4BCAD1F8.1080903@monsternett.no>
Mime-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: Espen Berg <espen@monsternett.no>
Return-path: <kvm-owner@vger.kernel.org>
Received: from static.115.55.40.188.clients.your-server.de ([188.40.55.115]:46098
	"EHLO scripty.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752797Ab0DVIAy (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 22 Apr 2010 04:00:54 -0400
In-Reply-To: <4BCAD1F8.1080903@monsternett.no>
Content-Disposition: inline
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Sunday 18 April 2010 11:33:44 Espen Berg wrote:
> All guest are Debian lenny with latest upstream kernel, hvm/kvm.
>
> We are using kvm-clock as guest source clock.
>
> cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> kvm-clock

I had to deactivate C1E (AMD CPUs) and use acpi clocksource (for both servers 
and VMs, IIRC). If you can, you should give it a try. After that, live 
migration worked somewhat stable.


regards, 
thomas