On 9/26/23 10:16, stan via users wrote:
upgraded to f39 beta and the problem was cured. Sledgehammer approachOn Mon, 25 Sep 2023 10:12:46 -0400 Robert McBroom via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:Power outage dropped my f38 system while a virtual Rawhide system was running. On restart the virtual machine is paused and none of the virt-manager shutdown, reset or delete work. It wasn't supposed to come up on a host restart. What can be done to clear the lock? Error resetting domain: Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainCreate) Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn ret = fn(self, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/share/virt-manager/virtManager/object/domain.py", line 1393, in reset self._backend.reset(0) File "/usr/lib64/python3.11/site-packages/libvirt.py", line 2408, in reset raise libvirtError('virDomainReset() failed') libvirt.libvirtError: Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainCreate)Was curious, so did some searching. Not familiar with qemu or libvirt, so might or might not help you. This seems to have happened in the past, as well. What I can glean from this bug report is that libvirt and qemu being out of synch caused it. https://bugzilla.redhat.com/show_bug.cgi?id=1530346 This bug report in arch seems to support that it is a mismatch. https://bugs.archlinux.org/task/63516 Both of these are older, so it might be a regression because something else was fixed. You could try reinstalling qemu on the host. One comment mentioned restarting libvirt was successful. A really old link, but it sounds a lot like your problem, so the solution might still work. https://stackoverflow.com/questions/16763240/libvirt-cannot-stop-reboot-force-shutdown-or-destroy-guest
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
