Re: [libvirt-users] virsh migrate results in error: Timed out during operation: cannot acquire state change lock

>> I issue this command on server one: >> sudo LIBVIRT_DEBUG=1 virsh migrate --live --copy-storage-all i00cn1011 >> qemu+ssh://user@computer2/session> debug.log 2>&1 > Based on IRC conversations, I'm assuming you already made sure that > computer2 already sees all the same disk image files, with the same > sizes, as are present on computer1 (the contents need not be identical, > since that is what --copy-storage-all is supposed to fix, but libvirt > currently does not pre-create the files on the destination and leaves > the user to do so instead - patches to fix that are welcome). Well, are you saying I should copy the data from computer1 to computer2 before using virsh migrate? I only created an identical LVM partition with the same name and path. I did not copy anything.

> You may want to upgrade to 0.9.9 (stable release) or 0.9.10-rc2 (release > candidate for next week's release) on both machines, to try and get bugs > that have been fixed in the meantime out of your way. You can safely > upgrade libvirt even while your VM continues to run. Are you sure there is no problem in me upgrading libvirt on the main computer?

If so I'll give it a try. >> Does anyone know what the problem may be and how to solve it? > At any rate, when older libvirtd hits the 'cannot acquire state change > lock' bug, the only solution is to restart libvirtd (again, a safe > operation; your guest will continue to run in the meantime). You mean I should restart libvirtd on both computers?