From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: [PATCH 2/4] kvm: Allow invtsc migration if tsc-khz is set explicitly Date: Wed, 4 Jan 2017 09:57:40 -0200 Message-ID: <20170104115737.GC14961@amt.cnet> References: <1482866480-26208-1-git-send-email-ehabkost@redhat.com> <1482866480-26208-3-git-send-email-ehabkost@redhat.com> <20170104114404.GA14961@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Paolo Bonzini , qemu-devel@nongnu.org, kvm@vger.kernel.org, Haozhong Zhang To: Eduardo Habkost Return-path: Content-Disposition: inline In-Reply-To: <20170104114404.GA14961@amt.cnet> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: "Qemu-devel" List-Id: kvm.vger.kernel.org On Wed, Jan 04, 2017 at 09:44:06AM -0200, Marcelo Tosatti wrote: > On Tue, Dec 27, 2016 at 05:21:18PM -0200, Eduardo Habkost wrote: > > We can safely allow a VM to be migrated with invtsc enabled if > > tsc-khz is set explicitly, because QEMU already refuses to start > > if it can't set the TSC frequency to the configured value. > > On the source host, yes, but on the destination it does not. > > SOURCE: -cpu kvm64,tsc-frequency=2660001000 > DESTINATION: -cpu kvm64 > > Only prints: > > qemu-system-x86_64: warning: TSC frequency mismatch between VM (2660001 > kHz) and host (2893428 kHz), and TSC scaling unavailable > qemu-system-x86_64: warning: TSC frequency mismatch between VM (2660001 > kHz) and host (2893428 kHz), and TSC scaling unavailable > > And allows migration. Ignore that comment, patch 4 deals with it.