- Run vSphere Host Update Utility 4.0 to install all 4.0 patches.
- If the host is managed by vCenter Server, you must Upgrade vCenter Server to v.4.1 first.
- Install vSphere CLI on a computer.
- Download the upgrade ZIP bundle to the vSphere CLI computer. Make sure download the ESXi (ESX Installable) ZIP bundle.
- Power off any virtual machines that are running on the host and place the host into maintenance mode.
- (Optional) Configure a scratch directory (see KB1004177). Create a directory (scratch_dir) on the VMFS volume.
- (Optional) Set the scratch directory to /vmfs/volumes/datastore1/scratch_dir
- (Optional) Select the “ScratchConfig.ConfiguredSwapState” option.
- (Optional) Reboot the ESXi host.
- On vSphere CLI computer, vihostupdate.pl --server <host-ip-addr> -i -b "upgrade-from-ESXi4.0-to-4.1.0-0.0.260247-release.zip" -B ESXi410-GA-esxupdate
- vihostupdate.pl --server <host-ip-addr> -i -b "upgrade-from-ESXi4.0-to-4.1.0-0.0.260247-release.zip" -B ESXi410-GA
- Reboot the ESXi host.
-
Recently, we created a new child domain in the existing AD forest with two new Windows Server 2012 R2 domain controllers. The AD authenticat...
-
find out the name of vSphere host running the stuck task if possible SSH to the vCenter Server server appliance service vmware-vpxd resta...
-
Updated on 07/13/2016. See the update this post, I might find the ultimate solution, even I am still not sure what the cause of the issue. ...
Is this as well possible on 32bit hosts?
ReplyDeleteStarting with v.4.0, EXSi only works on 64-bit hardware. It should not be a problem if you are already running v.4.0.
ReplyDeleteVerify the hardware with the compatibility guide (http://www.vmware.com/resources/compatibility/search.php).
Nope, was on 3.5 on a 32bit installation now updated with your instructions to 4.0
ReplyDeleteThe host is 64 bit compatible.
Will that work to update from 4.0 to 4.1 on this host?
When executing vihostupdate.pl in PowerCLI I get CommandNotFoundException. Any hint?
I don't see any reason why the update won't work.
ReplyDelete#1. The host is 64-bit compatible.
#2. It's running v.4.0.
You should execute the command in VMware vSphere CLI, not PowerCLI.