I have been a huge fan of the VM Service capability, which has been an integral part of vSphere with Tanzu since its inception with the release of vSphere 7.0 Update 2. The VM Service had another major update last year that enabled further customization of workloads with the Sphere 8.0 release. What makes the latest update so exciting for vSphere with Tanzu users is that in vSphere 8.0 Update 2, the VM Service now officially supports deploying Microsoft Windows VMs and can also create VMs using all the rich VM configuration options that the vSphere platform supports!

I just got to try out the new VM Service feature yesterday and deployed a Windows OVF that I had built almost a year ago, which I have waiting for this feature to finally ship! 😀

I typically save my VM Service YAML manifest files so that I can easily reuse them but after performing the kubectl apply, I noticed nothing was being deployed and when I went to retrieve more details by running:

kubectl get vm -o yaml

I noticed the following error message:

message: 'Failed to get the VM''s image: windows-desktop-10'

[Read more...]

I recently upgraded my single ESXi host, which is used for my personal vSphere Homelab, to the latest patch release of ESXi 7.0 Update 3e using ESXCLI and connecting directly to VMware's online depot.

I still love how easy it is to update a single ESXi host using ESXCLI and using VMware's Patch Repo -

ESXI_VERSION=ESXi-7.0U3e-19898904-standard

"esxcli software profile update -d https://t.co/cs4yUyvnxQ -p ${ESXI_VERSION}"https://t.co/77Iu0K0hUG pic.twitter.com/nLhx5ztmNa

— William Lam (@lamw) July 7, 2022

This is the same method that I have been using since 2012 when I first wrote about this in a blog post using a pretty cool method of upgrading/patching a single ESXi hosts. If you are fortunate to have multiple ESXi hosts and a vCenter Server, you definitely should be using vSphere Lifecycle Manager (vLCM) provided by vCenter Server rather than the ESXCLI method, especially as there are no upgrade pre-checks built into in compared to vLCM.

Although my environment has a vCenter Server, I can not use vLCM because I only have a single ESXi host and ESXCLI method is really the only viable option. Customers may have a simliar setup, whether that is for a homelab, smaller environment or simply do not have a vCenter Server. Using the ESXCLI workflow, it certainly is the easiest if your ESXi host can reach VMware's online repo which is hosted at hostupdate.vmware.com, however this may not be possible for everyone, especially for remote locations where connectivity may be spotty or simply is not allowed to have outbound connectivity.

For such environments, you might be interested in hosting your own ESXi update repo and as always, I was curious on how one could setup something simliar without much effort and well, here we are with this blog post 😀

[Read more...]