Seems to be a related bug in libvirt: https://bugzilla.redhat.com/show_bug.cgi?id=1530346
My own data: lsb_release -d Description: Ubuntu 18.04.3 LTS libvirtd -v --version libvirtd (libvirt) 4.0.0 virsh list Id Name State ---------------------------------------------------- 8 … running virsh shutdown 8 error: Failed to shutdown domain 8 error: Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainSuspend) Excerpts from the bug at https://bugzilla.redhat.com/show_bug.cgi?id=1530346 : "I am able to reproduce with [libvirt] 3.7.0 but unable to reproduce with current master (v4.2.0-457-gda613819e9). … I'm running bisect now to see which commit fixed this." "My bisect points at this commit 72adaf2f10509c3682f2c65ffad4176e00e5a2fb (v4.1.0-rc1~337) which is supposed to fix this bug 1536461 which follows my investigation and suspicion. So basically, 4.1.0 is fixed, the problematic commit that introduced the bug is v3.4.0-rc1~119." Libvirt git for your convenience: https://libvirt.org/git/?p=libvirt.git ** Bug watch added: Red Hat Bugzilla #1530346 https://bugzilla.redhat.com/show_bug.cgi?id=1530346 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770295 Title: ceilometer compute cannot collection memory.usage meter for all vm in one compute node To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1770295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
