vSphere 8 end of support (11 Oct 2027): the VCF 9.1 upgrade path and costs

Summary. Broadcom ends general support for vSphere 8.0, covering ESXi 8.x, vCenter 8.x and vSAN 8.x, on 11 October 2027, five years after its 11 October 2022 release. A companion article puts VCF 5.2.x, NSX 4.x, HCX 4.x, Aria Automation and Aria Operations 8.18.x and VMware Live Recovery 9.0.x on the same date, after which there are no new patches and no technical support. Broadcom's recommended destination is VMware Cloud Foundation (VCF) 9 or vSphere Foundation (VVF) 9; the current release is 9.1.1, generally available since 3 September 2026. Both are per-core subscriptions with a 16-core minimum per CPU; VCF includes 1 TiB of vSAN per licensed core and VVF 0.25 TiB. We found no public list price, so your written quote is the only number that counts, and perpetual licence holders must convert to subscription before upgrading. Standalone vSphere needs vCenter and ESX 8.0 Update 3 or later first, VCF 5.2 upgrades in seven stages, and a licence update is due at least every 180 days. Hardware can block you: Broadwell-EP Xeon E5-2600 v4 hosts cannot install 9.x, while Cascade Lake and AMD EPYC Rome run 9.x but not the next major release. From 1 November 2026, 344 days remain. Start the core count now.

About this article. This guide is for teams that intend to stay on VMware, or need the upgrade facts before deciding. On 1 November 2026 we checked lifecycle dates, licensing rules and upgrade steps against Broadcom knowledge base articles, TechDocs and VMware documents. We found no Broadcom price list for VCF or VVF, so no prices appear here. No vendor paid for inclusion. Researched with AI assistance and reviewed by our editorial team.

If you are pricing an exit, read our VMware alternatives 2027 comparison and our earlier VMware exit cost model.

What ends on 11 October 2027

Broadcom's end-of-service article puts the whole VMware 8-era stack on one date, so every component needs a 9.x answer at the same time.

Two details matter. VVF for VDI environments follow a separate lifecycle, with no end date announced as of Broadcom's February 2026 note. And perpetual licences keep working after support lapses: hosts and VMs keep running with all licensed features, but patch downloads and support cases stop, and major-version upgrades should not be attempted during a coverage gap.

What changed in the past year

1. VCF 9.1 arrived, then 9.1.1. Broadcom published VCF 9.1 upgrade guidance on 18 June 2026, and 9.1.1 reached general availability on 3 September 2026. Upgrades to 9.1 add two mandatory pieces: a VCF management services cluster and a headless VCF License Server appliance.

1. Compliance moved to an add-on. In 9.1, configuration management and compliance remediation moved into the paid VMware Advanced Cyber Compliance (ACC) add-on. Baseline VCF keeps a Security Operations dashboard and audit trail.

1. A reprieve for Skylake-SP. On 18 September 2026 Broadcom extended support for first-generation Xeon Scalable (Skylake-SP) servers to all of VCF 9.x in deprecated mode, using an override install procedure. It will not extend beyond 9.x.

1. Regional availability diverged. Broadcom told The Register in December 2025 that VVF is no longer available in some EMEA countries, though most still have it, and that vSphere Standard remained on sale.

1. A new vSphere Standard was promised, not delivered. In September 2026, VMware product chief Paul Turner told The Register that a new release is coming. Broadcom's datasheet still limits Standard and Enterprise Plus to versions up to 8 Update 3, and we found no date, specification or price on 1 November 2026.

VCF 9.1 vs VVF 9.1: what each subscription includes

VCF and VVF share one licensing model from 9.0, but the feature gap is wide. The table summarises Broadcom's 9.1.1 comparison of 14 October 2026.

Broadcom's 9.1 FAQ says the VCF 9 licence also covers HCX and VCF Private AI Services. Avi Load Balancer, vDefend Firewall and VMware Live Recovery are licensed separately, and Data Services Manager became a separate purchase on 5 May 2025. If you run the built-in NSX load balancer, Broadcom allows use until 30 May 2027 only for customers who have secured equivalent Avi licences, at one Avi service unit per 100 qualified VCF cores.

Broadcom's upgrade-paths chart maps old vSphere Standard, Enterprise and Enterprise Plus customers to VVF, and customers who had NSX or Aria Suite Enterprise alongside vSphere to VCF.

Licensing: per-core rules, minimums and regional differences

The counting rule. KB 313548 requires at least 16 physical cores to be licensed for each CPU in every ESXi host, even if the CPU has fewer. Its own example: one host with two 8-core CPUs and one with two 24-core CPUs is 32 plus 48, so 80 cores. Count every physical core; Broadcom warns that cores disabled in BIOS can make its tool's results inaccurate. vSAN is counted separately, in raw TiB contributed by all hosts.

How licences attach. In 9.x you assign a primary licence to a vCenter instance, and ESX hosts and other components connected to it are licensed automatically. Subscriptions for the same product, unit and Site ID pool into one default licence, which you can split.

