WilliamLam.com

Quick Tip - Enabling ESXi Coredumps to be stored on USB

by // Leave a Comment

I was recently working with Engineering to reproduce an issue which causes an ESXi PSOD (Purple Screen of Death) and I wanted the generated ESXi coredump to simply write to the USB device, which I could easily grab.

As of ESXi 7.x, I know we had removed a few of the old ESXi kernel boot options for allowing ESXi to store coredumps on a USB device and the using the ESXi kernel boot option allowCoreDumpOnUsb=TRUE should now be used, however I was struggling to get it to work.

Since I was using a debug version of ESXi, I needed to install ESXi from scratch and I thought I could simpply add the required kernel option, as shown in the screenshot below, and I had assumed it would automatically configure the ESXi coredump file to be stored on the VMFS-L volume residing on the USB device.


After a couple of attempts, I finally realized that this particular ESXi kernel boot option, is literally that, a boot option that is only applicable after the initial ESXi installation. 🤦 Unlike other ESXi kernel boot options which can be used during the initial installation which would apply certain configuration changes, this setting applies after ESXi has been installed. Once I appended the setting, the ESXi coredump file was created in the VMFS-L volume and I was then able to reproduce the issue and generate vm-support bundle that included the coredump!

Is my vSphere Cluster managed by vSphere Lifecycle Manager (vLCM) as a Desired Image or Baseline?

by // 11 Comments

Prior to vSphere 7.0, ESXi lifecycle management has been provided by vSphere Update Manager (VUM), which has been around for more than a decade plus and is most likely what you are still using today. With the release of vSphere 7.0, VMware introduced a brand new lifecycle management solution for ESXi called vSphere Lifecycle Manager (vLCM), which you can read more about HERE.


While VMware has made it clear that vLCM will be the future going forward for ESXi lifecycle management, we also understand that most customers will still be using the existing VUM-based solution and we wanted to make sure it was easy to  transition between the two solutions, especially within the vSphere UI.

An interesting question was recently brought up was how to determine whether a vSphere Cluster was using the new vLCM solution based on desired images versus VUM, which uses baselines?

Note: If you are not familiar between vLCM Desired Image and VUM Baselines, be sure to check out this helpful resource HERE.

[Read more...]

How to automate adding a license into vCenter Server with custom label? 

by // Leave a Comment

When adding a license key into vCenter Server using the vSphere UI, users have the ability to provide a custom label that is then associated with that specific license key.


This is certainly more useful than the system default label which uses "License N", where N is an incrementing number.

While the majority of license management can be fully automated using the vCenter Server LicenseManager API, adding a license key with a custom label is unfourntately an operation that is currently not possible with the public API.

With that said, there is a way in which you can still automate this operation 🙂

[Read more...]