So after a restart of the unraid box it tells me failed to start libvert do to /var/run/libvert files are stuck in no mans land only way to get it started is to stop the libvgert service go and manully delete all the files then restart it. This just started too.

what can be done to get this started ok after a restart?

vms-diagnostics-20260907-1419.zip

Had something similar. I had to disable vm and docker. Then enable vm first and docker second in that order. Then it worked.

The diagnostics suggest that this is being caused by the third-party HomeAssistant_inabox_v3 container.

The container starts before VM Manager and bind-mounts /var/run/libvirt/libvirt-sock. Because the socket does not exist yet, Docker creates a directory at that path. Libvirt then cannot create its socket and fails with Address already in use.

Please disable autostart for HomeAssistant_inabox_v3 and reboot. Make sure that VM Manager starts first, then start the container manually.

There is no need to recreate libvirt.img. The diagnostics show that the existing image and VMs start correctly after the socket conflict is removed.

ok will do that