From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:44083) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TIymN-00054f-Rs for qemu-devel@nongnu.org; Tue, 02 Oct 2012 05:28:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TIymM-0006US-Dg for qemu-devel@nongnu.org; Tue, 02 Oct 2012 05:28:39 -0400 Received: from mx1.redhat.com ([209.132.183.28]:33167) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TIymM-0006UO-52 for qemu-devel@nongnu.org; Tue, 02 Oct 2012 05:28:38 -0400 Message-ID: <506AB3C5.9040109@redhat.com> Date: Tue, 02 Oct 2012 11:28:37 +0200 From: Orit Wasserman MIME-Version: 1.0 References: <5055AC78.8040606@dlhnet.de> <505765F9.1020302@redhat.com> <41d65e62ce930c78bf56bdf74dd29124.squirrel@ssl.dlhnet.de> In-Reply-To: <41d65e62ce930c78bf56bdf74dd29124.squirrel@ssl.dlhnet.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Block Migration and xbzrle List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: lieven-lists@dlh.net Cc: Peter Lieven , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" On 10/02/2012 10:33 AM, lieven-lists@dlh.net wrote: > Orit Wasserman wrote: >> On 09/16/2012 01:39 PM, Peter Lieven wrote: >>> Hi, >>> >>> I remember that this was broken some time ago and currently with >>> qemu-kvm 1.2.0 I am still not able to use >>> block migration plus xbzrle. The migration fails if both are used >>> together. XBZRLE without block migration works. >>> >>> Can someone please advise what is the current expected behaviour? >> XBZRLE only work on guest memory so it shouldn't be effected by block >> migration. >> What is the error you are getting? >> What command line ? > > Meanwhile I can confirm that it happens with and without block migration. > I I observe 2 errors: > a) > qemu: warning: error while loading state section id 2 > load of migration failed > b) > the vm does not enter running state after migration. > > The command-line: > /usr/bin/qemu-kvm-1.2.0 -net > tap,vlan=798,script=no,downscript=no,ifname=tap1 -net > nic,vlan=798,model=e1000,macaddr=52:54:00:ff:01:15 -drive > format=host_device,file=/dev/mapper/iqn.2001-05.com.equallogic:0-8a0906-d85f4e007-3f30017ce11505df-ubuntu-tools-hd0,if=virtio,cache=none,aio=native > -m 4096 -smp 2,sockets=1,cores=2,threads=1 -monitor > tcp:0:4002,server,nowait -vnc :2 -qmp tcp:0:3002,server,nowait -name > 'Ubuntu-Tools' -boot order=dc,menu=off -k de -incoming > tcp:172.21.55.34:5002 -pidfile /var/run/qemu/vm-250.pid -mem-path > /hugepages -mem-prealloc -rtc base=utc -usb -usbdevice tablet -no-hpet > -vga cirrus -cpu host,+x2apic,model_id='Intel(R) Xeon(R) CPU Migration with -cpu host is very problemtic, because the source and destination can have different cpu resulting in different cpu features. Does regular migration works with this setup? Can you try with a different cpu type? What are the source and destination /proc/cpuinfo output ? Cheers, Orit > L5640 @ 2.27GHz',-tsc > > Thanks, > Peter > >> >> Regards, >> Orit >>> >>> Thanks, >>> Peter >>> >>> >> >> >> > > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >