WilliamLam.com

vSphere ESXi 7.x will be last version to officially support Apple macOS Virtualization

by // 11 Comments

As a heads up, I just wanted to share that VMware has just published a new knowledge base article to communicate that ESXi 7.x will be the last major release to officially support Apple macOS Virtualization, which was originally introduced back in 2011 with the release of vSphere 5.0.

Last year, VMware had also published a blog outlining that they will no longer pursue hardware certification for the Apple 2019 Mac Pro 7,1 for ESXi and as unfortunate as this is, hopefully this updated news will not come as a surprise to any of our customers or partners due to the various challenges in supporting the Apple hardware platform with ESXi.

On a more personal note, this is also a bitter sweet end, I have been writing about Apple macOS Virtualization on ESXi since its inception almost exactly 11 years ago. I came to learn about the new virtualization capability during an on-site beta for vSphere 5.0 (codenamed MN) at VMware HQ back when I was a customer. Not only did our organization have a need for this capability, but this was also the time that Apple had announced EOL'ed of Apple XServe, which was the initial hardware platform that was officially supported. I still recall emailing our leadership after the on-site to purchase as many XServe as we could before you could no longer buy the systems so that we can enable our development teams who were building both iOS and macOS applications.

It certainly has been a wild ride over the years in advocating for our users and their plethora of use cases to getting the Apple Mac Mini to run ESXi like any other x86 platform and even getting the Apple Mac Mini added to the VMware HCL. I still remember all the hoops and hacks that one needed to jump through just to boot ESXi and over the years, various VMware Engineers have incrementally helped get us to where we are at today, so a big thanks for all of their support over the years.

Aquantia/Marvell AQtion (Atlantic) driver now inbox in ESXi 7.0 Update 2

by // 25 Comments

Last spring, VMware and Aquantia (now part of Marvell) collaborated and delivered their first ESXi Native Driver for their AQtion (Atlantic) based 10GbE network adapters. This new driver was primarily focused on enabling network connectivity for ESXi when running on either an Apple 2018 Mac Mini (8,1) and Apple 2019 Mac Pro (7,1) that included the 10GbE networking option. Consequently, this driver also benefited the broader VMware Community as it enabled additional 10GbE networking through a number of Thunderbolt 3 to 10GbE network adapters that customers could now take advantage in their VMware environments.

With all these benefits, VMware has decided to inbox the Aquantia/Marvell driver with the latest ESXi 7.0 Update 2 release, so that customers no longer had to create a custom ESXi Image Profile that included the driver, which was always required when installing ESXi on either the Apple Mac Mini or Mac Pro that were configured with the 10GbE networking option. For a complete list of supported Aquantia/Marvell AQtion based network adapters, please see the VMware HCL.

Here is a screenshot of an earlier release of ESXi 7.0 Update 2 running on the 2018 Mac Mini which now automatically recognizes the 10GbE network adapter out of the box.

Apple NVMe driver for ESXi using new Community NVMe Driver for ESXi Fling 

by // 77 Comments

VMware has been making steady progress on enabling both the Apple 2018 Mac Mini 8,1 and the Apple 2019 Mac Pro 7,1 for our customers over the past couple of years. These enablement efforts have had its challenges, including the lack of direct hardware access for our developers and supporting teams due to the global pandemic but also the lack of participation from Apple has certainly not made this easier.

Today, I am happy to share that we have made some progress on enabling ESXi to see and consume the local Apple NVMe storage device found in the recent Apple T2-based mac systems such as the 2018 Mac Mini and 2019 Mac Pro. There were a number of technical challenges the team had to overcome, especially since the Apple NVMe was not just a consumer grade device but it also did not follow the standard NVMe specification that you normally would see in most typical NVMe devices.

This meant there was a lot of poking and prodding to reverse engineer the behavior of the Apple NVMe to better understand how this device works, which often leads to sudden reboot or PSODs. With the Apple NVMe being a consumer device, it also meant there were a number of workarounds that the team had to come up with to enable ESXi to consume the device. The implementation is not perfect, for example we do not have native 4kn support for SSD devices within ESXi and we had to fake/emulate a non-SSD flag to work around some of the issues. From our limited testing, we have also not observed any significant impact to workloads when utilizing this driver and we also had had several internal VMware teams who have already been using this driver for a couple of months now without reporting any issues.

A huge thanks goes out to Wenchao and Yibo from the VMkernel I/O team who developed the initial prototype which has now been incorporated into the new Community NVMe Driver for ESXi Fling.

UPDATE 2 (06/30/2023) - Thanks to reader Spotsygamer, who shared v1.2 of NVMe Fling also works with ESXi 8.x and vSAN ESA

UPDATE 1 (11/21/2021) - v1.2 of NVMe Fling works with ESXi 7.x

Caveats

Before folks rush out to grab and install the driver, it is important to be aware of a couple of constraints that we have not been able to work around yet.

  1. ESXi versions newer then ESXi 6.7 Patch 03 (Build 16713306) is currently NOT supported and will cause ESXi to PSOD during boot up.
  2. The onboard Thunderbolt 3 ports does NOT function when using the Community NVMe driver and can cause ESXi to PSOD if activated.

Note: For detailed ESXi version and build numbers, please refer to VMware KB 2143832

VMware Engineering has not been able to pin point why the ESXi PSOD is happening. For now, this is a constraint to be aware of which may impact anyone who requires the use of the Thunderbolt 3 ports for additional networking or storage connectivity.

With that out of the way, customers can either incorporate the Community NVMe Driver for ESXi offline bundle into a new ESXi Image Profile (using vSphere Image Builder UI/CLI) and then exporting image as an ISO and then installing that on either a Mac Mini or Mac Pro or you can manually install the offline bundle after ESXi has been installed over USB and upon reboot, the local Apple NVME will then be visible for VMFS formatting.

Here is a screenshot of ESXi 6.7 Patch 03 installed on my 2018 Mac Mini with the Apple NVMe formatted with VMFS and running macOS VM