From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: TSC deadline timer in guests vs. migration?
Date: Mon, 4 Jul 2016 13:01:42 +0200
Message-ID: <759376f0-e0bf-e53a-99e4-598bf14547e3@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
To: Marcelo Tosatti <mtosatti@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	David Matlack <dmatlack@google.com>,
	Peter Hornyack <peterhornyack@google.com>,
	KVM list <kvm@vger.kernel.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:60297 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753023AbcGDLBq (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 4 Jul 2016 07:01:46 -0400
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Can bad things happen if a guest using the TSC deadline timer is
migrated?  The guest doesn't re-calibrate the TSC after migration, and
the TSC frequency can and will change unless your data center is
perfectly homogeneous.

What do you think?

Paolo