Since vSphere ESXi 5.0 uses the new VIB model the commands and process have changed slightly but the basic concepts are the same.
- Download the patch file you want directly from the VMware Patch Portal
- Ensure that you enable SSH for remote support on the ESXi Host
- Make sure your host is in Maintenance Mode, this is a requirement since you will need to reboot
- Transfer the update file over to the host using FileZilla or SCP to a MOUNTED DATASTORE of some kind. NOTE: There is not enough space to transfer this to a location on the local ESXi Image. It took me a bit to realize this was failing to copy.
- Once you have uploaded the file to a datastore, this is considered a “Local Depot Repository” as opposed to one on FTP or HTTP.
Got finally sick of opening the vSphere client every time I needed access to a virtual machine running on my ESXi 4.1 server. Did some googling and trying out couple of options and finally found a way to do this. “C:\Program Files\VMWare\Infrastructure\Virtual Infrastructure Client\4.1\vmware-vmrc.exe” -h <esxi_host> -u <username> -p <password> “[datastore1] myvm/myvm.vmx” via Direct shortcut
With the 2.6.34 Kernel series my machine complained when building the modules for VMware server. Something to do with unable to find the autoconf.h file. After a bit googling I found a few comments the lead me to try creating symlinks. The new kernels put the header files in /lib/modules/2.6.34/build/include/generated whereas the build process looks