WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
    • VMware Cloud Foundation 9
  • VKS
  • Homelab
    • Hardware Options
    • Hardware Reviews
    • Lab Deployment Scripts
    • Nested Virtualization
    • Homelab Podcasts
  • VMware Nostalgia
  • Apple
You are here: Home / VMware Cloud Foundation / Quick Tip - Disable ESX Live Patching enforcement to enable vSphere Supervisor

Quick Tip - Disable ESX Live Patching enforcement to enable vSphere Supervisor

07.25.2025 by William Lam // Leave a Comment

While enabling the vSphere Supervisor on my VMware Cloud Foundation (VCF) 9.0 setup, I came across an error I had not seen before as I have performed this numerous times across both vSphere 8.x and vSphere 9.0:

A general system error occurred: Solution specification in the image are incompatible with hosts 'esx02.vcf.lab, esx01.vcf.lab'


I was going through various vCenter Server logs files, but was not able to find anything useful and the strangest part was the vSphere Supervisor Service was already up and running but something about incompatibility and image.

As a last resort, I navigated over to the "Updates" tab for my vSphere Cluster and sure enough, the reason for the error was quite clear from vSphere Life Cycle Manager (vLCM) as you can see from the screenshot below.


It looks like when you configure the vLCM Remediation Settings for the cluster to "Enforce Live Patching", it will only allow updates that support ESX Live Patching and the vSphere Supervisor Service update does not and hence the error. I was hoping that this configuration purely meant that it will attempt to use ESX Live Patching when applicable but if not, it will default to non-live patching, but guess I made the wrong assumption.

The workaround was quite easy, simply update the remediation setting and uncheck the box for live patching and the vSphere Supervisor Service enablement completed without any issues.


Needless to say, I think we can certainly improve on the overall user experience for this specific error and help bubble up the message to quickly help users understand what the issue is and this is something I have already shared with the vLCM PM.

Categories // VMware Cloud Foundation Tags // VCF 9.0, vSphere Supervisor

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

  • Automating the Reporting of VCF Workload Domain Import Pre-Check Validations 12/04/2025
  • Import vCenter Server with Single ESX Host as new VCF Workload Domain? 12/03/2025
  • Managing Storage for VCF Automation (VCFA) Content Library Transfer Spooling Area 12/01/2025
  • Enabling new vSphere Kubernetes Service (VKS) Cluster Management for VCF Automation (VCFA) 11/21/2025
  • Realtek Network Driver for ESXi 11/12/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...