Installing ESXi to a USB key using VMware Workstation 11

24th January 2015 0 By Simon

This is an updated post covering VMware Workstation 11 instead of Workstation 9, it’s been updated to cover installing using the formatwithmbr switch during the initial boot process as well as highlighting an issue with creating multiple USB keys from the same VM template.

This is still the the quickest and easiest method for me to install ESXi on to a host with no local CD\DVD drive.

Continue to read after the break for the updated build \ preparation process.



Type Ctrl+N to open up the New Virtual Machine Wizard


Browse to your ISO file.


Define the name and location where you’re going to store the files.



Un-tick the Power on VM box because we are going to edit the VM settings after we finish, it’s no good clicking customize hardware at this point because the HDD hasn’t been created yet.


Here we can see the VM hardware settings, we are going to delete the HDD to reduce overhead.


Click OK.

Next we need to power on the VM and then attach the USB device to it. Browse to the Home on Workstation or Player



Right click on your VM and choose Power and the Power On.


Now we need to attach the USB to the VM.

ESXi Install 02_thumb[17]

To ensure that we can use the SanDisk Cruzer Fit USB devices we need to ensure that ESXi is installed with the MBR partitioning format.

During the boot process hit Shift+O to interrupt the boot process and bring up the following screen.

ESXi Install 03_thumb[29]

Add a space after runweasel to add formatwithmbr, this ensures that the USB drive is formatted with mbr rather than gpt during the installation.

Time to go through the installation.









The installation completes in a couple of minutes and then you’re good to go :). Let the system reboot and during the POST power off the VM and remove the USB drive.

Now take the USB key and plug it in to your Host and boot away.

**** Important Note ****

If you need to build multiple USB keys you MUST create new VM’s for every USB device, failure to do so will lead to various issues with each host built using the same VM template (dropped ICMP packets, unreliable communications between the host and vCenter etc).

**** Important Note ****