WilliamLam.com

ESXi on GMKtec NucBox K11

by // 6 Comments

The GMKtec NucBox has been growing in popularity amongst the VMware community as a modern AMD Ryzen-based alternative to the Intel/ASUS NUC, offering many of the same advantages while avoiding some of the drawbacks of Intel's Hybrid CPU architecture.

In preparation for my upcoming session at the inaugural VMUG Connect Conference in April, I have been experimenting with several modern hardware options, with the goal of deploying the full VMware Cloud Foundation (VCF) solution for use within a lab environment, while still staying budget friendly!

I know several folks have had great success with the GMKtec NucBox K8 Plus and it just so happens, while browsing the GMKtec website, I noticed an additional NucBox has just been released called the K11.


While the differences between the K8 Plus and K11 is pretty minimal, I was interested in validating some new hardware add-ons, so getting the latest hardware would hopefully give me the best chance!

In collaboration with the VMware {Code} team, I was able to get hands on with the latest GMKtec NucBox K11!

[Read more...]

Quick Tip - VMware Cloud Foundation (VCF) Bringup fails without persistent ESX-OSData

by // 5 Comments

You will never run into this problem if you follow current recommended practices to install the ESX-OSData volume on a persistent storage device that could either be dedicated and/or co-located your ESXi installation.

For those deploying VMware Cloud Foundation (VCF) in a lab environment, you might attempt to reserve the limited number of storage devices for use with vSAN and decide to install ESXi on a USB device, which is perfectly fine but if you do not select a persistent storage device for the ESX-OSData volume, then it will default to use the ESXi ramdisk.

I recently observed that if you have such a configuration, the VCF Cloud Builder Bringup process will fail after attempting (three times) to re-deploy the vCenter Server Appliance (VCSA).


As you can see from the screenshot above,  VCF Cloud Builder UI does not provide any details and ask users to look at the vCenter Server installation logs.

[Read more...]

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