Today two VM hosts running kernel 2.6.38-11, one with with 14 guests and another with 53 had scheduled reboots of the many of their guests.
On the VM host with 14 guests, 11 rebooted. On the one with 53 guests, 48 rebooted. VM guests that automatically rebooted this morning at 6:30 AM via at(8) hung instead of rebooted. All of the VM guests were rebooting from kernel 2.6.38-11 into 2.6.38-12 Not all of the VM guests on the hosts were scheduled to be rebooted. "virsh shutdown" and "virsh destroy" appeared to always hang. After using "kill -9" on the PID of the VM guest "virsh start" for that guest worked every time. Initially on the VM hosts "virsh list" would output some VM names then hang. After enough VM guests were reset via "kill -9" (but before all of them were) "virsh list" became able to run to completion. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/882579 Title: Some Commands return: "Timed out during operation: cannot acquire state change lock" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/882579/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
