From: Orit Wasserman <owasserm@redhat.com>
To: lieven-lists@dlh.net
Cc: Peter Lieven <pl@dlhnet.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Block Migration and xbzrle
Date: Tue, 02 Oct 2012 11:28:37 +0200 [thread overview]
Message-ID: <506AB3C5.9040109@redhat.com> (raw)
In-Reply-To: <41d65e62ce930c78bf56bdf74dd29124.squirrel@ssl.dlhnet.de>
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
>
next prev parent reply other threads:[~2012-10-02 9:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-16 10:39 Block Migration and xbzrle Peter Lieven
2012-09-16 10:39 ` [Qemu-devel] " Peter Lieven
2012-09-17 18:03 ` Orit Wasserman
2012-10-02 8:33 ` lieven-lists
2012-10-02 9:28 ` Orit Wasserman [this message]
2012-10-02 9:30 ` Peter Lieven
2012-10-02 9:30 ` Peter Lieven
2012-10-02 10:40 ` Orit Wasserman
2012-10-02 10:40 ` [Qemu-devel] " Orit Wasserman
2012-10-04 6:31 ` Peter Lieven
2012-10-04 6:31 ` Peter Lieven
2012-10-02 9:38 ` Paolo Bonzini
2012-10-02 9:38 ` [Qemu-devel] " Paolo Bonzini
2012-10-02 9:44 ` Peter Lieven
2012-10-02 9:44 ` [Qemu-devel] " Peter Lieven
2012-10-02 10:09 ` Paolo Bonzini
2012-10-02 10:09 ` [Qemu-devel] " Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=506AB3C5.9040109@redhat.com \
--to=owasserm@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lieven-lists@dlh.net \
--cc=pl@dlhnet.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.