[Qemu-devel] Problems with live migration

[Qemu-devel] Problems with live migration

[Toni F. [ackstorm]]

Hi all,

I have working with Openstack Folsom and with Glusterfs as shared 
storage for /instances. All working fine, but when i'm trying to use 
"nova live-migration":

2013-03-07 18:33:42 3140 ERROR nova.virt.libvirt.driver [-] [instance: 
773164b5-5e5c-4328-a762-d91f50f2ac33] Live Migration failure: Timed out 
during operation: cannot acquire state change lock

I know that the real command that openstack executes

virsh migrate --live instance-00000036 qemu+ssh://nova-compute-lnx001/system

When i execute that command the same error is showed

error: Timed out during operation: cannot acquire state change lock

Any idea about this error?

Thanks a lot
Regards

Re: [Qemu-devel] Problems with live migration

[Eric Blake]

[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]

On 03/13/2013 12:01 PM, Toni F. [ackstorm] wrote:
> Hi all,
> 
> I have working with Openstack Folsom and with Glusterfs as shared
> storage for /instances. All working fine, but when i'm trying to use
> "nova live-migration":
> 
> 2013-03-07 18:33:42 3140 ERROR nova.virt.libvirt.driver [-] [instance:
> 773164b5-5e5c-4328-a762-d91f50f2ac33] Live Migration failure: Timed out
> during operation: cannot acquire state change lock
> 
> I know that the real command that openstack executes
> 
> virsh migrate --live instance-00000036
> qemu+ssh://nova-compute-lnx001/system
> 
> When i execute that command the same error is showed
> 
> error: Timed out during operation: cannot acquire state change lock
> 
> Any idea about this error?

That error is from libvirt, not qemu, so you are asking on the wrong
list.  But when asking on the libvirt list, be sure to mention what
version of libvirtd is running on nova-compute-lnx001.  Meanwhile, when
libvirtd gets in a stuck lock state, you can often restart libvirtd to
get past that point, with no negative consequences to your running qemu
guests.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

Re: [Qemu-devel] Problems with live migration

[Toni F. [ackstorm]]

Hi Eric,

Thanks for your response, i will ask in the libvirt list.

Unfortunatly, restarting libvirt don't solves the problem.

Regards.

On 13/03/13 21:55, Eric Blake wrote:
> On 03/13/2013 12:01 PM, Toni F. [ackstorm] wrote:
>    
>> Hi all,
>>
>> I have working with Openstack Folsom and with Glusterfs as shared
>> storage for /instances. All working fine, but when i'm trying to use
>> "nova live-migration":
>>
>> 2013-03-07 18:33:42 3140 ERROR nova.virt.libvirt.driver [-] [instance:
>> 773164b5-5e5c-4328-a762-d91f50f2ac33] Live Migration failure: Timed out
>> during operation: cannot acquire state change lock
>>
>> I know that the real command that openstack executes
>>
>> virsh migrate --live instance-00000036
>> qemu+ssh://nova-compute-lnx001/system
>>
>> When i execute that command the same error is showed
>>
>> error: Timed out during operation: cannot acquire state change lock
>>
>> Any idea about this error?
>>      
> That error is from libvirt, not qemu, so you are asking on the wrong
> list.  But when asking on the libvirt list, be sure to mention what
> version of libvirtd is running on nova-compute-lnx001.  Meanwhile, when
> libvirtd gets in a stuck lock state, you can often restart libvirtd to
> get past that point, with no negative consequences to your running qemu
> guests.
>
>    


-- 

Toni Fuentes Rico
toni.fuentes@ackstorm.es
Administración de Sistemas

Oficina central: 902 888 345

ACK STORM, S.L.
ISO 9001:2008 (Cert.nº. 536932)
http://ackstorm.es

Este mensaje electrónico contiene información de ACK STORM, S.L. que es privada y confidencial, siendo para el uso exclusivo de la persona(s) o entidades arriba  mencionadas. Si usted no es el destinatario señalado, le informamos que cualquier divulgación, copia, distribución o uso de los contenidos está prohibida. Si usted ha recibido este mensaje por error, por favor borre su contenido y comuníquenoslo en la dirección ackstorm@ackstorm.es