Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. If the update is successful (it can take a few minutes, be patient), you should see something like this (I’ve truncated the output as it’s a bit long): Update Result
To apply it, just pop the name of the profile in to the following command: esxcli software profile update -p ESXi-6.7.0-20191204001-standard -d The second entry is the one that I wanted. In my case that returned me four results: ESXi-6.7.0-20191201001s-standard VMware, Inc. You don’t want to soft through EVERY update available. The “grep” command at the end can be adjusted to filter the results. Next, to prove connectivity and get the correct update name, the following command can be use to list the available software profiles: esxcli software sources profile list -d | grep ESXi-6.7.0-201912 The first step is to open up the hosts’s firewall so it can connect out: esxcli network firewall ruleset set -e true -r httpClient Luckily there’s another way if you have ESXI hosts that can connect to the internet. Please refer to the log file for more details. VIB VMware_bootbank_esx-base_6.7.0-0388 requires esx-update << 6.7.0-3.74, but the requirement cannot be satisfied within the ImageProfile. VIB VMware_bootbank_esx-base_6.7.0-0388 requires esx-update >= 6.7.0-3.73, but the requirement cannot be satisfied within the ImageProfile.
I had downloaded the offline update bundle from VMware’s site and placed it on a shared VMFS datastore.īut I was met with the following error when I tried to apply it: My first attempt at an update was not successful however. Updating my hosts via esxcli however still works.
That said, I will most likely not be able to run the next version of vSphere owing to the deprecation of the vmklinux driver stack.Ĭoming back to the topic in hand, vSphere Update Manager tends to complain when I use it owing to my unsupported processors. In my case, updates aren’t as straightforward as they should be but that’s offset by the cheaper cost and age of the hardware. As any homelabber will attest, sometimes compromises have to be made to run your own lab. Having been switched off for some time, I brought it back up over the Christmas break after a long lunch with homelab hero The point of this post is not the reasons why my lab has come back to life (I’ll cover that at some point), but about how I got it updated to the latest version of vSphere.Īs a recap, and to save anyone reading my previous post, my lab is constructed from Dell workstations that don’t appear on the HCLs for VMware. The one constant though was the build of ESXi that I was using. Since that time it has had a few rebuilds and reconfigurations, been off for several months, been idle, been busy and generally just worked. About 18 months ago I wrote a post on my experience upgrading my homelab from vSphere 6.5 to vSphere 6.7.