From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:33638)
	by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <pl@kamp.de>)
	id 1YL75j-0004AY-Su
	for qemu-devel@nongnu.org; Tue, 10 Feb 2015 04:26:48 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pl@kamp.de>) id 1YL75f-0006S6-Ri
	for qemu-devel@nongnu.org; Tue, 10 Feb 2015 04:26:47 -0500
Received: from mx-v6.kamp.de ([2a02:248:0:51::16]:49857 helo=mx01.kamp.de)
	by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <pl@kamp.de>)
	id 1YL75f-0006R8-FT
	for qemu-devel@nongnu.org; Tue, 10 Feb 2015 04:26:43 -0500
Message-ID: <54D9CEC9.9040902@kamp.de>
Date: Tue, 10 Feb 2015 10:26:33 +0100
From: Peter Lieven <pl@kamp.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [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: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, mtosatti@redhat.com, agraf@suse.de

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