Installing VMware ESXi 6.7.0 on a Hades Canyon NUC
This is an article I should have done a long time ago as I recorded the video below early this summer. In any case, better late than.. you know. Anyway, the Hades Canyon NUC has a relatively powerful quad-core i7 CPU with Hyperthreading capabilities and that combined with its small size make it an interesting choice for a home lab where you want to run VMware ESXi.
There’s basically nothing that special on getting the thing installed. I did reset the BIOS settings before the installation and then just ran it from a USB stick onto the NVMe drive that I had installed. However, many people have reported various problems getting it installed. Unfortunately I don’t know how to help as I did not face any problems outside the one described in details below. Based on what I’ve read it seems that most people having issues with this are actually running the NUC8i7HNK model instead of the top-end NUC8i7HVK. That’s a bit of a bummer, since the fast GPU of the HVK model is kind of wasted in ESXi use so why pay for it…
EDIT: The NUC8i7HNK works also as long as you update the BIOS to version 0051!
Here’s a small video of me installing ESXi 6.7.0 on the NUC8i7HVK and booting it up for the first time.
However, only one of the two Gigabit Ethernet interfaces will work out of the box. That’s why the interface did not get an IP address in the video above. Both interfaces were detected, but for some reason only the other one was detecting signal when I had an Ethernet cable plugged in. Do note that I was playing around with this late May, so things may have improved since.
- From the Direct Console User Interface, press F2 to access the System Customization menu.
- Select Troubleshooting Options and press Enter.
- From the Troubleshooting Mode Options menu, select Enable ESXi Shell.
- Enable ESXi Shell
- Enable SSH
- Press Enter to enable the service.
Now using another computer make an SSH connection to the ESXi box, log in as root and execute the two following commands:
esxcli system settings kernel set -s preferVmklinux -v TRUE
After the reboot your both network interfaces should be working as expected.