From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Live Migration of 32-bit Linux guest broken since 2.6.35-rc2 Date: Tue, 08 Jun 2010 16:34:37 +0300 Message-ID: <4C0E46ED.5030305@redhat.com> References: <215BBDE4-B30E-4E55-8AC7-3B7C25662FAC@dlh.net> <4C0E09C0.9060300@dlh.net> <4C0E29B6.7060302@redhat.com> <4C0E2A1E.6080609@redhat.com> <4C0E2ECC.5090806@redhat.com> <4C0E3C46.30901@dlh.net> <4C0E3CD5.4070202@redhat.com> <4C0E4576.8030609@dlh.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org To: Peter Lieven Return-path: Received: from mx1.redhat.com ([209.132.183.28]:61937 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753963Ab0FHNel (ORCPT ); Tue, 8 Jun 2010 09:34:41 -0400 In-Reply-To: <4C0E4576.8030609@dlh.net> Sender: kvm-owner@vger.kernel.org List-ID: On 06/08/2010 04:28 PM, Peter Lieven wrote: >> >>> i will retry the case later today and send info register output. >>> what is the recommended value for nx (and why)? >> >> Enabled (so you get no-execute memory protection). > > do you have a guideline which flags should be identical to ensure > proper live migration? > i would like to do an automatic compare before life migration to avoid > crashes. All of them [1]. If you have an asymmetric machine, you can disable those flags with the -cpu switch. Note the default qemu cpu disables many flags, so if one machine has sse4.2 and the other doesn't, migration will still work without disabling anything. [1] Rather, all flags understood by qemu and kvm that are enabled by the cpu model that you gave to qemu with -cpu. -- error compiling committee.c: too many arguments to function