vSphere 8 end of general support: the dates, what changes and what to plan now

The dates, and who publishes them

Broadcom has put the month in writing. In an August 2025 post on its VMware Cloud Foundation blog, addressed to SAP customers, it wrote that vSphere 8 “will be supported until October 2027, with an optional two-year Extended Support period available for purchase”. The day, 11 October 2027, is on no public Broadcom page we could read; MSSP Alert reported on 15 September 2026, citing CRN, that vSphere 8 perpetual licence holders stop receiving security patches “after October 11, 2027”. Before a contract depends on the day, confirm it on Broadcom’s product lifecycle page in its support portal.

The next milestone is public: Broadcom’s end of technical guidance list gives 11 October 2029 for VMware ESXi 8.0, vCenter Server 8.0 and vSAN 8.0. For the vSphere 7 dates, Broadcom footnoted technical guidance: “Does not apply to Broadcom contracts. Applicable to valid VMware contracts only.” The list carries no notes, so ask which applies to your contract before you count on 2029.

Broadcom gives ESXi, vCenter and vSAN 7.0 the same dates, and their 8.0 versions the same guidance date. Broadcom’s end of technical guidance list (undated, read 28 September 2026); VMware Cloud Foundation blog, 25 July 2024, 16 July 2025 and 1 August 2025; KB 415405; MSSP Alert, 15 September 2026.

What ends with general support

Broadcom’s maintenance handbook of 8 June 2026 covers “all generally available versions and releases of Broadcom Software” not designated end of service or end of life. After the end of service date Broadcom “has no obligation to provide Support” for the version, while “the published service and security packs and fixes will continue to be available as part of self-service support for the duration of your remaining active Maintenance term”, and it makes “reasonable efforts” to give at least twelve months’ notice. For vSphere 7, Broadcom called 2 October 2025 the end of service date and wrote that customers still running 7.x “will not be able to receive product support, security patches and updates”. The only technical guidance definition we found on Broadcom’s knowledge base is VMware’s for vSphere 6.0 (KB 318892): “primarily through the self-help portal”, without “new security patches or bug fixes unless otherwise noted”.

Critical patches. KB 314603 is the documented exception: patches for Critical Severity Security Alerts, with a CVSS score of 9.0 or higher, go to “all customers, including those with expired support contracts”, for supported versions, and “Supported versions of VMware vSphere are version 8.x.” We found no Broadcom document that extends this beyond the end of general support, and the press report above has security patches for vSphere 8 perpetual holders stopping after 11 October 2027.

Extended Support. Broadcom described its model before 9.0 as five years of general support with, “in certain cases”, two more years of Extended Support to buy, and its August 2025 post names that option for vSphere 8. We found no public terms for it. If some hosts may need it, ask for availability and conditions in writing with the renewal quote; our quote checklist covers the rest of the quote.

vSphere 7 as the precedent

vSphere 7 shipped on 2 April 2020 with end of general support first set for 2 April 2025. In July 2024, about eight months before that date, Broadcom extended it by six months to 2 October 2025. Two lessons carry over. The extension came once, and we found no announcement of one for vSphere 8 as of 28 September 2026: plan on October 2027. And versions cannot be skipped: Broadcom’s June 2025 overview of vSphere 9.0 says “Upgrading directly from vSphere 7.0 is not supported” and that vCenter 9.0 “does not support managing ESX 7.0 or earlier”, so an estate still on 7.x has two upgrades ahead.

Where 8.x goes next

Broadcom’s product-line comparison of April 2026 settles the question for the standalone editions: “vSphere Standard and vSphere Enterprise Plus are only available as versions up to the 8 Update 3 release”, and vSphere 9.1 features are “only available as part of VMware vSphere Foundation 9.1 and VMware Cloud Foundation 9.1”. In September 2026 Broadcom told reporters that an updated vSphere Standard is coming; until it ships, Standard and Enterprise Plus have no documented 9.x version.

Perpetual licences need a step first: the VCF 9.1 FAQ of 3 September 2026 says customers with perpetual licences “will need to switch to subscription licenses prior to upgrading”, and the VVF 9.1 FAQ says the same. The tier and the term against this calendar are in our renewal guide, the core count in our core counting guide.

