[libvirt-users] Timed out during operation: cannot acquire state change lock

Hi, I am looking for help to troubleshoot: node002 ~ # virsh virsh # list Id Name State ---------------------------------- 1 dom001 paused virsh # resume dom001 error: Failed to resume domain dom001 error: Timed out during operation: cannot acquire state change lock virsh # then I've looked into /var/run/libvirt/qemu node002 ~ # ls -l /var/run/libvirt/qemu/ total 8 -rw------- 1 root root 5 Jan 10 17:41 dom001.pid -rw------- 1 root root 2785 Jan 10 17:47 dom001.xml node002 ~ # ps ax|grep 16681 16681 ? Sl 6:07 /usr/bin/qemu-system-x86_64 --enable-kvm -S -M pc-0.13 -enable-kvm -m 512 -smp 2,sockets=2,cores=1,threads=1 -name dom001 -uuid 357d1d40-31a1-ca62-da4b-5c6f9f5f1399 -nodefconfig -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/dom001.monitor,server,nowait -mon chardev=monitor,mode=control -rtc base=utc -boot c -kernel /srv/kernels/kernel-2.6.36-gentoo-r5-2 -append console=tty1 root=/dev/vda -device lsi,id=scsi0,bus=pci.0,addr=0x6 -drive file=/dev/vg_node002/dom001_root,if=none,id=drive-virtio-disk0,boot=on,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0 -drive file=/dev/vg_node002/dom001_swap,if=none,id=drive-virtio-disk1,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk1,id=virtio-disk1 -netdev tap,fd=61,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:29:98:f8,bus=pci.0,addr=0x7 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -vnc 127.0.0.1:0 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 I have used virt-manager to start the machine (KVM+QEMU), then I tried to pause the machine and the virt-manager was gray for long time so I killed it. Now I cannot resume the machine. Any tips? Regards, Robert

The 11/01/11, Robert Šmol wrote:
Hi,
I am looking for help to troubleshoot:
node002 ~ # virsh virsh # list Id Name State ---------------------------------- 1 dom001 paused
virsh # resume dom001 error: Failed to resume domain dom001 error: Timed out during operation: cannot acquire state change lock
You may have hit a bug corrected by this patch http://comments.gmane.org/gmane.comp.emulators.libvirt/28718?set_cite=hide I would check your libvirt version has this bugfix and upgrade if needed. I don't remember the version having this fix, sorry. -- Nicolas Sebrecht

The 11/01/11, Nicolas Sebrecht wrote:
The 11/01/11, Robert Šmol wrote:
Hi,
I am looking for help to troubleshoot:
node002 ~ # virsh virsh # list Id Name State ---------------------------------- 1 dom001 paused
virsh # resume dom001 error: Failed to resume domain dom001 error: Timed out during operation: cannot acquire state change lock
You may have hit a bug corrected by this patch http://comments.gmane.org/gmane.comp.emulators.libvirt/28718?set_cite=hide
I would check your libvirt version has this bugfix and upgrade if needed. I don't remember the version having this fix, sorry.
The fix I'm talking about is included in v0.8.5. -- Nicolas Sebrecht

Hi, thanks for quick reply, however it seems I am running node002 ~ # libvirtd --version libvirtd (libvirt) 0.8.6 This is on funtoo/gentoo but I do not see any custom patches applied. Shall I open a bug report, how to troubleshoot? Robert <https://pm011sma.intranet.fw:2381/chphead.php?chppath=Logs%3A%3ASystem%20Management%20Homepage&chppage=System%20Management%20Homepage%20Log&chpurl=/errlog.php%3Flog%3Dhpsmhlog&chptarget=undefined#> On 01/11/2011 03:51 PM, Nicolas Sebrecht wrote:
The 11/01/11, Nicolas Sebrecht wrote:
The 11/01/11, Robert Šmol wrote:
Hi,
I am looking for help to troubleshoot:
node002 ~ # virsh virsh # list Id Name State ---------------------------------- 1 dom001 paused
virsh # resume dom001 error: Failed to resume domain dom001 error: Timed out during operation: cannot acquire state change lock You may have hit a bug corrected by this patch http://comments.gmane.org/gmane.comp.emulators.libvirt/28718?set_cite=hide
I would check your libvirt version has this bugfix and upgrade if needed. I don't remember the version having this fix, sorry. The fix I'm talking about is included in v0.8.5.

The 11/01/11, Robert Šmol wrote:
Hi, thanks for quick reply, however it seems I am running
node002 ~ # libvirtd --version libvirtd (libvirt) 0.8.6
This is on funtoo/gentoo but I do not see any custom patches applied. Shall I open a bug report, how to troubleshoot?
You might rather start a thread upstream at the developper mailing list (libvirt-list). -- Nicolas Sebrecht
participants (2)
-
Nicolas Sebrecht
-
Robert Šmol