aminux

Great, Thanks. I see that on the changelog Change Log September 2026Fixes the VM service sometimes failing to start after a reboot. It happened when this container started first. If you already have it installed, its web page shows you the one setting to change. Fixes new installs failing on servers with no UEFI VMs yet. Open Home Assistant goes to the port Home Assistant confirms, even when something else like Emulated Hue is using port 80. Asks GitHub for the release list far less often. When GitHub is busy or can't be reached, it uses the last list it saved. After a reboot, watched VMs start again as soon as the VM service is up, and the Home Assistant icon stays next to the VM rather than going back to the generic one. Needs Unraid 7.0 or newer.

ok, so if I just delay the start of that docker it would work. But after all, I think I am going to try to move everything to the docker from linuxserver, as I think it is more efficient, and if I see the need to go back to the VM, I know now how. Thank you all for the support here.

Would it work if the Docker starts with a delay of lets say 5min? what is the boot sequence, does VM starts at the same time as Docker?

indeed, a VM or a docker with Homeassistant it is less troublesome than the inabox stuff

ohh Woo, Thank you JorgeB That was completely spot on! I even got to understand what the problem was. The original file directly started, so once I got the VM running I had to change nothing. I was expecting more from that docker and the management of the VM from there, as SpaceInvaderOne is someone with quite a bit of traction, so many issues might face similar issues (or already did). I posted there as well about the issue, as you suggested, so I hope this helpful for other users. I will set as well the VM disks to the Cache and set the backup plugin job to back it up overnight. For other users that might want to try something different: You can try the homeassistant docker, and if you need HACS, then you can use this guide: https://www.simplysmart.house/terminal From what I see, the VM makes it look easier to install HACS and the Apps, but the Apps seems unnecessary if you have docker in your unraid, and the HACS can be easily installed but with a "workaround"