VCF Operations is mandatory. Licensing in 9.x runs through a VCF Operations instance and the VCF Business Services console. After an upgrade from version 8, components run in evaluation mode for up to 90 days. You must then update licences at least once every 180 days. Miss that window and Broadcom treats licences as expired: hosts disconnect from vCenter and you cannot start workloads. Broadcom says existing workloads are not proactively stopped when evaluation expires; its 180-day text does not address them, so confirm this with Broadcom. Air-gapped sites can use disconnected mode and exchange usage files manually.

Mixed versions are allowed. VCF 5.x environments keep their existing keys while new 9.x environments use the new model, so a phased upgrade does not force a big-bang licence swap.

The 72-core story. Licenseware recounts a March 2025 distributor memo describing a 72-core minimum per order line and a 20 percent late-renewal surcharge. Neither appears in Broadcom's public licensing documents, and Licenseware reports the 72-core line was treated as unofficial or walked back from April 2025. Get order minimums and late-renewal terms in writing on your quote.

Regional differences. First, VVF has been withdrawn in some EMEA countries, and Broadcom says availability can vary by region. Second, VCF Edge carries different rules: 8 cores minimum per CPU, at least 10 sites licensed within a year, and no more than 256 cores per site. Third, VCF licences bought after 13 December 2023 by the end customer can be ported to Broadcom's list of certified cloud services, but licences obtained through OEMs or provider programmes cannot.

Run Broadcom's counting tool before you ask for a quote. On vCenter or vSAN 8.0 Update 3, use the modified module attached to KB 400416, because the original calls an API missing from that release.

            # Broadcom KB 313548 licence counting tool (PowerCLI 13.3+, PowerShell 7.4.6+)
Connect-VIServer -Server vcenter.example.local
Import-Module .\FoundationCoreAndTiBUsage.psm1
Get-FoundationCoreAndTiBUsage -DeploymentType VCF -CSV -Filename "vcf-cores.csv"
Get-FoundationCoreAndTiBUsage -DeploymentType VVF -CSV -Filename "vvf-cores.csv"
          

Hardware compatibility: check CPUs first

Broadcom's CPU policy has two phases: deprecated (the installer warns, still supported for the whole 9.x line) and discontinued (the installer halts).

Beyond CPUs, check four things. Your exact server model must be listed in the Broadcom Compatibility Guide; models marked VCF Supported. Confirm w/Vendor get VMware software support, but BIOS and firmware support comes only from the OEM. vSphere Lifecycle Manager baselines are not supported in 9.x, so every cluster must move to image-based management during the upgrade. vVols are deprecated from 9.0 and will be removed in a future release. And pre-existing NSX Federation deployments cannot be imported into VCF 9.1.

If many hosts sit in the deprecated row, 9.x buys time but not a full platform life: the next major release will not install on them.

The upgrade sequence

Path A: VCF 5.2.x to VCF 9.1

Broadcom's Professional Services sequence has seven stages, and VCF 4.x must reach 5.2 first. A 5.2.x estate can go straight to 9.1.1, starting with VCF Operations 9.1.1; use the latest binaries.

1. Assess and remediate. Complete the Planning and Preparation Workbook, validate hardware, confirm a temporary IP per vCenter, check certificates and passwords, and run the SDDC Manager precheck.

1. Upgrade Aria Operations to VCF Operations 9.1. It must be on 8.18 first. If you have no Aria Operations, deploy VCF Operations; it is mandatory in 9.x. A Cloud Proxy in the first VCF instance is required.

1. Upgrade SDDC Manager to 9.1.

1. Deploy VCF management services and the License Server from the Build > Lifecycle tab.

1. Upgrade the management domain core. NSX first (two-step, because NSX VIBs are now part of ESX), then vCenter using a Reduced Downtime Upgrade (required between major versions), then ESX hosts on vLCM images, then the NSX Edge cluster.

1. Bring over the other management components. Import Aria Automation into VCF Operations and upgrade it to VCF Automation (Broadcom often suggests a separate workstream if you have custom code). Aria Operations for Networks must reach 6.14 before import. Aria Operations for Logs has no direct upgrade: deploy VCF log management and transfer the data. Replace VMware Identity Manager 3.3.x with the VCF Identity Broker.

1. Finalise. Upgrade distributed switches and the vSAN on-disk format, configure licensing, then upgrade the VI workload domains.

Path B: standalone vSphere 8 (no SDDC Manager or NSX)

Broadcom documents this as a first phase, for estates without SDDC Manager, NSX or Aria Operations for Logs. Prerequisites: vCenter 8 Update 3 or later, ESX 8 Update 3 or later, and optionally vSAN 8 Update 3 and Aria Operations 8.18.x. The order is: upgrade Aria Operations or deploy VCF Operations 9.1, deploy the License Server, upgrade vCenter, upgrade ESX hosts, then the vSAN on-disk format and vSAN File Service. Broadcom's VCF Upgrade Planner tool walks through it.

From there you can stay on VVF, or converge into full VCF. The VCF Installer converts an existing vCenter 8.0 Update 3 environment, including NSX 4.2, into a VCF management domain; VCF Operations imports further vCenters as workload domains. Broadcom says neither requires downtime or a migration of applications or data, but it adds infrastructure per whole vCenter, not per cluster.

