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
How do you access folders? I would like to change some files in custom components folder.
Hi all,
I have created the VM with the OVA qcow2 image and in the VNC windows it states it is all OK. But I can not open it. What could be wrong?
My first thought is, that the VM is running in the wrong IP range. Normally I am in the range of 192.168.178.xxx but this one runs with the IP 192.168.122.136/24
If this is the problem, how can I change the IP?
If that is not the problem, anny suggestions?
Hey, i don’t know if you have find the answer but be sure to be on
network: br0. With this network config you unraid should be exemple 192.168.178.1 and HA VM will be 192.168.178.2.
So your VM will have is own IP on your network.
Hi, yes, I solved the problem. But I had to use “vhost” as that network “adapter” is in the correct subnet.
But thank you for replaying and providing a solution 
Apologies for opening up this old thread, but seemed the best place to pose my questions. I have been running my VM successfully on an old hardware platform (HP Microserver Gen8) but that started having some hardware failures so I have swapped to a UGreen 4800Plus which is considerably newer hardware.
This has prompted me to look at the settings of the HAOS VM and there are a couple of settings I am curious about:
The Machine setting is still set to Q35-7.2. Is this still considered the optimal setting?
Also the USB Controller is set to 2.0 (EHCI) but I know at least one of the USB devices I pass through is USB3 capable.
Does anyone have any advice or suggestions for ensuring this runs optimally?
Thank you
You can use the latest Q35-9.2 - tested on an HPE Microserver Gen 10 Plus v2.
Doing so, however, might prevent the Supervisor from recognizing the installation as a fully-flegged “HomeAssistant OS” thus preventing access to add-ons.
If add-ons and other features of “HomeAssistant OS” are critical, then you must leave the “Q35-7.2” setting. This is also the case if you plan on restoring from a previous backup.
Yes, if your server is USB-3 capable (and BIOS enabled for the ports you want to use)1 then you can use the “3.0 QEMU XHCI”; in this specific instance (UNRAID) the hypervisor will have better compatibility with the QEMU XHCI controller.
1: in some servers, like the HPE Microserver, the use of USB 3.0 can be enabled or disabled trough BIOS when needed to mitigate certain specific user-case scenarios where interference mitigation takes priority on transfer speed.
Edited to add better information about “Machine” setting regarding “Q35-xx” compatibility.
