WilliamLam.com

Updated findings for passthrough of Intel NUC Integrated Graphics (iGPU) with ESXi

by // 48 Comments

While searching for drivers for another Intel NUC platform, I saw that Intel had recently published new graphic drivers for Linux including support for their new Intel Arc GPUs. This of course got me curious on wondering whether this would help at all with the issues regarding passthrough of the integrated graphics (iGPU) for recent Intel NUCs? 🤔

As a refresher, starting with the 11th Gen Intel NUCs, passthrough of the iGPU on Windows had stopped working and would result in the infamous Windows Error Code 43 and even worse on the 12th Gen Intel NUCs, Windows would simply BSOD after the initial reboot. The behavior is also simliar for Linux operating systems, while it better handles the issue by not crashing the OS, iGPU passthrough is also not functional for Linux systems.

To be honest, I had low expectations these new Linux graphic drivers would behave any differently, but I decided for the sake of persistency that I would give it one more go. I had access to both an Intel NUC 12 Extreme (Dragon Canyon) and Intel NUC 12 Pro (Wall Street Canyon), both of which included recent Intel iGPUs.

🤯🤯🤯 is the only way I could describe what I had discovered after my testing!

[Read more...]

How to delete an ESXi component in vSphere Lifecycle Manager (vLCM) depot?

by // 8 Comments

vSphere Lifecycle Manager (vLCM) allows users to upload an ESXi component into its depot using the Import Updates operation in the vSphere UI, but deleting an ESXi component from the vLCM depot is currently not possible when using the vSphere UI.


However, using the vLCM REST API we can delete an ESXi component from the vLCM depot with the Settings Depots Offline APIs. To demonstrate these specific vLCM REST APIs, I will be using PowerCLI (Connect-CisServer) but you can also use the vLCM REST API directly via any REST Client.

[Read more...]

Quick Tip - Changes to building custom ESXi images in vSphere 8

by // 2 Comments

Historically, when a new version of ESXi is released, customers will use vSphere Image Builder either through the vSphere Image Builder UI or PowerCLI Image Builder cmdlets to create a custom ESXi image to include additional drivers such as the USB Network Native Driver for ESXi Fling.

Note: The current version of the USB Network Native Driver for ESXi Fling is not compatible with ESXi 8.0 and a new version of the driver will be needed. There is currently no ETA on when a new version will be available.

Typically, customers will use their existing vCenter Server deployment, which is usually running an older version to create their new custom ESXi image. This means you are importing a newer ESXi release into your vCenter Server or in the case of the PowerCLI Image Builder cmdlets, you are using an older release of PowerCLI. While this may have worked with previous releases, the assumption that vSphere Image Builder is "forward" compatible with future releases of ESXi is actually an incorrect assumption that many have made, including myself.

I bring this up because in vSphere 8, there have been changes in ESXi where this incompatibility will be observed when attempting to create a custom ESXi 8.0 image using a non-compatible vCenter Server or a PowerCLI release.

[Read more...]