The 9.x line has its own clock. Broadcom’s July 2025 support model expects six years from 9.0, to an estimated end of service on 17 June 2031, with a minor release about every nine months; early minor releases are expected to get 27 months of support, the last one 45. The minor release you land on sets the date of your next upgrade, so check its end date before you pick the target.

Upgrade paths and the order Broadcom sets

For 9.0, Broadcom wrote in June 2025 that “vSphere 9.0 supports direct upgrade from vSphere 8.0”, and the oldest host vCenter 9.0 manages runs ESX 8.0 (Broadcom’s 9.x documents call the hypervisor ESX), but the back-in-time rule below also bars 8.0 U3i and later from 9.0.0.0, 9.0.1.0 and 9.0.2.0. For 9.1, Broadcom’s procedure for a vSphere 8 estate, updated on 24 September 2026, starts from vCenter 8 Update 3 and ESX 8 Update 3 or later, and “VCF Operations and the license server components are required to license all 9.1.x environments”. It upgrades or deploys VCF Operations and the licence server first, then vCenter, then the ESX hosts, then the vSAN on-disk format and File Service; VCF 5.2.x deployments have their own path. Broadcom’s fuller sequence for VCF 9.0, KB 390634, also puts the VADP-based backup product, vSphere Replication and Site Recovery Manager before vCenter, and adds: “Patches can be applied in any order. The upgrade order only matters for major/minor releases.” A vCenter upgrade to 9.0 deploys a new appliance, which needs a temporary IP address until it takes over the old one’s address and host name.

Broadcom does not support a “back-in-time” upgrade from a source that “contains code fixes, security patches, or driver updates that are not yet present in the target release” (KB 450972). vSphere 8.0 U3j and U3k came out after VCF 9.1.0, so they cannot be upgraded or converged to it; the Import workflow, which puts the estate under VCF 9.1 fleet management on its 8.0 U3 builds, still works. Broadcom’s KB 448135 adds that VCF 9.1.1.0, released on 3 September 2026, resolves the block for 8.0 U3j and later. Check your 8.0 build against the target build before you book the window.

What to check on every host and cluster

Each check below, from Broadcom’s knowledge base or release notes, can decide whether a host moves to ESX 9 or waits.

Broadcom KB 318697, 428874, 391170 and 401070; TechDocs: ESX 9.0 hardware requirements (24 August 2026), VCF 9.0 vSphere support notes (14 September 2026), VCF 9.1 support notes (24 September 2026).

Deprecated is not discontinued: a deprecated CPU installs with CPU_SUPPORT_WARNING and runs 9.x, but Broadcom’s policy in KB 428874 is that such systems “will be removed in the next major VCF release”. For Skylake-SP, the KB attaches an install and upgrade procedure with an override, dated 18 September 2026, and ties support to the server models in the Broadcom Compatibility Guide, with hardware support left to the server maker. The device lists are spreadsheets attached to KB 391170, such as ESX_9.0_End_of_Life_Devices.xlsx; check every adapter and controller against them. vVols is the strictest line: Broadcom discontinued all vVol certifications for 9.0, while critical fixes for vVols continue on 8.x until its end of support.

A plan against the calendar

October 2027 is the date to work back from. The order below is ours; every step rests on the Broadcom documents cited above.

Our planning order, built on the Broadcom documents cited in this guide.

What we do

Eurokommerz and our engineering partner Vixen.UNO turn these dates into a plan for your estate. VMware optimisation includes an audit of the estate, its licences, versions and subscriptions, matches licences to real workloads within Broadcom’s current licensing logic, and produces an action plan ahead of renewal and end of support, with dates. The modernisation of vSphere, vSAN, NSX and VCF then runs in agreed maintenance windows with a rollback plan at every stage, followed by support under an agreed SLA. VMware and Broadcom licences are supplied together with Vixen.UNO under one European contract with Eurokommerz. The first step is a free call; the technical assessment is paid, with its price fixed before work begins, and our infrastructure audit is available as a separate fixed-price product.

FAQ