VCF 9.1 Clarifies Supported Upgrade Paths

Broadcom announced VMware Cloud Foundation (VCF) 9.1, described by the VMware Cloud Foundation blog as a private cloud release targeted at production AI, modern applications, and traditional workloads (VMware blog, May 5, 2026). William Lam published a technical explainer titled "VCF 9.1 - Demystifying Supported Upgrade Paths to 9.1" that maps supported upgrade combinations and includes visuals and an interactive planning tool (williamlam.com, May 23, 2026). CaptainvOps published a hands-on upgrade walkthrough showing a lab upgrade from VCF 9.0.2 to VCF 9.1, documenting VCF Operations upgrade steps and the new VCF license appliance deployment flow (captainvops.com, May 2026). Broadcom's knowledge-base article notes that an incorrect upgrade path can trigger known errors and states that VCF 9.1 upgrade binaries do not surface in VCF Operations 9.0 (knowledge.broadcom.com). The VMware VCF Upgrade Planner on GitHub and third-party tools such as VirtualBytes' Upgrade Path Advisor are available to validate supported hop paths and conversion requirements (vmware.github.io; tools.virtualbytes.io).

Editorial analysis - technical context: The collected reporting highlights three technical friction points practitioners should expect when planning an upgrade to VCF 9.1. First, upgrades span multiple product domains-vSphere (vCenter/ESX), NSX variants, Aria Operations, and Aria Automation-and supported sequences differ by combination, as presented in William Lam's upgrade-path visuals (williamlam.com). Second, tooling and orchestration behavior changes in 9.1, including an upgraded VCF Operations flow and a new VCF license appliance that CaptainvOps documents being deployed and registered as part of the process (captainvops.com). Third, vendor-side constraints matter: Broadcom KB flags that improper sequencing can cause errors and that 9.1 binaries may not appear in older VCF Operations instances, creating a dependency on correct pre-upgrade steps (knowledge.broadcom.com). William Lam also calls out that vSphere 8.x is EOS, which is a relevant lifecycle datapoint when assessing supported starting states (williamlam.com).

Product upgrades that cross multiple control planes and network/storage domains are a common and high-risk operational activity for private cloud operators. Organizations upgrading to a major platform release while trying to retain on-prem control for data sovereignty or cost reasons face both sequence complexity and transient compatibility gaps. The availability of an interactive upgrade planner (William Lam) and an official GitHub VCF Upgrade Planner reflects a broader industry pattern where practitioners rely on automation and preflight validation tools to reduce human error. The Broadcom KB entry formalizing error scenarios underscores why operators should treat upgrade sequencing as part of change-control and test validation activities.

For practitioners: monitor three indicators while preparing for VCF 9.1 upgrades.

• •Whether your VCF Operations instance displays 9.1 binaries, as Broadcom's KB documents cases where binaries do not surface in VCF Operations 9.0 (knowledge.broadcom.com).
• •The status of NSX and Aria Automation in your environment, since GitHub's VCF Upgrade Planner documents that certain components can only be upgraded via the VCF conversion process (vmware.github.io).
• •Community and vendor fixes to tooling steps: CaptainvOps' lab notes highlight UI and workflow changes and a license-appliance auto-registration behavior that operators should validate in a test environment (captainvops.com). Observers can also use VirtualBytes' Upgrade Path Advisor to validate supported hop paths before changing production systems (tools.virtualbytes.io).

The available reporting and tools make clear that upgrading to VCF 9.1 is feasible but operationally nontrivial. Organizations should plan end-to-end validation and use vendor and community upgrade planners to confirm supported sequences. William Lam's visuals and interactive tool, Broadcom's KB, the GitHub planner, and community walkthroughs together form a practical ecosystem for preflight checks and dry-run testing prior to production upgrades.