WilliamLam.com

Quick Tip - Using ESXCLI to upgrade ESXi 8.x throws MemoryError or Got no data from process

by // 28 Comments

Several users in the community have reported running into a memory error issue when attempting to upgrade their standalone ESXi hosts using this ESXCLI trick, which has been possible since ESXi 5.1 back in 2012.

[MemoryError]
Please refer to the log file for more details.


Initially, I was not able to reproduce in my lab environment at work, which was running ESXi 8.0 Update 2, but I still got an error message but it was different:

Got no data from process.
Command "LANG=en_US.UTF-8 /usr/lib/vmware/esxcli-software sources.profile.list -d "https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml" "
еxited with error code: 1


After checking my homelab environment which was also running ESXi 8.0 Update 2, I did see the same MemoryError message as reported by the community when using ESXCLI to list the available ESXi Image Profiles from VMware's online patch repository.

[Read more...]

Determining new VMware vSphere Foundation (VVF) & VMware Cloud Foundation (VCF) license usage in vSphere 8.0 Update 2b

by // 14 Comments

vSphere 8.0 Update 2b was just released last week and with this release, customers can now take advantage of the new included 100 GiB trial vSAN storage capacity for each deployed VMware vSphere Foundation (VVF) core for use with vSAN!

Note: If you would like to understand how much vSAN storage you are entitled to (100GiB for VVF and 1TiB for VMware Cloud Foundation (VCF)), check out the new inventory and calculator script in KB 95927 (brownfield) and KB 96426 (greenfield) for more details.

In addition to installing and/or updating your vCenter Server to vSphere 8.0 Update 2b, you will also need to login to Customer Connect to download your new VVF and/or VCF license keys that will activate your vSAN entitlement.

I have already received questions on how to determine whether an ESXi host has been licensed with the new VVF and/or VCF license keys and which you can do so by using the vSphere UI by navigating to Administration->Licensing->Licenses->Assets->Hosts or vSAN Clusters and using the various filters, but this can be time consuming when you have a large environment with various license editions.

This is where automation and vSphere API can help!

[Read more...]

VMware Event Broker Appliance (VEBA) v0.8.0

by // 5 Comments

I am very excited to share that we have just released our long awaited v0.8.0 of the VMware Event Broker Appliance (VEBA)! 🥳


The v0.8.0 release has been in the works for quite some time and because of the major architectural change in migrating to the VMware Tanzu Sources for Knative, we also needed to update all example functions to reflect the new event payload schema, refresh all user documentation and our VEBA website, which only performed during our spare cycles and typically in the evenings!

It has certainly been a long journey and I could not have done it without my colleague Robert Guske, who has been a machine in updating all of our documentation to make it easier to consume for both our existing and new users. 🙌

Last but now least, I want to give a huge thanks 👏 to my original partner in crime Michael Gasch, while he is no longer with VMware, he was still kind enough to help answer some questions while hitting some release automation issue over the weekend and was instrumental in helping me get the v0.8.0 release out!

Changelog for VEBA v0.8.0:

  • Updated Software Build-of-Material (SBOM) (See the VEBA BOM for detailed changes)
  • Replaced VMware Event Router with VMware Tanzu Sources for Knative
  • All VEBA endpoints now protected with basic authentication
  • New Google Chat notification function
  • Migrated function container images from Google (GCR) to Github (GHCR)
  • Updated all PowerShell/PowerCLI functions with the latest PS/PCLI base images
  • Improved website documentation
  • Various Bug Fixes and Code Improvement

Download for VEBA v0.8.0: