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 15:51:33 +0300 Message-ID: <4C0E3CD5.4070202@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> 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]:7507 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753746Ab0FHMvh (ORCPT ); Tue, 8 Jun 2010 08:51:37 -0400 In-Reply-To: <4C0E3C46.30901@dlh.net> Sender: kvm-owner@vger.kernel.org List-ID: On 06/08/2010 03:49 PM, Peter Lieven wrote: >> >> And finally, perhaps you have NX disabled in the bios of one of the >> machines? >> >> What does 'dmesg | grep NX' show on both hosts? >> > > nx was disabled on one of the nodes. That explains the problem. > 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). > and why was it working with 2.6.34 and is not with 2.6.35-rc2? We fixed a different bug. But you shouldn't live migrate from a machine with nx to a machine without nx, unless you use -cpu ...,-nx on both nodes. -- error compiling committee.c: too many arguments to function