VMware on wporter.org

Resolving ESXi 8.0 esxcli software profile MemoryError with hostupdate depot

Sun, 16 Mar 2025 11:13:59 +0000

Problem

VMware ESXi 8 host fails to query the hostupdate (hostupdate.broadcom.com) depot’s contents with a MemoryError when an esxcli software profile update command is issued.

This also prevents ESXi from being updated (does not just affect querying the depot).

[root@vmware:~] esxcli software profile update -p ESXi-8.0U3c-24414501-standard -d https://hostupdate.broadcom.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
 [MemoryError]
 Please refer to the log file for more details.

Verify

Search the /usr/lib/vmware/esxcli-software file for the mem= argument being passed to the Python interpreter. The default 300 Mb is insufficient for querying the chunky ESXi 8 hostupdate depot, though 7.0 and 6.7 will still work fine.

vCenter Server Appliance - regen certs, recover PWs, other tips and tricks

Sun, 16 Mar 2025 11:12:59 +0000

Enabling SSH

Consider this a prerequisite for everything that follows.

If SSH was not enabled while you set up the VCSA (it’s a toggle labeled “Enable SSH” with a tooltip about being required for HA - you probably left it off) you can enable it via the vCenter Server Management UI at port 5480.

Log on to the management UI. In the left menu, select “Access”.

Click “Edit” in the top right of the screen, toggle “Activate SSH Login”, then click “OK”.

Changing vCenter Server DHCP address

Sun, 16 Mar 2025 10:12:59 +0000

Problem

You would like to change the IP address for a vCenter Server appliance that is currently configured with DHCP by modifying the reservation.

Doing this the way you might first think of (by changing the reservation then forcing the VCSA to get a new IP) fails, because you must regenerate certificates afterwards and cannot do so when the SSO authentication service is not working (after an IP change).

Solution

Tested with a VCSA ver 8.0.3.00000 on 16 Mar 2025. Fresh install, not a neglected appliance!

Updating standalone VMware ESXi hosts from the online hostupdate depot with esxcli

Sat, 08 Mar 2025 10:12:59 +0000

Problem

You have a standalone VMware ESXi server, or a non-clustered (no vCenter available) set of servers that need to be updated.

Solution

Before starting:

Verify that your IPMI/BMC is plugged in! If it is not, you will not have a good time if your sole ESXi server fails to write the bootloader and wipes its config at a site three hours away. Make sure it’s accessible somehow.
Check your server’s DNS settings! Name resolution won’t work once you suspend VMs if the server is pointed at a guest it’s running.

Updating ESXi 8 hosts from a depot file

Fri, 05 Jul 2024 12:34:56 +0000

Personal notes - I usually use Lifecycle Manager because it’s easy.

Download the depot file from somewhere (of course I mean the Broadcom portal, you dirty pirate.)

Upload the depot file to a host datastore of some kind, either through the web UI browser or with SCP.

user@pc:~$ scp VMware-ESXi-8.0U3-24022510-depot.zip user@hv0.mydomain.internal:/vmfs/volumes/<datastore>

You can either use esxcli remotely, or ssh into the host.

Determine which profiles are available from the depot with esxcli once it’s on accessible storage.