I’m having the same problem as you, and I want to check with you now.
Did you install 11.0.1 with esxi 6.5 and then upgrade to 11.3.2, or did you install 11.0.1 with esxi 7.1 and then upgrade to 11.3.2.
Looking forward to getting your reply!

Your the man! Well done! This worked for me, but I had to upgrade from 6.7 to get it functional.

I have a Ryzen Threadripper 3970X (32 cores, 64 threads) and trying to get this working. I’ve been trying with both macOS Big Sur and Monterey just to at least get one of them working at first.

I pasted in the above and it helped to get the macOS installer working (FINALLY)! Thanks for that. At least now I’m in the right direction. (Also thanks to Erick for pointing me to the comments here on his Big Sur post!)

So I think the next thing I need to do is get the correct address values for my processor. e.g. the ones in this format:

> cpuid..=””

The questions I have now are…

1. I probably don’t need to define ALL the cpuid’s for the macOS VM if I only use, let’s say, 8 processors.
2. Where exactly can I find out this cpuid information to compile and put in the VMX file? Maybe it’s in the dmesg?

Could someone point me in the right direction here so I can get these defined in my VMX file with the correct cpuid.* values?

I’ve compiled all my previous attempts from the VM’s which have the log files in there and also dumped the dmesg output and vmx files: https://mega.nz/folder/TGwUhDbI#kfURB9dqPErQrLexujokbw

On another note, after I followed the unlocker instructions and gave a reboot, I noticed these after the unlocker.py. Not sure if the custom.vgz is part of the unlocker and if it was there previously? Regardless, it seems to work. 🙂

2022-02-18T14:47:32.784Z cpu46:2100850)init Running unlocker.py
2022-02-18T14:47:42.487Z cpu3:2098006)NRandom: 547: Entropy INTR health check passed
2022-02-18T14:47:43.564Z cpu59:2100896)ALERT: UWVMKSyscall: 2494: vmkramdisk is deprecated: custom.vgz mount
2022-02-18T14:47:43.797Z cpu59:2100896)VisorFSTar: 2029: fileZwlmev (3109454295355930691) as custom.vgz for 36014512 bytes
2022-02-18T14:47:43.797Z cpu59:2100896)WARNING: VisorFSTar: 1678: Unauthorized tardisk mount. Tardisk mount restrictions are disabled on this host

Thanks for the help!!! This article is spot on.

-gregg

Installing macOS 12 Monterey on VMware ESXi 7 Update 3

Great. Thanks for sharing Byron!

I can confirm that I also ran into this problem with the Browser console. Switching to VMRC fixed it.

Hi Alexx. Are you doing this in the browser? Does the same thing happen if you use VMRC? Give that a shot in VMRC if you haven’t already.

hey Vince, have you tried installing monterey on esxi 7 or 6.7 with amd ryzen?

Hi Jeremy. Glad to hear you figured it out and shared the fix. Much appreciated. 🙂