Install Home Assistant Hass.io as VM in VMware Workstation

There a multiple ways to install Home Assistant Hass.io on different platforms. The instructions for deploying Hass.io as Virtual Machine (VM) are not very clear when using VMware Workstation or VMware ESXi. In this blog post I highlight the steps needed to deploy Hass.io as VM using VMware Workstation 15 Pro.

Here are the steps:

  • Download the VMDK image of Hass.io (link) and save it to a folder were the VMware Workstation Virtual Machine will be stored
  • Open VMware Workstation
  • Choose a custom (advanced) configuration

  • For the VM hardware comparability select: ESXi 6.5
  • Select: I will install the operating system later
  • As Guest Operating System select: Other 64-bit
  • Give the Virtual Machine a name and browse to the location the VMDK file stored. The will be a warning that there already resides a Virtual Machine in the same location. Select: Continue

  • Select the number of processors and cores. A minimum is 1 processor and 1 core.
  • Assign memory to Hass.io VM. A minimum is: 1024 MB.
  • Select as network type: NAT
  • Select as I/O controller: LSI Logic (Recommended)
  • Select as disk type: SATA
  • Select a disk: Use an existing virtual disk
  • Browse to the VMDK file downloaded earlier
  • There will be a question to convert the existing virtual disk to a newer format, select: Convert

  • The Hass.io VM is ready to be created, select Finish

Before starting the VM, edit the Virtual Machine settings and modify to following:

  • The disk is only 6 GB, expand the disk to 32 GB or higher.

  • Remove the Sound Card in the hardware configuration.

  • Change the firmware from BIOS to UEFI. Do not select “Enable secure boot”!

  • Select OK and Power On the VM.
  • When the boot is completed press “enter” in the console and the login prompt appears. To log in use “root” without a password.

  • The Hassio console prompt appears, enter “login” for host access.
  • To find the IP address assigned, use the “ip a” command in the console and look for the IP address on the enp2s0 nic.

  • Open a browser session and use the following format: http://ip-address:8123

Now you’re ready to update Home Assistant and lets start playing.

VMware ESXi Dependency Error when trying to update

When trying to update a VMware ESXi 6.7 build 9484548 host to the latest ESXi 6.7 Update 1 build I’ve got the following error:

[DependencyError]
VIB VMware_bootbank_esx-base_6.7.0-1.28.10302608 requires esx-update << 6.7.0-1.29, but the requirement cannot be satisfied within the ImageProfile.
VIB VMware_bootbank_esx-base_6.7.0-1.28.10302608 requires esx-update >= 6.7.0-1.28, but the requirement cannot be satisfied within the ImageProfile.
Please refer to the log file for more details.

When searching around it looks like there are more people who experiencing this problem (link) when trying to update to 6.7U1. Using these steps I was able to update the ESXi 6.7 host from build 9484548 to the latest version (10764712) :

  • SSH to the ESXi host
  • Put the ESXi host in Maintenance Mode
esxcli system maintenanceMode set --enable true
  • Open the ESXi firewall for HTTP traffic. The ESXi host must have internet access.
esxcli network firewall ruleset set -e true -r httpClient
  • Find the latest ESXi release name in the VMware build numbers overview, link. When writing this blog post the latest release name/patch is “ESXi670-201811001” which has build number 10764712.

  • The VMware patch depot contains a huge list of builds, to make it easier filter and find the right profile using the following command:
esxcli software sources profile list -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml | grep ESXi-6.7.0-201811
  • This results in two profiles:
ESXi-6.7.0-20181104001-no-tools VMware, Inc. PartnerSupported 2018-11-08T08:39:18 2018-11-08T08:39:18
ESXi-6.7.0-20181104001-standard VMware, Inc. PartnerSupported 2018-11-08T08:39:18 2018-11-08T08:39:18
  • Update the host by adding the “ESXi-6.7.0-20181104001-standard” profile and point to to the VMware patch depot using this command:
esxcli software profile update -p ESXi-6.7.0-20181104001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
  • Check if the update completed successfully

  • Disable the HTTP client in the ESXi firewall
esxcli network firewall ruleset set -e false -r httpClient
  • Reboot the ESXi hosts
reboot
  • When the ESXi hosts is rebooted exit maintenance mode by using SSH
vim-cmd hostsvc/maintenance_mode_exit
  • Check the update completed successfully
vmware -v

When all the steps are successfully the build version of VMware ESXi 6.7.0 is 10764712.

Extend the evaluation period of Windows Server 2012/2016 and 2019

In my lab environment I use evaluation versions of Windows Server 2012, 2016 and 2019 (if available). The evaluation versions of Windows Server are valid for 180 days by default and can be extended. The Windows Server evaluation versions can be found on the Evaluation Center, link.

In this example below, the Windows Server 2016 evaluation has only 10 days remaining . 

 

 

 

 

 

To extend the evaluation period the following steps can  be used:

    • Open an elevated command prompt (cmd)
    • Enter the following command:
cscript.exe %windir%\system32\slmgr.vbs /dlv

 

 

 

 

 

      • There are 6 remaining rearms available. This means the Windows Server evaluation version can be used for 3 years. To rearm use the following command:
cscript.exe %windir%\system32\slmgr.vbs /rearm
    • Restart the system 
    • After the restart the evaluation period is extended for another 180 days