I don't think "virsh shutdown" and "virsh destroy" are "triggers".
I think when the guest rebooted something went wrong and subsequent attempts to use "virsh shutdown" and "virsh destroy" fail. This morning the en-mass VM guest reboot was triggered by cron jobs inside the guests. I tried unsuccessfully to reproduce this on a VM host that only has a single VM guest. I'm still investigating if having several VM guests reboot at the same time is the trigger or not. -- 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