Hi SpaceInvaderOne, Thank you very much for the introduction to the Homeassistant and the docker template. I have an issue that other unraiders had (https://forums.unraid.net/topic/200692-homeassistant-in-a-box-v3-vm-failures/). The problem is related to when the docker starts and when the VM, so with restarts of UnRaid. It would be great if a fix could be provided, I am sure it will remove headaches for many people (mine took some time to cure :-) )

Hi There, I installed with some effort the Homeassistant and managed to make it run, made some automations at home and then restarted the unraid server today. I am using the docker HomeAssistant_inabox_v3 Somehow it gave me a failure to start the VMs (Libvirt Service failed to start), so I read some posts with similar issue, suggested to remove the libvirt.img file (with the check box function), - oh damm, what a stupid I am that did not take a backup first! - , and still not working, changed the path to where system is (cache) - /mnt/cache/system/libvirt/libvirt.img - for the image and managed to start the VM services, created a new VM using the docker, and then it got stuck here (before it was going through the /mnt/user/system path). Side note: If you are having a similar issue, before deleting anything, try to change the libvirt.img directory to the drive, and restart with Docker not enabled, once the VM services start, start the Docker. I realized that with Docker enabled, the VM start gives me issues. (might that be another issue that i have or give some clues?) VirshError: virsh start 'Home Assistant' failed (1): error: Failed to start domain 'Home Assistant' error: Failed to create file '/etc/libvirt/qemu/nvram/9b188b6c-ddba-415b-bf41-9656acb37b80_VARS-pure-efi.fd.new': No such file or directoryafter that, gave the whole qemu directory write access to test, recreate the docker, removed and create a new VM and the same issue occurred. I left it back to read only because I dont like the idea of a docker having write access to an unraid system directory without knowing why that should change. Anyways, I am attaching the system diagnosis with the hope that someone can guide me on what I need to do here and why the failures. Even better if somehow the is a way to recover that image that I had, I installed HACS and some community repositories to do some automations very helpful to me. I want as well to understand why should i give the drive path directly instead of the user path, i though that was not a good practice, but more than anything, I want to solve this problem and get some insights of best practices on this type of VM to avoid loosing all the automations that I already prepared and did. Thank you in advance for helping me with this issue. unraid-diagnostics-20260925-2349.zip

Rebooting did not solve the problem, obviusly that was one of the first steps to do, for all the devices involved. It was a factory reset. Anyways, from one side, more tools to diagnose problems and perform automatic setups do help, however the complexity of the net and subnets and the applications running on all those layers make it hard to find out where the problem is.

ok, so for anyone having a similar issue, I had to hard-reset my router set-up, and then it started all working as expected. Very weird, I have no idea what actually happened there, but it was not an issue with Unraid settings, even though the troubleshooting made me read documentation and rethink it.

Thank you so much for looking in to this and giving me some insights. I moved the cable to the 1Gbps port and it did nothing different, but I will tried a new cable in a new port just to discard the isssue there. How do I force the card to go 1Gb? I have done some changes to simplify how I have the network set-up, so I am attaching new diagnostics. Good point regarding SSH, I have activated it. The IP i had it reserved via router, with the MAC address of the old port, recently changed to the new card. Regarding reaching the IP of my server, I have tried with different clients and different OS without difference. I have ping the IP from the router directly, through the very simple diagnostics tools there, and then, it responds, both the server and the pihole. Thing is, besides opening ports in my router for the qbittorrent client, i didnt change anything or got a software update, but I think you have a good point, the issue might be there, as we have discarded the docker as the current issue, that the pi-hole has a similar issue invite to think that there might be the issue. My network setting is a following Internet modem from the ISP, then to it (ips 192.168.1.x) connected to WAN Port 10Gbps, with DMZ to the ISP to manage ports, Asus router, with unraid and pihole, and the whole WiFi with a another ASUS in Mesh mode. (ips 192.168.50.x) being unraid on 100 and the pihole on 175 connected to a WAN port 1Gbps another router with IoT things and other stuff I wan to keep separated from my core network (ips 192.168.1.x) unraid-diagnostics-20260916-0938.zip

Hi There, I am in need of help because I am not getting anywhere. Currently I can access my server via its IP only via tailscale, which is not ideal. I have a the System data and Appdata in a cache drive. In order to backup the data, I use the Appdata Backup plugin, which is configured to update the dockers afterwards. I notice that the network settings for my docker was a bit mess up, I think it has to do with some of the docker updates, but I am not 100% sure. In order to troubleshoot, I stopped docker, restarted the server, the router, tried to flush ARP tables and did other things that found in the forum, in reddit, etc, but nothing did work. My knowledge here is limited, but I have the feeling that I have conflicting IPs from the docker and the server. Another thing that I notice is that my pi-hole (outside unraid) became as well unreachable. The Fix Common problems did not get me anywhere, it is suggesting to update tailscale but I dont want to do it until i fix the bigger issue. As well, a month ago or so, I installed a second Ethernet card, because it could connect to my router at 2.5Gbps instead of the 1Gbps that the integrated Ethernet card offered. I have tried to connect to that one instead, but it neither worked. I am attaching the diagnostics with the hope that someone can help me with this. If I turn on docker, I can access to the different apps via the ip:port but again, only via tailscale. It seems that the torrents client, for instance, can even generate traffic. I have tried to change some network settings, but the VM manager does not allow me to deactivate it (via GUI, i guess there is a way via terminal). Maybe if i need to change something there, someone could guide me how to force it (I dont have VMs anyways) Thank you in advance or any insights you might have unraid-diagnostics-20260915-2233.zip

I was reading this and I was not able to solve it with the indications in the forum, however somehow I managed, the threat is a bit old, but just in case it helps someone. The linuxserver template has already a WebUI and a WEBUI_PORT. Those two needs to have the new port, HOWEVER of you click on Edit for the WebUI, you will see that 8080, the container port is greyed out, so you cannot change it. What worked for me was to delete the variable WebUI and then create it again with the Container port that I wanted to have. Another thing that I changed was in Advace view, once more change the PORT manually to the one I wanted to have. I hope this helps if someone faces the same issue

Thank you, it did solve the issue!

Hello. Already with 6.12 I tried to create and install Ubuntu in a virtual machine, but never managed to do it as it gets stuck and not sure why. The config is: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Ubuntu</name> <uuid>cd9b2251-d11e-0488-22ff-b94036ff40b3</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux" webui="" storage="default"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-9.0'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/cd9b2251-d11e-0488-22ff-b94036ff40b3_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' clusters='1' cores='1' threads='1'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='utc'> <timer name='hpet' present='no'/> <timer name='hypervclock' present='no'/> <timer name='pit' tickpolicy='delay'/> <timer name='rtc' tickpolicy='catchup'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback' discard='unmap'/> <source file='/mnt/user/domains/Ubuntu/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/ubuntu-24.04.1-desktop-amd64.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/VM/'/> <target dir='/mnt/unraid'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:71:34:5f'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' sharePolicy='ignore'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> </domain> When I start the machine, I select "Try or Install Ubuntu" (tried as well with safe Graphics, same results), then it starts I select some options to do the installation. Stucks here, but does not really says much.. it just keeps there Any idea? Thanks in advance.

Thank you, it worked!