Hi, I have a trouble using local ssd in Macmini8,1. After installing this fling, I'm able to see the disk, but when I try to format and use it for datastore, it crashes without any PSOD. And starts to boot again.

So I tried format it in macOS Recovery -> GPT, single partition and then format with vmkfstools. This didn't work either.

Anything I try to do with the disk in esxi (cli or web) results in crash.

Am I missing some obvious settings or something?

I'm running fresh install of ESXI Update 3 ( Build 17499825)

I have also tried this with ESXi 6.7.0 Update 3 (Build 16713306). Same behaviour. Any formatting, partitioning of the disk fails with sudden crash and reboot.

I have the same issue on the MacMini 8,1.
I installed ESXi 6.7 with Apple-T2-NVME and Aquanta 10G drivers. Trying to format the NVME SSD makes ESXi crash.

I tried with ESXi 6.7 U3 (14320388) and it works :-)

I just finished testing all the builds in between 14320388 ==> 16713306 (which does NOT work at all on my Mac Mini 2018).

I found that these builds all work to some degree:

14320388
15018017
15160138
15820472
16075168
16316930

For kicks I also tried the latest 6.7 release (17700523) which did NOT work (as expected)

YMMV ... hope to see updates soon with support for 7.x releases!

@Fravadona Thanks for this. I'm running into that exact same crash - Mac Mini 2018 w/ 1TB internal NVMe. Will try build 14320388 as you suggest. How did you figure this out? Trial and error?

Hello, after I upgraded patch, SSD works fine, but I can't properly run VMs. When I let them in the previous state I can't boot with error: "Your computer restarted because of problem". But when I remove smc.version & smc.present from advanced settings, VM looks like frozen in loading system but I can login to VM through SSH, but can't VNC to, it looks like the GUI has problem or ?

6.7.0 Update 3 (Build 15160138), BigSur

Same when I try to create new VM and make clean install

I can't edit previous comments, so I'm sorry for a lot of replies. I fixed it finally with update esxi-unlocker to newest version https://github.com/shanyungyang/esxi-unlocker

Thanks Jmuransky for your solution.