WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple
You are here: Home / Automation / Retrieving CPU Microcode revision from ESXi in vSphere 8.0 Update 3

Retrieving CPU Microcode revision from ESXi in vSphere 8.0 Update 3

06.28.2024 by William Lam // Leave a Comment

Whether you are applying a CPU microcode update through a hardware vendor's BIOS update or an ESXi update/upgrade, verifying the CPU microcode revision within ESXi is not as easy as it could be.

Today, if you wanted to get the current CPU microcode revision from ESXi, you would need to enable SSH and then use the vsish interface to retrieve this information by running the following command:

vsish -e cat /hardware/cpu/cpuList/0 | grep "microcode" -A2

While you can retrieve the CPU microcode revision, the method and required interfaces was less than ideal, especially at scale. Given ESXi already exposes a number CPU attributes via the ESXCLI interface, which includes programmatic access when using PowerCLI, I thought it would be a nice feature to also include the CPU microcode revision as part of the output and had filed an internal feature enhancement a few years back.

Today, I am happy to share that the feature I had requested awhile back is now shipping in the latest vSphere 8.0 Update 3 release and can be accessed by using the following existing ESXCLI (local and remote) command:

esxcli hardware cpu list


As you can see from the screenshot above, a new Microcode Revision property is now available and provides the current CPU microcode revision as detected by ESXi.

If you prefer to retrieve the new CPU microcode property using PowerCLI, here is a quick PowerCLI snippet that you can use:

$esxcli = Get-EsxCli –VMHost (Get-VMHost 192.168.30.5) -V2
$esxcli.hardware.cpu.list.Invoke()[0]

More from my site

  • Useful NVMe Tiering reporting using vSphere 8.0 Update 3 APIs
  • Nested ESXi Virtual Appliance & USB Network Native Driver for ESXi for vSphere 8.0 Update 3
  • Sharing a single NVMe device with NVMe Tiering? 
  • New ESXi-Arm Fling based on 8.0 Update 3b
  • How much Virtual Machine memory is using NVMe Tiering?

Categories // Automation, ESXCLI, ESXi, vSphere 8.0 Tags // ESXi 8.0 Update 3, vSphere 8.0 Update 3

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • VMware Flings is now available in Free Downloads of Broadcom Support Portal (BSP) 05/19/2025
  • VMUG Connect 2025 - Minimal VMware Cloud Foundation (VCF) 5.x in a Box  05/15/2025
  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025

 

Loading Comments...