On Tue, Jun 11, 2019 at 19:19:05 +0200, Lentes, Bernd wrote: [...]
Hi,
Hi,
it happened again. Following the log of my script it started on 8th of june at 5:59:09 (UTC+2) to blockcommit the domain. These are the related lines in libvirtd.log: ===================================================
Thanks for comming back to me with the information. Unfortunately this is not a full debug log but I can try to tell you what I see here:
2019-06-07 20:30:57.170+0000: 30299: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor 2019-06-08 03:59:17.690+0000: 30299: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor
So this looks like qemu crashed. Or at least it's the usual symptom we get. Is there anything in /var/log/libvirt/qemu/$VMNAME.log?
2019-06-08 03:59:26.145+0000: 30300: warning : qemuGetProcessInfo:1461 : cannot parse process status data 2019-06-08 03:59:26.191+0000: 30303: warning : qemuGetProcessInfo:1461 : cannot parse process status data 2019-06-08 03:59:56.095+0000: 27956: warning : qemuDomainObjBeginJobInternal:4865 : Cannot start job (destroy, none) for domain severin; current job is (modify, none) owned by (13061 remoteDispatchDomainBlockJobAbort, 0 <null>) for (38s, 0s)
And this looks to me as if the Abort job can't be interrupted properly while waiting synchronously for the job to finish. This seems to be the problem. If the VM indeed crashed there's a problem in job waiting apparently. I'd still really like to have debug logs in this case to really see what happened.