From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53794) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YL816-00034i-Ds for qemu-devel@nongnu.org; Tue, 10 Feb 2015 05:26:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YL814-0002u8-58 for qemu-devel@nongnu.org; Tue, 10 Feb 2015 05:26:04 -0500 Received: from mx1.redhat.com ([209.132.183.28]:56707) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YL813-0002u1-VM for qemu-devel@nongnu.org; Tue, 10 Feb 2015 05:26:02 -0500 Message-ID: <54D9DCB0.8030407@redhat.com> Date: Tue, 10 Feb 2015 11:25:52 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <54D9CEC9.9040902@kamp.de> <54D9D421.10907@redhat.com> <54D9D765.4040805@kamp.de> <54D9DACD.9020704@redhat.com> <54D9DC74.1020502@kamp.de> In-Reply-To: <54D9DC74.1020502@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 11:24, Peter Lieven wrote: >>> >> First of all (but unrelated to the bug) do not use "-cpu qemu64" with >> KVM. > > I remember there was an issue with kvm64 anytime in the past, but this > is ages ago I think. I will change that for new vserver starts. What > (which flag) is the exact issue with qemu64 vs. kvm64 QEMU64 does not resemble any actual processor. You want the lowest denominator of your cluster, probably Nehalem. Paolo