From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Lieven Subject: Re: Live Migration of 32-bit Linux guest broken since 2.6.35-rc2 Date: Tue, 08 Jun 2010 14:49:10 +0200 Message-ID: <4C0E3C46.30901@dlh.net> References: <215BBDE4-B30E-4E55-8AC7-3B7C25662FAC@dlh.net> <4C0E09C0.9060300@dlh.net> <4C0E29B6.7060302@redhat.com> <4C0E2A1E.6080609@redhat.com> <4C0E2ECC.5090806@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org To: Avi Kivity Return-path: Received: from zion.dlh.net ([91.198.192.1]:35865 "EHLO mail.dlh.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751479Ab0FHMtX (ORCPT ); Tue, 8 Jun 2010 08:49:23 -0400 In-Reply-To: <4C0E2ECC.5090806@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity wrote: > On 06/08/2010 02:31 PM, Avi Kivity wrote: >> On 06/08/2010 02:29 PM, Avi Kivity wrote: >>> On 06/08/2010 12:13 PM, Peter Lieven wrote: >>>> sorry, the subject should read 2.6.35-rc2 >>>> >>>> Peter Lieven wrote: >>>>> Hi, >>>>> >>>>> I freshly installed kernel 2.6.35-rc2 using userspace qemu-kvm=20 >>>>> 0.12.4. >>>>> >>>>> When I live migrate a 32-bit opensuse-11.2 VM, the incoming VM sh= ows >>>>> the following error after the mem transfer has finished: >>>>> >>>>> kvm: unhandled exit 80000022 >>>>> kvm: kvm_run returned -22 >>>>> >>>>> cmdline: >>>>> /usr/bin/qemu-kvm-0.12.4 -net none -drive=20 >>>>> format=3Dhost_device,file=3D/dev/mapper/iqn.2001-05.com.equallogi= c:0-8a0906-e1861b105-4cb000e7e8c4bf3b-opensuse-11-2-i586,if=3Dide,boot=3D= on,cache=3Dnone,aio=3Dnative =20 >>>>> -m 1024 -monitor tcp:0:4003,server,nowait -vnc :3 -name=20 >>>>> 'opensuse-11.2-i586' -boot order=3Ddc,menu=3Don -k de -incomin= g=20 >>>>> tcp:172.21.55.20:5003 -pidfile /var/run/qemu/vm-154.pid =20 >>>>> -mem-path /hugepages -mem-prealloc -rtc base=3Dutc -usb -usbdevi= ce=20 >>>>> tablet -cpu qemu64,model_id=3D'Intel(R) Xeon(R) CPU E54= 30 =20 >>>>> @ 2.66GHz' >>>>> >>>>> Migrating the same VM worked with 2.6.34 kvm module. >>> >>> >>> Please provide you host /proc/cpuinfo. >>> >> >> Also, after migration fails, the output of 'info registers' in the=20 >> monitor. >> > > And finally, perhaps you have NX disabled in the bios of one of the=20 > machines? > > What does 'dmesg | grep NX' show on both hosts? > nx was disabled on one of the nodes. i will retry the case later today=20 and send info register output. what is the recommended value for nx (and why)? and why was it working with 2.6.34 and is not with 2.6.35-rc2? --=20 Mit freundlichen Gr=FC=DFen/Kind Regards Peter Lieven =2E....................................................................= =2E.................................... KAMP Netzwerkdienste GmbH Vestische Str. 89-91 | 46117 Oberhausen Tel: +49 (0) 208.89 402-50 | Fax: +49 (0) 208.89 402-40 mailto:pl@kamp.de | http://www.kamp.de Gesch=E4ftsf=FChrer: Heiner Lante | Michael Lante Amtsgericht Duisburg | HRB Nr. 12154 USt-Id-Nr.: DE 120607556 =2E....................................................................= =2E...................................=20