WilliamLam.com

Passthrough of Integrated GPU (iGPU) for Apple Mac Mini 2018

by // 39 Comments

After successfully enabling and persisting the passthrough of the iGPU for the latest Intel NUC 10 (Frost Canyon), I thought it was worth experimenting with the Apple Mac Mini 2018 to see if the same could be accomplished with its iGPU, which is an Intel UHD 630. The biggest benefit in addition to unlocking the iGPU for general use is support for Apple's Metal API which gives developers access to the underlying GPU when building and testing MacOS and iOS applications. This is also quite timely as the Apple Mac Mini 2018 was just added to the VMware HCL!

My initial attempt failed when using the latest ESXi 6.7 Update 3 release. After enabling passthrough of the iGPU and rebooting the ESXi host for the change to take affect, the system would get stuck during boot up when loading the dma_iommu_mapper module. After speaking with Engineering, the issue is probably not related to dma_iommu_mapper module but some other module shortly after but without serial console output or ability to see terminal screen, it would be very difficult to debug the issue.

About to give up, my last attempt was try ESXi 7.0 and to my surprise the ESXi host fully booted up after enabling passthrough of the iGPU. It is still not clear on what might be causing the problem for 6.7 but at least 7.0 works!

Note: To be able to successfully power on a MacOS VM running on ESXi 7.0, ensure you have applied the recent ESXi 7.0b patch. You will need to go to the VMware Patch Portal siteto download and apply the update.

Step 1- Enable passthrough of the iGPU using the vSphere UI and then reboot for changes to take affect.

Step 2 - Navigate to Configure->Hardware->Graphics->Host Graphics and change the default graphics type to "Shared Direct"

[Read more...]

MacOS 11 (Big Sur) Beta 1 on ESXi

by // 15 Comments

The first Beta of Apple MacOS 11 (Big Sur) was just released a couple of days ago and I know folks are excited to start kicking the tires. Some folks have noticed when to installing Big Sur running on VMware Fusion, the following error is observed:

BIErrorDomain error 3


From the suggested workarounds, it looks like the MacOS installer was somehow unable to detect that the underlying hardware was Apple which causes this generic error to be thrown. Interestingly, this was the same error I came across when attempting to install Big Sur on ESXi 7.0. Instead of having to lookup your physical Apple hardware IDs and specify several VM Advanced Settings, you can simply add the following setting which will accomplish the same behavior:

smbios.reflectHost = "TRUE"

After the setting has been applied, the error should go away and you should be able to upgrade from an existing MacOS deployment to Big Sur. This issue has already been reported internally at VMware and I have also shared with the teams the quick workaround.

Here is Big Sur on ESXi 7.0 running on an Apple Mac Mini 2018 (requires ESXi 7.0b patch VMware-ESXi-7.0b-16324942)


Here is Big Sur on ESXi 6.7 Update 3 running on an Apple Mac Mini 2018 (requires ESXi 6.7 Patch 02 ESXi670-202004002)

Quick Tip - Certificates in Apple Keychain causes Terraform init to fail with Registry service unreachable

by // 1 Comment

I have been struggling with an interesting Terraform issue on my MacOS system where running the "init" operation would throw the following error:

Initializing the backend...

Initializing provider plugins...
- Checking for available provider plugins...

Registry service unreachable.

This may indicate a network issue, or an issue with the requested Terraform Registry.

Error: registry service is unreachable, check https://status.hashicorp.com/ for status updates

This was extremely frustrating to debug which I had filed a Github issue here. From what I have gathered, this actually had nothing to do with connectivity to the HashiCorp endpoint which works perfectly but probably was related to some other issue. What was even more strange was that using "sudo" which another user reported in an older issue allowed the operation to go through. I was also not having this problem on my other MacOS system, so I knew this was probably environmental but was running out of ideas to try.

I took another look this past weekend while doing some testing and I stumbled onto this thread here which the user found the real root cause. It looks like certain certificates within Apple Keychain Access, possibly related to Microsoft Remote Desktop that have expired was actually causing the problem. When I took at look at the Keychain Access login->certificates, I saw a number of certificates which had expired but were still marked trusted. After removing these entries (although this can be automated using the security utility, it was not trivial given the lack of arguments to quickly list out expired certificates), that I simply used the UI to delete the entries.

Once all the expired certificates were removed, I was able to successfully perform the Terraform init operation! I have already shared this update in my Github issue and hopefully this error message can be improved in the future as it was very miss-leading on the actual issue.