Cost considerations, with a worked example

We found no Broadcom per-core price, so this example counts licensable units and leaves price as a variable. It is illustrative, not a client case. The rules come from KB 313548.

Today: 8 hosts, each with two 12-core Cascade Lake CPUs (192 physical cores) and 30 TiB of raw vSAN capacity (240 TiB total).

• Licensable cores: 8 × 2 × 16 = 256. The 16-core floor adds 64 cores, a 33% uplift.

• VCF vSAN entitlement: 256 × 1 TiB = 256 TiB, which covers 240 TiB. No add-on.

• VVF vSAN entitlement: 256 × 0.25 = 64 TiB, so 240 − 64 = 176 TiB of vSAN add-on.

After a refresh: 4 hosts, each with two 24-core CPUs (192 physical cores) and 60 TiB raw (240 TiB total).

• Licensable cores: 4 × 2 × 24 = 192, with no floor penalty. That is 64 fewer than today, a 25% cut.

• VCF entitlement: 192 TiB, so a 48 TiB add-on. VVF entitlement: 48 TiB, so a 192 TiB add-on.

Three-year subscription: if P is your quoted annual price per core, today's estate costs 256 × 3 × P = 768P, and the refreshed estate 192 × 3 × P = 576P. The difference, 192P, is what you set against new hardware, which also replaces CPUs that the next major VMware release will not support.

Also model: replacement servers for discontinued CPUs, ACC for compliance remediation, Site Recovery Manager or ACC for orchestrated DR, Avi licences if you depend on the NSX load balancer, Data Services Manager, and services for Aria Automation code.

Timeline: back-planning from 11 October 2027

If your VMware renewal falls before mid-2027, pull the decision forward.

Upgrade, switch to VVF, or leave: decision table

India and EU notes

India. We found no Broadcom rupee price list, so expect quotes through partners. Disconnected licensing suits regulated or air-gapped sites, but someone must own the 180-day usage-file cycle, because a missed update stops new workloads.

EU. Check VVF availability with your partner before planning a VVF downgrade, since Broadcom has withdrawn it in some EMEA countries. vSphere Standard is no fallback for now: it is available only up to 8 Update 3, which loses support on the same date. Teams weighing a move to public cloud should also read our note on the EU Data Act ban on cloud switching fees.

How eCorpIT can help

eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our data centre and cloud networking team runs the core and vSAN count, checks every host against Broadcom's compatibility guide, models VCF, VVF and exit options against your written quotes, and plans the upgrade with a tested rollback at each stage. Talk to us at /contact-us/.

Last updated: 1 November 2026.

References

1. End of General Support for vSphere 8.0 (KB 459135) — Broadcom Knowledge Base

1. Upcoming End of Service for vSphere 8, vSAN 8, Aria 8, NSX 4 and VCF 5 product suite (KB 456708) — Broadcom Knowledge Base

1. VMware Cloud Foundation 9.1.x release notes — Broadcom TechDocs

1. Counting cores for VMware Cloud Foundation and vSphere Foundation and TiBs for vSAN (KB 313548) — Broadcom Knowledge Base

1. VMware Cloud Foundation 9.1 frequently asked questions, 3 September 2026 — VMware by Broadcom

1. Upgrading vSphere 8 and optionally vSAN and Aria Operations 8 to 9.1.x — Broadcom TechDocs

1. How to upgrade to VMware Cloud Foundation 9.1, 18 June 2026 — VMware Cloud Foundation Blog

1. Updating licenses and viewing the license usage file, VCF 9.1 — Broadcom TechDocs

1. CPU support deprecation and discontinuation in VCF releases (KB 318697) — Broadcom Knowledge Base

1. VVF for VDI lifecycle support (KB 428674) — Broadcom Knowledge Base

1. Perpetual licence functionality after support and subscription expiration (KB 429208) — Broadcom Knowledge Base

1. Deprecated CPU systems and servers in ESX 9.0 and implications for support (KB 428874) — Broadcom Knowledge Base

1. VMware kills vSphere Foundation in parts of EMEA, 11 December 2025 — The Register

1. VMware swings its focus back to low-end server virt, promises vSphere Standard upgrade, 2 September 2026 — The Register

1. vSphere product line comparison datasheet — VMware by Broadcom

1. Broadcom shifts course: vSphere Standard aims to win back small VMware customers — ITdaily

1. Licensing model, VCF 9.1 — Broadcom TechDocs

1. VMware Cloud Foundation 9.1.1 and VMware vSphere Foundation 9.1.1 feature comparison and upgrade paths, 14 October 2026 — VMware by Broadcom

1. NSX Load Balancer to VMware Avi Load Balancer migration (KB 439411) — Broadcom Knowledge Base

1. VMware's official floor is 16 cores per CPU, not 72 — Licenseware

1. Licensing script in KB 313548 fails (KB 400416) — Broadcom Knowledge Base

1. VMware Cloud Foundation 9.1.1.0 release notes, 3 September 2026 — Broadcom TechDocs