I think this just started happening recently. I've noticed after a recent hard reboot that the VM no longer auto starts but I haven't had any problems starting it manually.

 

libvirt log-

2021-12-17 01:40:16.602+0000: 15020: info : libvirt version: 6.5.0
2021-12-17 01:40:16.602+0000: 15020: info : hostname: Brunnhilde
2021-12-17 01:40:16.602+0000: 15020: warning : networkNetworkObjTaint:5292 : Network name='default' uuid=2214f59d-018d-4270-9f9c-550be516a722 is tainted: hook-script
2021-12-17 01:40:17.475+0000: 15020: warning : qemuDomainObjTaint:6075 : Domain id=1 name='Debian' uuid=9ea9f033-d785-8237-cc67-201e243543ae is tainted: high-privileges
2021-12-17 01:40:17.475+0000: 15020: warning : qemuDomainObjTaint:6075 : Domain id=1 name='Debian' uuid=9ea9f033-d785-8237-cc67-201e243543ae is tainted: host-cpu
2021-12-17 01:40:18.159+0000: 15004: error : virNetSocketReadWire:1826 : End of file while reading data: Input/output error
2021-12-17 01:55:15.872+0000: 15931: error : qemuMonitorIO:578 : internal error: End of file from qemu monitor
2021-12-17 03:18:36.263+0000: 25203: info : libvirt version: 6.5.0
2021-12-17 03:18:36.263+0000: 25203: info : hostname: Brunnhilde
2021-12-17 03:18:36.263+0000: 25203: warning : qemuDomainObjTaint:6075 : Domain id=1 name='Debian' uuid=9ea9f033-d785-8237-cc67-201e243543ae is tainted: high-privileges
2021-12-17 03:18:36.263+0000: 25203: warning : qemuDomainObjTaint:6075 : Domain id=1 name='Debian' uuid=9ea9f033-d785-8237-cc67-201e243543ae is tainted: host-cpu

 

 

brunnhilde-diagnostics-20211216-2227.zip

Well, after some searching I see that the high-privilege and host-cpu warnings are to be expected in unRAID so I guess that leaves me back at square one as far as the vm not auto starting???

Is the VM relying upon some custom network to be up and running first?

No. The only thing passed through is a usb hub for insteon.

It looks like this is only happening on array stop/start. The vm started as expected on a server reboot.