[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Block Migration and xbzrle
From: |
Peter Lieven |
Subject: |
Re: [Qemu-devel] Block Migration and xbzrle |
Date: |
Tue, 2 Oct 2012 11:30:07 +0200 |
Am 02.10.2012 um 11:28 schrieb Orit Wasserman:
> On 10/02/2012 10:33 AM, address@hidden 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 ?
The CPUs are identical, we also check if flags and cpu types match if cpu type
is set to host.
Regular migration does work.
BR,
Peter
>
> 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 address@hidden
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>