From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41660) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YL7Rg-0003g9-Fg for qemu-devel@nongnu.org; Tue, 10 Feb 2015 04:49:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YL7Rd-0005u9-83 for qemu-devel@nongnu.org; Tue, 10 Feb 2015 04:49:28 -0500 Received: from mail-wg0-x22a.google.com ([2a00:1450:400c:c00::22a]:42650) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YL7Rd-0005tq-1W for qemu-devel@nongnu.org; Tue, 10 Feb 2015 04:49:25 -0500 Received: by mail-wg0-f42.google.com with SMTP id x13so32215389wgg.1 for ; Tue, 10 Feb 2015 01:49:24 -0800 (PST) Sender: Paolo Bonzini Message-ID: <54D9D421.10907@redhat.com> Date: Tue, 10 Feb 2015 10:49:21 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <54D9CEC9.9040902@kamp.de> In-Reply-To: <54D9CEC9.9040902@kamp.de> Content-Type: text/plain; charset=utf-8 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: Peter Lieven , "qemu-devel@nongnu.org" Cc: mtosatti@redhat.com, agraf@suse.de On 10/02/2015 10:26, 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? How can anyone help without knowing anything about your configuration? :) Paolo