How to make a bootable VMware vSphere 5 USB installation media


Now that VMware has released their new vSphere 5 into the public, questions always come up on how to make a bootable vSphere 5 USB installation media. As of now there isn’t any official way of doing this if you are using a Microsoft, Apple or Linux GUI  based OS. So I have made a small step-by-step guide on how to achieve this. So here we go…


1. Download UNetbootin and run the software (WindowsMac OS XLinux).

2. Download the VMware vSphere 5 ISO file -> VMware Download Center.

3. Start the UNetbootin application and choose Diskimage (ISO) and browse to the downloaded ISO file.

4. Choose Type: USB Drive and choose the correct USB drive letter that you want the bootable installer to be installed to.

5. You are now done! Just make sure you edit the boot sequence in your BIOS (UEFI mode on some systems).

You can also visit the vSphere 5 documentation online.

Please post some comments if you feel like leaving some feedback!




VMware vSphere 5 released today!

VMware Announces General Availability of VMware vSphere® 5

VMware vSphere 5 supports virtual machines (VMs) that are up to four times more powerful than previous versions – VMs can now be configured with up to 1 terabyte of memory and 32 virtual CPUs. When combined with VMware vSphere 5’s enhanced High Availability, these gains in VM scalability and performance enable customers to virtualize any business-critical applications with confidence in the application’s continued performance and availability.

VMware vSphere 5 also introduces three key new flagship features – Auto-Deploy, Profile-Driven Storage and Storage DRS – that extend the platform’s unique datacenter resource management capabilities, delivering intelligent policy management to support an automated “set it and forget it” approach to managing datacenter resources, including server deployment and storage management. Customers can define policies and establish the operating parameters, and VMware vSphere 5 does the rest.

VMware News Releases
VMware vSphere 5 Documentation
VMware vSphere 5 Download

Checksum Offload – network slow downs?

I’m pretty sure that the Checksum Offload causes a bunch of network slow downs – especially in a virtual environment.
Whenever a customer says that it takes a good few seconds to open i.e. a Word document, placed on a share, I always disable Checksum Offload wherever possible on the NIC, inside the VM. This has always been the main reason for the slow downs. I’m not sure why exactly, but it seems that disabling this feature solves the problem!


Any comments are welcome!

Hot to get VMware vSphere Client to work in Windows 7

Here is a step-by-step guide to get VMware vSphere Client and the vSphere Host Update Utility to work in Windows 7. My system is running Windows 7 – 64-bit, so please make sure you enter the correct “Program Files” folder if your system is 32-bit. Let’s get started:

1.  Open the following folder:
     C:\Program Files (x86)\Vmware\Infrastructure\Virtual Infrastructure Client\Launcher

2.  Edit the VpxClient.exe.config file and make it look like the following:


     Just add the lines from 12 to 14 and your set!

3.  Create a new folder in the same location called Lib, and then place the System.dll (attached here -> System.dll).

4.  Edit your system environment variables and create a new one, DEVPATH, and set it to:
     C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib

 Now, vSphere Client should work!  But the Host Update Utility still need some tweaking, here are the final steps:

5.  Copy VpxClient.exe.config file (from above) to the following location, re-naming it to VIUApp.exe.config:
     C:\Program Files (x86)\VMware\Infrastructure\VIUpdate 4.0\

And now the Host Update Utility will work, also.

Have fun!

Upgrading your virtual hardware to version 7 (VMware vSphere)

If you’ve upgraded to or installed ESX(i) 4.0 you’ll see that you have an advanced option to pick which virtual machine hardware version to use for your new VMs. As noted in the image below, the virtual hardware version will determine which other VMware products the VM can be run on. Virtual machine version 7 is also required for new ESXi 4.0 features like virtual IDE hard drives, VMXNET generation 3 virtual NICs, the LSI Logic SAS virtual controller and VMDirectPath. If you’ve upgrade from ESXi 3.5, you can use the process below to upgrade the virtual hardware version from 4 to 7.

Click on the images to get full-size previews.


 1) While the VM is powered down, right click on the VM and select Upgrade Virtual Hardware. If the VM is already at version 7 then the option will not be available. The option will also not be available if the VM is running. As shown in the 2nd image, the option is upgrade the virtual hardware is not reversible. This includes a VM with a snapshot on it. If you’re using vCenter Server, you can use Update Manager to upgrade the VM which will automatically backup the VM before the upgrade. As shown in the 3rd image below, it is best to upgrade VMware Tools in the VM prior to upgrading the virtual hardware. This will help preserve network settings especially on Microsoft Windows VMs.




2) If you’ve opted to upgrade VMware Tools prior to the virtual hardware upgrade, selec the Cancel option shown on the image above and click OK. Then power on the VM and once it has booted up, you can right click and select Guest \ Install/Upgrade VMware Tools. With ESXi 4.0 you can select to manually upgrade VMware Tools or to have VMware Tools automatically upgraded.



3) After VMware Tools has been upgraded, the status should show as OK on the summary page for the VM. Select the Upgrade Virtual Hardware option again. After a few minutes the process should complete as shown in the 3rd image below.




4) Once the process has completed, the VM Version should show 7 on the VM’s summary page. You will also want to check the console of the VM as the change in virtual hardware may require a further reboot of the VM.



5) And there you go, hope this works out for you! Thanks to VM-Help for the info.