From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49883) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YLvk4-0007y1-IE for qemu-devel@nongnu.org; Thu, 12 Feb 2015 10:31:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YLvjy-0000uR-VD for qemu-devel@nongnu.org; Thu, 12 Feb 2015 10:31:48 -0500 Received: from mx-v6.kamp.de ([2a02:248:0:51::16]:47470 helo=mx01.kamp.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YLvjy-0000ti-LU for qemu-devel@nongnu.org; Thu, 12 Feb 2015 10:31:42 -0500 Message-ID: <54DCC75A.2000401@kamp.de> Date: Thu, 12 Feb 2015 16:31:38 +0100 From: Peter Lieven MIME-Version: 1.0 References: <54D9CEC9.9040902@kamp.de> <20150210105038.GA32350@amt.cnet> In-Reply-To: <20150210105038.GA32350@amt.cnet> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] kvmclock_current_nsec: Assertion `time.tsc_timestamp <= migration_tsc' List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Marcelo Tosatti Cc: Paolo Bonzini , "qemu-devel@nongnu.org" , agraf@suse.de Am 10.02.2015 um 11:50 schrieb Marcelo Tosatti: > On Tue, Feb 10, 2015 at 10:26:33AM +0100, Peter Lieven wrote: >> Hi, >> >> while migrating vServers from 2.1.0 to 2.2.0 I see the following assertion that seems to have >> been introduced between 2.1.0 and 2.2.0 trigger on the destination. This happens in a serious >> amount of cases. In most cases it works flawlessly on the second attempt to migrate the vServer >> (same source and same destination). >> >> Any hints how to debug the root cause? >> >> Thank you, >> Peter > Peter, > > Make sure you have the following commit applied to the host: > > commit 7f187922ddf6b67f2999a76dcb71663097b75497 > KVM: x86: update masterclock values on TSC writes Thanks for the pointer. It seems that has fixed the assertion issue. Peter