Just create a new vm, choose Linux 64 bit, remove hard disk, Sata , SCSI… Make sure boot is setup to EFI… Then save…
Edit it again, add excisting hard disk, point to the vmdk file…, Ide 0 … Save … Boot up
2 Likes
hoi, downloaded and installed in esxi6.7 this image : https://github.com/home-assistant/hassos/releases/download/1.10/hassos_ova-1.10.vmdk
working well, setup esxi with "other linux 64 bit - efi mode)
after a while 1 hours / 1 day … randomy, i cant access/ping home assistant anymore, also if i look in esxi in the status, the internal IP is gone
i need to restart the hassos completely to see the IP again and can access it again …
whats wrong? how can i troubleshoot? if the IP vanishes, i cant find it anymore on the network, so in esxi i can only access the shell direcly via webgui
i now have configured Linux 64 bit , i can only choose VM network as adapter
maybe i need to try another os, so i can choose E1000 ?
Nice, got it to work. So is it the same procedure to import settings like on a rpi? Create a stick and passthrough to the vm ?
i dont need to passthroug anything? just attached the vmdk as a harddisk , and boot from it
you dont need an usb or whatever
Yes thats what I did - Fat 32 USB named CONFIG with network config file for a static IP attached it to the VM and rebooted - it imported the config at BOOT
1 Like
ah ok, and then you dont need to have the USB atached afterwards? so once config is loaded, its stays on static? even on reboot and no usb in passthrough?
With VMware® Workstation 14 Pro - 14.1.3 build-9474260 i bringt it up…
I met the same problem
Not working with VMware Fusion under macOS either when dragging the VMDK file into the “Install from Disk or image” screen, then selecting the ESXi 6.x option shown below that others have cited above. Errors out with
Could not open /dev/vmmon: Broken pipe. Please make sure that the kernel module ‘vmmon’ is loaded.
Completely new to the community, so perhaps just missing an obvious step, but exhbits the same failures regardless if selecting the option for Other Linux 4.x kernel 64-bit as well.
The VMDK is the already installed disk image. You add that VMDK as an existing hard disk when creating a new virtual machine. It should be Other Linux 4.x etc
I could never get it to work with Fusion on a Mac, with virtualbox on the same Mac and using exact same settings it worked straight away.
I haven’t used Virtual Box, Fusion or Workstation for quite a while but you should be able to import and export OVA files in all of them. The HASS virtual image should have been an OVA but for some reason it isn’t. If you can export the OVA from one virtual host you should be able to import it into another.
I tried that and then I just install Ubuntu Server CLI in Virtual Box and then hassio in Ubuntu Server.
This is how I solved it to run in VMware Workstation 15, but probably works also with 14.
- Create new virtual maschine (custom)
- Select “Windows 10 x64” as operating system
- Firmware Type --> UEFI (without secure boot)
- SCSI Controller --> LSI Logic SAS
- Virtual disk type --> SATA
- When importing the vmdk, do not choose “convert”, just add it.
5 Likes
I would really, really recommend you using a bare metal virtualisation instead of VMWare Workstation
i love you, sir 
NOW IT’S WORK in the VMWare Workstation (14)!
I can also confirm that this is the working solution. 
I’ll made a blog post about enabling Hass.io as VM in VMware Workstation 15 Pro. https://www.ivobeerens.nl/2019/01/15/install-home-assistant-hass-io-in-vmware-workstation/
1 Like
Excellent guide. Used information from your example to adjust VMware Player deployment to use the VMDK.
Required the following step to adjust VMware Player to boot correctly.
Convert “BIOS” (default) to “EFI” type for new Virtual Machine
Last step before we start the image. The Home Assistant bootable VMDK disk was designed and configured for the boot-loader of EFI, instead of the older legacy “BIOS” boot-loader.
If you have VMware workstation/ ESXi server, you may have access to a GUI entry to adjust this virtual firmware bootloader configuration.
However, VMware Player does not expose this setting in the GUI. To address this challenge, we will use VMware documented method to directly update the configuration file for our new Virtual machine for one (1) setting. https://communities.vmware.com/docs/DOC-28494
Navigate to the folder where the VMDK was extracted. You will now see several other files, include the primary configuration file for our new Virtual Machine. Its name will be “ homeassistant.vmx ” . The “*.vmx” filename extension/suffix will contain hardware configuration for booting the VWmare VM server image.
Edit configuration file for new Virtual Machine
Use either MS Windows notepad.exe or Notepad++ or similar tool to edit the configuration file.
If the VM image was not started, we will NOT find a key:value pair with the string “firmware”. Note: If the VM image was started before we add in our entry, then startup issues will occur. (If this happens, please restart the lab from Step 4a.)
Append the following string to the bottom of the file & save the file.
firmware = “efi“
Start the new Virtual Machine
We are now ready to start our image and begin to use the Home Assistance application. Select our new Virtual Machine & click “Play virtual machine”.
Observe the screen for “boot-loader” information related to EFI. This will be confirmation that we did configure the VMDK hard drive image to load correctly and will have no unexpected issues.
Extra Step – Disable the annoying backspace keyboard beep within a VMware image for VMWare Player
VMware Player configuration item:
Add this line in C:\ProgramData\VMware\VMware Player\config.ini
mks.noBeep = “TRUE”
Additional Docker Commands for the Home Assistant Application
docker ps [List all containers & running status; should see a minimum of three (3) running containers]
docker images [List all images]
docker logs homeassistant 2>&1 | more
docker logs hassos_supervisor 2>&1 | more
docker logs hassio_dns
docker exec -it -u root -e term=xterm homeassistant /bin/bash [shell]
docker exec -it -u root -e term=xterm homeassistant /bin/bash -c ‘netstat -anp | grep tcp | grep LISTEN’ [validate network port TCP 8123]
updated to fusion 11.5.2
other Linux x64 doesn’t exists there anymore. HA VMDK boot hangs with random: crng init done
tried guest OS: linux 4 x64 linux 5 x64 Windows 10 x 64 and ubuntu x64
all hang
any suggestions how to get it to work?
1 Like