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!
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.
While working on some demos planned for my VMware Explore session, Tech Deep Dive: Automating VMware ESXi Installation At Scale [CODEB1574LV], I kept getting this network monitoring prompt when powering up my Nested ESXi VM running in VMware Fusion.
Since Nested ESXi requires the use of promiscuous mode (for inner-VM networking), you will be prompted to approve of the request or networking will be disabled. For demo purposes, you probably do not want this prompting and I was wondering if this could be disabled. After a quick ping in our internal VMware Hosted Google Space, I learned that we can disable the UI prompt by adding a VMX option to the VM.