Well they helped me out as my systems automation took out my hassio instance… as designed but not intended, so I just figured I’d throw hassio on unraid
hi! Is there any way to passthrough a share to HA?
I have been trying for days to get this to work. I can get as far as the Home Assistant is Preparing window. When I run ‘supervisor log’ I get a ton of errors about ‘supervisor has no internet connection’. I’ve fiddled around with DNS, Nameservers, gateways and have no idea why the supervisor can’t connect. I can Ping to external sites from the VM with no issue. At a complete loss and close to giving up. I just wanna free up a Raspberry Pi for another project.
I think you’ve got the wrong image. I had this issue yesterday, there are a couple of versions of the qcow2 file, I tried the generic and got this message. I downloaded the next one down the list (can’t remember the name, but I think it was the next qcow2) and once I changed the drive it fired right up.
That’s true, I found out but forgot to update here.
Hi all, Has anyone encountered issues with HA VM install on Unraid over the last few days? I followed the instructions as per above and the system is running. However after a while with the two pinned CPU cores the unraid host locks into a 100% CPU usage. When i quit the HA VM it sheds processes and the other apps including docker containers and host returns to functioning. I have posted the above issue on the unraid forum as well as there is another HA user there that installed around the same time as me and has the same issue. Any assistance would be amazing.
Yeah, don’t take the upper one saying “aarch64”! We need amd64 and not ARM builds here 
Shouldn’t instructions how to install the guest agent be included?
Thanks for that - very helpful. For Germany I selected the German keyboard and use the plugin "
Dynamix File Manager" to create the directory and upload the “qcow2” file. No need to export that share.
What about the USB port? I selected 3.0 qemu XHCI and it works fine with HmIP-RFUSB and HA SkyConnect (only Zigbee). What is “recommendet”?
I installed unraid on a Zimaboard 832 with 4 cores and 8 GB RAM. CPU2, CPU3 are pinned to Home Assistant and initial memory is set to 2GB. That work fine for my system with about 100 devices, 25 integrations (among them ZHA, HomematicIP, Shellys, Tibber, Node-RED, …) and 4 Add ons (Ring to MQTT, Samba, Google Drive backup, SSH). On Unraid I serve my files via SMB and use Docker container for Node-RED, Duplicati, Grocy, Mosquitto, Dashy, Uptime kuma)
Thank you, worked a treat
Did you get anywhere with this? I am now experiencing the exact same behaviour.
Can’t pinpoint any changes that could have caused it.
Hello.
I had the same problem but with the help of a friend’s settings, I managed to overcome the issue.
In the HA VM settings (in Unraid), activate the “XML VIEW” mode and validate the following disk parameter:
<disk type='file' device='disk'>
<driver name='quem' type='qcow2' cache='writeback'/>
<source file='/mnt/user/domains/homeassistant/haos_ova-11.4.qcow2'/>
<target dev='hdc' bus='sata'/>
<serial>vdisk1</serial>
<address type='drive' controller='0' bus='0' target='0' unit='2'/>
</disk>
O type must be qcow2 and not raw!
I hope this helps
3 Likes
I had to extract the image as following: unxz haos_ova-12.2.qcow2.xz
Then I could use the haos_ova-12.2.qcow2 image with the XML above
I really struggled with this and ended up writing a full guide with explanations and screenshots on how to fully set up Home Assistant on Unraid:
I haven’t had any luck running the qcow2 image. In @DrMor’s post they suggest avoiding the aarch release, but in the GitHub Releases page there is only one qcow image haos_generic-aarch64-13.1.qcow2.xz as of the date of this post. I can’t get past the UEFI prompt in unRAID with this image, but I can with haos_generic-x86-64-13.1.img.xz. The problem is that it doesn’t include the qemu-guest-agent which makes it impossible to shutdown the VM from the host system.
I was using the incorrect image for my system’s architecture (x86-64). I downloaded the ova qcow2 image for x86-64.
BTW, if you try creating the VM with the ARM image you can’t just swap the boot image to the correct one and start. It was easier for me to create a new VM from scratch.
This is the one you need:
https://github.com/home-assistant/operating-system/releases/download/13.1/haos_ova-13.1.qcow2.xz
Thank you - I was pulling my hair out trying to find this.
Sometimes you have to click the expand arrow to see the ova version