WilliamLam.com

Updates to USB Network & NVMe Community Driver for ESXi 7.0 Update 3

by // 16 Comments

Happy Thursday! I know many of you have been asking about the status and support for ESXi 7.0 Update 3 and the popular USB Network Native Driver for ESXi. It has taken a bit longer as Songtao (the Engineer behind the Fling) has also been extremely busy and was also recently on PTO. Although I know this is something folks use extensively, I do also want to remind everyone that this is provided as a Fling, which means it is developed and supported as time permits. I will certainly do my best to help get new releases out aligning with ESXi updates and as a reminder, a new version of the USB Fling will ALWAYS be required for major releases of ESXi, which also includes update releases.

[Read more...]

First look at the Supermicro E100-12T

by // Leave a Comment

I first came to learn about Supermicro's E100-9W platform last year, which I had first written about here. The E100-9W is a fanless kit that is part of Supermicro's Embedded IoT family and targets similiar use cases to the Intel NUC such as Industrial Automation, Retail, Smart Medical Systems, Kiosks and Digital Signage. Although the E100-9W was just released in 2020, it was actually using a much older Intel 8th Generation CPU due to some constraints with Intel's embedded CPU roadmap.

Supermicro did mention last year that a Tiger Lake-based model was in the works and last week, I just got my hands on a pre-production unit for their 2nd generation of this platform called the E100-12T.

[Read more...]

Single node Supervisor Control Plane VM for vSphere with Tanzu now possible in vSphere 7.0 Update 3

by // 8 Comments

Last year, when vSphere with Kubernetes (original name of what is now vSphere with Tanzu) was first released, I had shared a process on how to deploy a minimal setup including a detailed write-up for setting up vSphere with Tanzu on an Intel NUC with just 32GB of memory.

I am always looking for ways to simplify and ease the consumption of various VMware technologies within a homelab and I was pretty happy with the tweaks that I could make to reduce the amount of resources needed to run vSphere with Tanzu. Instead of needing to deploy three Supervisor Control Plane VMs, the modification to the vSphere with Tanzu configuration, allowed me to deploy just two Supervisor Control Plane VMs. It was unfortunate that deploying only a single Supervisor Control Plane VM at the time was not possible due to a known issue.

While deploying a pre-release of vSphere 7.0 Update 3 in one of my lab environments, I was going through the process of tweaking the vSphere with Tanzu configuration before enablement and I figure why not try the one node setting, in case it was fixed 🤷 I honestly was not expecting it to work since there was an internal bug that was filed awhile back and I had not seen the bug closed. To my complete surprise, vSphere with Tanzu enabled successfully and there was just a single Supervisor Control Plane VM!


It turns out that someone from Engineering must have fixed the issue and a single Supervisor Control Plane VM is now possible with the upcoming release of vSphere 7.0 Update 3! 🥳

UPDATE (07/02/24) - As of vSphere 8.0 Update 3, you no longer have the ability to configure a single Supervisor Control Plane VM using the minmaster and maxmasters parameters, which have also been removed from /etc/vmware/wcp/wcpsvc.yaml in favor of allowing users to control this configuration programmatically as part of enabling vSphere IaaS (formally known as vSphere with Tanzu). The updated vSphere IaaS API that allows users to specify number of Supervisor Control Plane VM will not be available until the next major vSphere release. While this regressed capability is unfortunate, it was also not an officially supported configuration and for users who wish to specify the number of Supervisor Control Plane VM using YAML method, you will need to use an earlier version of vSphere.

To change the settings, you will need to SSH to the VCSA and edit the following configuration file /etc/vmware/wcp/wcpsvc.yaml and search for minmasters and maxmasters and change the value from 3 to 1.

minmasters: 1
maxmasters: 1

For the changes to go into effect, you will need to restart the vSphere with Tanzu service which is listed as wcp by running the following command:

service-control --restart wcp

In addition, for homelab purposes, you may also want to change the controlplane_vm_disk_provisioning parameter, which defaults the Supervisor Control Plane VM to Thick provisioned rather than Thin, which many folks use in their labs.

controlplane_vm_disk_provisioning: "thin"