Hello,

every time I restart the unraid box the VM service fails to start. I have to stop it go to var/run/libvert and delete all the files in the dir then I can start the vm ok. How can this be fixed.

Thankyou.

vms-diagnostics-20261009-1510.zip

All containers updated? Seems to be homeassistant_inabox_v3 causing the issue, which was supposedly fixed some time ago. https://forums.unraid.net/topic/200692-homeassistant-in-a-box-v3-vm-failures/#comment-1637640

Edited Friday at 08:38 PM2 days by Kilrah

Kilrah is right. Your diagnostics show HomeAssistant_inabox_v3 causing this.

On both boots in the log, Docker starts that container in the same second the VM service starts, and libvirt then fails with:

Failed to bind socket to '/var/run/libvirt/libvirt-sock': Address already in use

The container maps the libvirt socket file itself. When the container starts first, that socket doesn't exist yet, so Docker creates a folder with that name. libvirt can't create its socket over that folder, which is why deleting the folder fixes it until the next reboot.

The template was fixed on 2026-09-27, but only for new installs. Updating the container doesn't change the setting on an existing one, so you need to change it yourself once:

1. Edit the HomeAssistant_inabox_v3 container.

2. Change the libvirt path (host and container) from /var/run/libvirt/libvirt-sock to /var/run/libvirt and apply.

3. Stop the VM service, delete the leftover folder in /var/run/libvirt one last time, and start the VM service again.

After that, the VM service should start normally after a reboot, whichever service starts first. You don't need to touch libvirt.img.