Hi, after a recent live backup done with a snapshot, blockcommit failed and a subsequent (manual) blockjob abort got stuck. Now we are unable to do basic operations on the virtual machine like if it was frozen and when issuing another command we see the following: $ virsh shutdown $domain error: Failed to shutdown domain $domain error: Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainBlockJobAbort) $ virsh blockcommit $domain --active --pivot error: Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainBlockJobAbort) $ virsh blockjob $domain --abort error: Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainBlockJobAbort) Houston, we've got a problem. We have roughly 16 hours to fix this. Any help is appreciated!

On 10/22/2017 02:04 PM, Dominik Psenner wrote: > Hi, > > after a recent live backup done with a snapshot, blockcommit failed and a > subsequent (manual) blockjob abort got stuck. Now we are unable to do basic > operations on the virtual machine like if it was frozen and when issuing > another command we see the following: > > $ virsh shutdown $domain > error: Failed to shutdown domain $domain > error: Timed out during operation: cannot acquire state change lock (held > by remoteDispatchDomainBlockJobAbort) > > $ virsh blockcommit $domain --active --pivot > error: Timed out during operation: cannot acquire state change lock (held > by remoteDispatchDomainBlockJobAbort) > > $ virsh blockjob $domain --abort > error: Timed out during operation: cannot acquire state change lock (held > by remoteDispatchDomainBlockJobAbort) > This looks like some API forgot to unset the job before returning. In that case, restarting libvirtd is the only option. If this happened on the latest release please do file a bug. Otherwise try with the latest release. Michal