Just read about this will be interesting to see what they do next for Apple.

Wonder if they will port ESXi to work on Apple Silicon if the interest is there. 

The MacOS support always looked a bit odd, as you were required to run it on Apple hardware. Thanks for sharing @JMeixner 

Was going to mention this. It gets more interesting when you look at what virtualising the macOS has become. Now Apple have their M1 & M2 processors, this isn’t just “standard ARM”, and the OS relies on Apple silicon specific features to run.
 

As @regnor jusr said, the MacOS EULA requires the software to only be run on authorised Apple hardware. So that’s always been a specific constraint by Apple, but as the CPU architecture was x64 Intel, ESXi could run with only drivers for specific components required. There were only two devices that supported ESXi IIRC, the Mac Mini and the Mac Pro.

With Apple Silicon this gets complicated. Starting with the M1 and then continuing with M2, fewer components aren’t Apple custom designs. Which means VMware creating drivers for all of this.

Wait though, it gets weirder! You can run macOS VMs on Apple silicon already, BUT they’re not running identically to a physical machine’s macOS install, they’re actually using generic ARM64 builds as nothing exists yet that can virtualise an M CPU, so the M kernels don’t run!

For more information read this: 

With the inability to natively virtualise an M1 CPU. The complete change of architectures (that still is awaiting an M series Mac Pro), I gotta say, I don’t blame VMware on this one! But never say never I guess, ESXi for ARM exists after all…

Even if VMware manages to solve the technical issues and were able to virtalize the M processors and macOS based on them, then Apples licensing will prohibit this…. I am afraid that Apple does not really want to run macOS VMs on another environment than it's own….