libvirt_up = 0 when one or more VM get qemuProcessReportLogError upon creation

[BenjaminS-81]

Hi all,

We have recently experienced the following error:

Jul 20 06:13:31 server1 libvirtd[47045]: 2022-07-20 06:13:31.181+0000: 47045: error : qemuProcessReportLogError:1914 : internal error: qemu unexpectedly closed the monitor: 2022-07-20T06:13:31.090440Z qemu-system-x86_64: -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1: Failed to get "write" lock
Jul 20 06:13:31 server1 libvirtd[47045]: 2022-07-20 06:13:31.181+0000: 47049: error : qemuProcessReportLogError:1914 : internal error: process exited while connecting to monitor: 2022-07-20T06:13:31.090440Z qemu-system-x86_64: -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1: Failed to get "write" lock

Jul 20 07:01:27 server1 libvirt_exporter[94868]: 2022/07/20 07:01:27 Failed to scrape metrics: virError(Code=38, Domain=10, Message='Unable to read from monitor: Connection reset by peer')

• While the above happened, the libvirt_exporter flagged libvirt_up to be == 0
• What we understand from it is that if even 1 VM fails to be created due to this error, then libvirt_up will be 0
• During this time, except for this specific failure, libvirt/virsh was working totally fine.

Please let us know if any more information is needed.