WilliamLam.com

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...]

How to install Windows 11 Arm with a vTPM using ESXi-Arm v1.11 

by // 7 Comments

The ESXi-Arm team has just released v1.11 of the ESXi-Arm Fling and one of the most exciting new capability is that you can now run Windows 11 Arm using an ESXi VM! There is also a TON of new features, so definitely check out the official ESXi-Arm Blog post announcement for more details.

One of the requirements for running Windows 11 Arm is the need for a Trusted Platform Module (TPM). Luckily, the latest ESXi-Arm v1.11 also now supports adding a vTPM to a guest and a requirement for setting this is a Key Management Server (KMS). Currently, the ESXi-Arm Fling is based on vSphere 7.0 (GA) and you can either use an existing compatible KMS (which you can look through VMware KMS Compatibility List) or for lab/testing purposes, you can use my KMIP Docker Container, which was also updated recently to support both amd64 and arch64 architecture.

For those interested in quickly setting this up and using my KMIP Docker Container for the KMS component, below is a quick walkthrough on how to set this up.

UPDATE (10/16/23) - vCenter Server may not be needed as you can use ESXi vSphere API to manually add encryption keys for use with vTPM, at least for x86. This same technique might also work with ESXi-Arm, for more information please see this blog post HERE.

Note: While vSphere 7.0 Update 2 introduced an embedded Native Key Provider (NKP) within vCenter Server, it can not be used with ESXi-Arm as both ESXi and vCenter must be running 7.0 Update 2 and the ESXi-Arm Fling is based on 7.0 GA.

[Read more...]

Using vSphere Lifecycle Manager (vLCM) to remediate Nested ESXi host with CPU on the host is not supported 

by // 4 Comments

If you are running a Nested ESXi VM on top of a physical ESXi host that does not have a supported CPU and you are using vSphere Lifecycle Manager (vLCM), the pre-check and/or remediation will fail due to the following error:

The CPU on the host is not supported by this image


The solution is actually quite simple and is similiar to what you had to do for your physical ESXi host by adding the ESXi kernel boot option allowLegacyCPU=true to successfully boot and install ESXi as recently explained in this blog post. To emulate this setup, I am using my trusty 2011 Apple Mac Mini which is running ESXi 8.0 with the kernel boot option and it is then running a Nested ESXi 7.0 Update 3g VM.

[Read more...]