by William Lam // 2 Comments
Happy 2025! 🎉 Here is a fun one to kick off the New Year ☺️
Last year, I demonstrated a method for customizing the SMBIOS hardware string using Nested ESXi, but the solution was not perfect and required hacking up a VM ROM file and it was also limited to using the BIOS firmware for your Nested ESXi VM as the behavior for EFI firmware was different.
I was doing some research towards the end of last year and I came across a much more elegant solution that works for both physical and virtual ESXi!
by William Lam // 5 Comments
A new version of the ESXi-Arm Fling (V2) was recently released and the major update to the ESXi-Arm V2 Fling is that it is now based on the latest ESXi 8.x codebase, which is currently 8.0 Update 3b. In my blog post, I had hinted there was a small easter egg 🐣 the Engineering team had included in the ESXi-Arm Fling update, which I did not know about until they had mentioned it!
Since no one has officially found the easter egg, I figured it might be time to break the silence and share as I think it can actually benefit some users based on their usage of ESXi, especially from a testing and/or learning perspective such as playing with the vSphere API as just one example.
by William Lam // 14 Comments
The general guidance and quickest way to recover an ESXi host if you have forgotten or lost the root password is to reset using vSphere Host Profiles if it was managed by vCenter Server or simply reinstall ESXi which would allow you to preserve the existing VMFS volumes along with any workloads that may reside on them.
In the past, it was also possible to reset the ESXi root password by booting the system into Linux and then manually updating the /etc/shadow file, which is simliar to how you could reset the password on a Linux-base system and you can find a number of blog articles outlining the details. With the introduction of the ESXi Configuration Store, the previous methodology no longer works for modern ESXi releases starting from ESXi 7.0 Update 1 and later.
Having said that, I know this is still a topic that comes up frequently, especially in the context of administrators joining a brand new company where the ESXi root password has not been properly documented or an admin being asked to support a random set of standalone ESXi hosts that have no owners. Regardless of the scenario, while a reinstallation is the quickest way to recover, it certainly would be nice to be able to maintain the original configuration, especially if there is no documentation to begin with.
While there has been various snippets of information shared online (here, here and here), which includes information from myself, I figured it might be good to figure out the latest process for recovering an ESXi 7.x or 8.x host without requiring a reinstallation.