From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:49737)
	by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <pl@kamp.de>)
	id 1YL9lQ-0001Y2-TO
	for qemu-devel@nongnu.org; Tue, 10 Feb 2015 07:18:02 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pl@kamp.de>) id 1YL9lN-0003On-J8
	for qemu-devel@nongnu.org; Tue, 10 Feb 2015 07:18:00 -0500
Received: from mx-v6.kamp.de ([2a02:248:0:51::16]:42952 helo=mx01.kamp.de)
	by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <pl@kamp.de>)
	id 1YL9lN-0003OS-8n
	for qemu-devel@nongnu.org; Tue, 10 Feb 2015 07:17:57 -0500
Message-ID: <54D9F6EC.5080807@kamp.de>
Date: Tue, 10 Feb 2015 13:17:48 +0100
From: Peter Lieven <pl@kamp.de>
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: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, "qemu-devel@nongnu.org" <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

I have build my kvm module from

http://git.kiszka.org/?p=kvm-kmod.git

but it seems not to have been updates since October.
The patch is not in there.

Is that repository not up to date anymore?

Peter