I noticed there is a vmdk available for download for hassio. Since I have been wanting to get hassio up and running on a mac mini for a while (but failed so far), I figured I give this a try, but I am failing still.
Guess I am doing something wrong, hopefully someone can help me:
I have downloaded and installed VirtualBox on OSX, then created a new machine with Ubuntu 64-bit and 1024mb memory.
Then, indicated the downloaded VMDK as a the disc for the virtual machine. However, when I do start that machine up I get the error message: āFATAL: No bootable medium found! System halted.ā
So, I figured I had to install an OS first. So, downloaded Ubuntu 18.04.1TLS Server iso and installed it on a VDI. Once that booted, shutdown the VM, added the VMDK and rebooted. No errors this time, but dont see anything HASS relatedā¦ and ādocker psā tells me docker is not installed or running?
I guess I am missing something (and not yet very knowledgable with VMās), but not a clue what?
Hope someone can point me in the right directionā¦
OK, got a step further, but not yet sure if everything is now the way it should be:
I now know that it is not needed to first create a VM with a blank linux install, like I did.
Just creating a new VM with the downloaded VMDK as the disc is enough, provided you have set it up as linux 64-bit and enabled UEFI (check the EFI boot checkbox in the settings for the VM).
Now, I get a HassOS boot Menu in the VM, but nothing seems to happen no matter what I do, it shows the menu:
1: Autoboot
2: Boot System 0
3: Boot System 1
4: Shell
Only when I hit 4 [Enter] does something seem to happen, I get a shell.
However, I noticed a screen seemed to flash by when I selected the Autoboot option. This is what I was able to capture:
I checked that the VMDK file was readable and writable by everyone. But not sure if this is something I am doing wrong, or there is something missing/wrong with the VMDK?
I just tried this, and I think the thing you may be missing is that you have to select Enable EFI (special OSes only) in the system tab of the settings for the VM. This gets the VMDK to boot.
I think you also need to select the Bridged network adapter to see the machine from your host. Just type hassio.local:8123 in the browser on your host.
I do have that EFI setting enabled, indeed thats what causes the vmdk to boot. But, as soon as the vmdk boots, I get that boot screen and nothing further seems to happen. I could not access the hassio.local instance. But I have not messed with the network adapter, Iāll have a look, thanks for the suggestion!
Could not get it to work yet unfortunately. I did check that EFI is checked, and seeing the HassOS boot menu tells me that that is working. However, after that I cannot access http://hassio.local:8123. Also, if I enter the shell and try ādocker psā, nothing shows up apart from a ādocker: No such file or directoryā message. So, I think nothing has actually been started up.
It starts up with a HASSOS page, and then immediately goes to a normal Linux type startup log. There is not scrollback in the window, so I canāt capture exactly what comes out, but there is no further input required.
ok, started from scratch bij re-downloading the vmdk. Setup a VM with āother linux 64 bitā and the rest as before: 1024gb ram, EFI on, 2 vcpu.
Now, the autoboot screen does not show and it looks like hass is starting, but no matter the network settings I try, I cannot access hassio.local:8123. Nor, when in NAT mode, can I access the ip of the VM (that I found in the virtualbox log). Also ping does not work.
I tried setting port forwarding rules for NAT, as well as setting up the bridged mode, but both failed so far.
@gpbenton, when you suggested bridged mode, I can choose various devices in the ānameā dropdown. I tried Wifi (airport) and Bridge0 (the others are ports on my mac that are not in use, like thunderbolt.
Anything else that requires attention in the network area?
sorry n00b, how do I do that? I can see a running log on the VM window, but canāt seem to access anything else that I am aware of (basically only hassio.local:8123
when I then enter āha infoā, I get some json that seems to indicate everything is ok. So, I guess a network config screw-up on my part is the cause here
I think the network configuration is likely to be the next problem. The interface you select should be the one that your Mac uses to connect to the network, but I donāt know enough about Macs to suggest one.
If you type login at the hassio > prompt you get to a command line and can use ping to see if you can access other nodes on the network.
Yes, when I login on the console, I can ping both IPās on my LAN as well as dns names on the internet succesfully.
Additionally, I have set the network configuration to NAT on the VMās settings, then under the āadvanced settingsā for network, I created a port forwarding rule from :8123 to :8123 and now I can access home assistant from the browser but only when entering http://:8123
So, the hassio.local name does not work (yet) ,it seems.
makes sense: forwarding ports from the host to the guest to reach those services running on the guest. I can also install add-ons, so going from the guest vm out to the internet is working as well.
However, not sure if that can explain why the dns (or is it bonjour?) is not working for me
If your router doesnāt support mDNS, then youāll have to use the IP address of your Pi instead of hassio.local. For example, http://192.168.0.9:8123. You should be able to find the IP address of your Pi from the admin interface of your router.
ah, did not know that mDNS is whats exposing the hassio.local address. So when using the vmdk, not only does the router on the lan have to support it, but also VirtualBox or something. Iāll dive into it some more to see what I can do there. THanks again!
