WilliamLam.com

ESXi-Arm V2 Easter Egg

by // 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.

[Read more...]

Quick Tip - Disable network traffic monitoring (promiscuous) UI prompt in VMware Fusion

by // Leave a Comment

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.

[Read more...]

Quick Tip - Workaround for unsupported processor error in Windows 11 for Arm on VMware Fusion

by // Leave a Comment

This morning I came across an intriguing post on the VMware Reddit channel where a user had ran into an issue while attempting to upgrade their Windows 11 on Arm VM, running VMware Fusion on an Apple Silicon system. The error message stated that the CPU processor is not currently supported for Windows as you can see from the screenshot below:

After sharing the thread internally, I immediately got an answer back from one of the VMware Fusion Engineers and this issue looks to have also recently impacted UTM and luckily, there was an easy solution using the following Windows registry hack:

  • Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability : BranchName -> CanaryChannel
  • Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\UI\Selection : UIBranch -> CanaryChannel

After applying the registry tweak, the VMware Fusion Engineer confirmed Windows Update was now able to successfully start as shared with their screenshot below.