On Thu, Sep 09, 2021 at 12:30:53AM +0000, Leek, Jim wrote:
> Here's the error I sometimes get on checkpoint/restore. It just happened again. In this test I had at least a 40 second break between checkpoint and restore, so extra sleep doesn't seem to help much.
>
> Error unpausing domain: Timed out during operation: cannot acquire state change lock (held by monitor=qemuDispatchDomainMonitorCommand)
>
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
> callback(asyncjob, *args, **kwargs)
> File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
> callback(*args, **kwargs)
> File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 66, in newfn
> ret = fn(self, *args, **kwargs)
> File "/usr/share/virt-manager/virtManager/object/domain.py", line 1312, in resume
> self._backend.resume()
> File "/usr/lib64/python3.6/site-packages/libvirt.py", line 2174, in resume
> if ret == -1: raise libvirtError ('virDomainResume() failed', dom=self)
> libvirt.libvirtError: Timed out during operation: cannot acquire state change lock (held by monitor=qemuDispatchDomainMonitorCommand)
This suggests that the previously executed 'qemu-montor-command' has not
finished running yet.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
