can someone point me to the benefits of running on a VM over a docker. I get that you don’t get the supervisor, but are the actual limitations on what you can do with Home Assistant?
No limitations. If you run the Home Assistant container from the Unraid App store (not the supervisor container…that’s a mess) you have a nice, fast instance of Home Assistant Core and you can use the rest of the UnRaid app store as your “addon store”.
2 Likes
Yes I say most dockers (addons) are in the unraid apps store already if your running unRAID you probably can add all the apps you need rather than using the supervisor.
Been running for a couple of days and its gets not acceable after some time, Sometimes it runs like 1 day sometimes like a couple of hours. Cant see anything strange in log.
Anyone else got this?
I mean with the beta qcow2.
Is it possible to resize the qcow2 image AFTER you’ve had an instance of HA running for months?
I dedicated 26GB originally, but need more space. Can I just run this to increase it by 10GB?
sudo qemu-img resize /mnt/user/domains/hassos_ova-3.3.qcow2 +10GB
You can use the UnRaid UI to allocate more (Shut down the HA instance first from supervisor > system > Host card first)
Click on the name of the VM, which expands the details, and then change the capacity and hit enter. When you start the VM again it will recognize the new space.
5 Likes
OMG… that is the worst UI ever. I had no idea! thanks.
Been running the Beta for a while no problems until I made a reboot. Added more disk. Now its not booting and the VNC says Cleanup of temporary directories and its been running for like 30 mins.
Any idea what that is?
Big problems.
Had to restore my cache drive and therefore I did a new install of hassio with the cqow2 file 4.10.
It installed fine but I’m unable to restore from backup. It’s like it do not restore.
I says reconnecting and I wait like 20 min then the login comes up and I uses my regular login. Wrong name… empty cache still the same … stop vm and start still can’t login.
Tested the dummie login that I used just to access and install samba add on. Then I come in but it’s a fresh install. Not the the restored.
Any ideas.
Did run cqow2 version 4.8 before the beta one and it worked.
Kind of panicking that all is lost. I have backups running every night.
Anyone else tried the 4.10 version and made a successfull restore?
For the VM machine type, is there a reason not to choose the latest (Q35-4.2) over what is stated in the instructions in the first post (Q35-2.11)?
The snapshots contain no system data. They are simply archived files consisting of the config directory and the other default shared directories and then each addon’s data directory.
You could check the .tar file to confirm what is in there.
No, that’s just what was latest in the list at the time. I’ll edit that.
1 Like
My unraid server is running on Intel Xeon E3-1246v3 3.5ghz CPU with 32GB of RAM.
Right now I have the VM assigned 32GB of vDisk, 2GB of RAM and 1 logical core (cpu 0 / 4):
I’ve noticed that during parity check, the VM slows to a crawl. The HA dashboard will load, but take forever. As soon as parity check is over, things are super quick.
- Is this a resource issue? Should I be upping my RAM?
- The disk image is on the unraid array (
/mnt/user/domains/), not on the cache disk. Should I move it?
Yes, move it to the cache disk. Parity check is IO intensive on the array drives but does not affect the cache drive.
Edit: I also see you have pinned a single core to the VM. I’d suggest moving that pin to CPU 3 and also adding the hyperthread for the core (CPU 7). Unraid system processes (parity checks) tend to use CPU 0 more than other cores. So that is another resource overlap that may affect your VM performance. If you still have issues consider pinning Unraid itself to only CPUs 0/4 and 1/5.
1 Like
2048 Mb for Hassos in VM is to less. it should be at least 4048 MB, I also think that one core is to less.
1 Like
2 cores for certain. I’ve seen errors trying to start with 1.
But 2GB of RAM is ok. 4GB is going to be better as more addons are added.
RAM configuration should depend on your setup. Many addons are docker containers. If you are adding those containers within the HASS VM then, yes, you may need more than 2GB. However, all of my containerized addons are installed directly to Unraid and not within the HASS VM. Therefore, those addons don’t share the VM memory.
3 Likes
Hi all,
I have a docker in my Unraid that send telegram messages if motioneye rec a video (it’s called video2telegram).
Now that I switched from HA in docker to HA in VM I was wondering how can I “link” the share folder inside my VM to a docker container.
It is possible?
Ty in advance!
Hello
I am trying to get passthough working with unraid + hassio on the vm.
I have set it up to give it a specific port but it wont work unless I connect aotec stick AFTER i start vm, so i basiclly have to do it in this order:
- start VM without stick
- connect the stick
- restart homeassistant (docker container inside vm)
and than it works, but it has to be done with each host restarts which is annoying.
It kind of looks like that HassOs locks device in same kind of “invisible state” if it was connected at startup (if a device is connected at startup - it doesn’t show up in hardware info even if i disconnect and connect it again - it cannot be connected at startup)
Do you have any idea why that might be happening?
Did you select the stick in your VM HAssio edit/setup?