WilliamLam.com

Failed to locate kickstart on Nested ESXi VM CD-ROM in VCF 9.0

by // 2 Comments

If you are automating the installation of ESXi using a scripted installation (aka Kickstart) and the KS.CFG is located on a CD-ROM device and you happen to be using a Nested ESXi VM and see the following message:

cannot find kickstart file on cd-rom with path -- /KS.CFG


You are probably using an IDE-based controller for the CD-ROM device, which the underlying IDE driver for ESXi has been removed as part of VMware Cloud Foundation (VCF) 9.0.


The fix is to simply remove the IDE controller and use a SATA controller and things will work as expected!

Enable TRIM/UNMAP from Nested vSAN OSA/ESA to physical vSAN OSA

by // Leave a Comment

If you are running Nested vSAN Original Storage Architecture (OSA) or vSAN Express Storage Architecture (ESA) workloads on top of a physical vSAN OSA setup, you may want to enable the Guest TRIM/UNAMP capability, which would allow your the "inner" (Nested) workloads to pass the TRIM/UNMAP requests down into your physical vSAN OSA deployment for space reclamation.

It was recently observed that storage utilization may continue to increase on a physical vSAN OSA setup even when the Nested vSAN ESA/OSA workloads have already freed up their storage, which is due to the fact that the TRIM/UNAMP commands are not being passed down into the physical vSAN OSA. If you are using vSAN ESA for your physical setup, Guest TRIM/UNMAP is already enabled by default, so this is only applicable if you are using vSAN OSA.

To enable the Guest TRIM/UNMAP capability, you need apply the following ESXi Advanced Setting to your physical vSAN OSA.

[Read more...]

vSAN ESA HCL hardware mock VIB for Nested ESXi

by // 1 Comment

Whether you are configuring vSAN Express Storage Architecture (ESA) directly from vCenter Server or from VMware Cloud Foundation (VCF), the underlying ESXi hardware is automatically validated against the vSAN ESA Hardware Compatibility List (HCL) to ensure that you are using supported vSAN hardware.

In the case of vCenter Server, you can simply ignore the HCL warnings and accept the risks and proceed with the configuration but when using VCF, the operation is blocked to ensure customers have a good experience when selecting vSAN ESA when deploying a VCF Management or Workload  Domain.


With that said, there is workaround where you can create your own custom vSAN ESA HCL JSON based on the hardware that you have and then upload that to either Cloud Builder for setting up a new VCF Management Domain or to SDDC Manager for deploying a new VCF Workload Domain, which I have blogged about HERE and HERE.

The use of Nested ESXi is a very popular way to deploy VCF, especially if you are new to solution and allows you to easily experiment and learn. More recently, I have noticed an uptick in the interests for deploying VCF with vSAN ESA and while you can certainly generate a custom vSAN ESA HCL as mentioned earlier, the process still requires some effort and in some situations the vSAN ESA HCL could get overwritten leading some frustration in debugging.

After helping some folks debug their VCF environments recently, I was thinking about a better experience and leveraging another technique that may not be very well known externally ...

UPDATE (02/03/25) - This solution can also be used for a physical ESXi deployment for use with vSAN ESA and VCF.

[Read more...]