From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60962) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YL8Qf-00074B-9i for qemu-devel@nongnu.org; Tue, 10 Feb 2015 05:52:34 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YL8Qd-0005nk-Td for qemu-devel@nongnu.org; Tue, 10 Feb 2015 05:52:29 -0500 Received: from mx1.redhat.com ([209.132.183.28]:34505) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YL8Qd-0005nS-MO for qemu-devel@nongnu.org; Tue, 10 Feb 2015 05:52:27 -0500 Date: Tue, 10 Feb 2015 08:50:38 -0200 From: Marcelo Tosatti Message-ID: <20150210105038.GA32350@amt.cnet> References: <54D9CEC9.9040902@kamp.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54D9CEC9.9040902@kamp.de> 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: Peter Lieven Cc: Paolo Bonzini , "qemu-devel@nongnu.org" , agraf@suse.de 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