WilliamLam.com

Creating custom ESXi images using vSphere Lifecycle Manager (vLCM) UI and PowerCLI cmdlets for vSphere 8

by // 26 Comments

I have started to use vSphere Lifecycle Manager (vLCM) more and more, especially after upgrading to vSphere 8 as it will be the primary lifecycle management solution going forward for both vSphere image and configuration management.

The other reason for using vLCM is that vSphere Update Manager (VUM) baselines have also been deprecated in vSphere 8 and while you can still use it for now, it should not come as a surprise that VUM and its functionality will be removed in the future and all of its workflows including the use of vSphere Image Builder should also be transitioned over to using vLCM.

One of the most common and basic workflow for customers today is creating custom ESXi images (ISO or Offline Bundle) that includes additional ESXi drivers. Since vLCM is probably new to most folks (including myself), I wanted to share how you can create your own custom ESXi images using both the vLCM UI (which can be a bit non-intuitive) as well as the new PowerCLI cmdlets that was jus released today as part of PowerCLI 13.0 release that adds support for both vLCM and vSphere 8!

[Read more...]

vSphere UI Client Plugin named N/A after vSphere 8 upgrade

by // 16 Comments

This past weekend I finally got a chance to upgrade my personal homelab to vSphere 8, which went super smooth! As shared on Twitter and Mastadon, I started with my VCSA which was running vSphere 7.0 Update 3h and once that had completed and running for a couple of days, I then upgraded my single ESXi host which was running 7.0 Update 3g which runs on Supermicro E200-8D.

After was functional after the upgrade, including the VMware Event Broker Appliance (VEBA) UI Plugin 😀

This morning, I happened to navigate over to the vSphere UI Client Plugin screen under Administration->Solutions->Client Plugins and I noticed I had one plugin named "N/A" and was was showing incompatible.


I was not sure what the plugin was and raised this internally with the vSphere UI team on whether this was expected and if there was something I needed to do. It turns out this was the default vCloud Availability plugin for vCloud Director that ships with a vCenter Server deployment and it uses the deprecated local plugin architecture and this particular version of plugin is no longer applicable or compatible with vSphere 8.

[Read more...]

Virtual NUMA (vNUMA) and CPU Hot-Add support in vSphere 8

by // 1 Comment

While looking for something in the vSphere 8.0 API Reference, I stumbled onto a new VM configuration setting in vSphere 8 called exposeVnumaOnCpuHotadd which looks quite interesting and has the following description:

Capability to expose virtual NUMA when CPU hotadd is enabled. If set to true, ESXi will consider exposing virtual NUMA to the VM when CPU hotadd is enabled. If set to false, ESXi will enforce the VM to have single virtual NUMA node when CPU hotadd is enabled. If unset, the VM continue to follow the behavior in last poweron.

This actually reminded me of question that we got during one of our vSphere 8 Meet the Experts (MTE) sessions at VMware Explore Barcelona and whether there were any new enhancements to vNUMA when CPU hot-add is enabled, which I was not aware of any at the time. The vNUMA and CPU Hot-Add issue is detailed in this blog post by no other than my buddy Frank Denneman and here is a quick summary of the issue:

CPU Hot-Add is not compatible with vNUMA, if hot-add is enabled the virtual NUMA topology is not exposed to the guest OS and this may impact application performance.

[Read more...]