If you can reproduce the problem, after that boot loop happens, shutdown the VM and pull the vmware.log file (plus the .1 file) and upload them to see what's going on.
It could be this:
2019-03-18T15:07:18.440Z| vcpu-1| I125: HostSMCRead: Unable to read key "OSK0".
2019-03-18T15:07:18.443Z| vcpu-1| W115: DarwinPanic: panic(cpu 1 caller 0xffffff7f8f890b1e): "DSMOS: SMC read error K0: 133"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/DontStealMacOS/DontStealMacOS-27.200.2/Dont_Steal_MacOS.cpp:191
2019-03-18T15:07:18.449Z| vcpu-0| I125: Destroying virtual dev for scsi0:0 vscsi=8974
Yes, I was just about to post that. This is a similar message seen when people try and install macOS on non-Apple hardware. Is it possible you've installed some third-party software called "unlocker" on this ESXi host? If not, only other thing I can suggest is to install MacOS on the bare metal and use it long enough to update the SMC firmware in case this is a bug. Otherwise, if you have support you may want to open an SR with VMware on this.
Has anyone found a solution to this?
I have two mac minis that fail with the latest OSX.
- 2014 mac mini with ESXi 6.5 or 6.7
- Latest mac mini with ESXi 6.5 o 6.7
Old OSX (10.9) works on the 2014 mac mini. Doesn't on the new one. New OSX (Mojave) doesn't install on either
Has anyone got the latest OSX to work on any ESXi version/mac mini combination?
Moderator note: Moved to ESXi