vSphere 9 end of support and EOL: what Broadcom publishes for 9.0, 9.1, VCF 9 and VCF 5.2

vSphere 9 end of support and EOL: what Broadcom publishes today

As of 10 October 2026, we found no public Broadcom page that gives a day for the end of general support of vSphere 9.0, vSphere 9.1 or VCF 9.x as a whole. Broadcom’s product lifecycle page in its support portal requires a sign-in; read without one on 10 October 2026, it showed menus and an access notice, no table, so we could not see whether it already gives a day for 9.0 or 9.1. What Broadcom publishes openly about vSphere 9 and ESXi 9.1 end of life is the support model of the 9.x line, the release date of each version and a list of end of technical guidance dates, and these are enough to set out the planning frame for an estate.

Broadcom’s VCF blog of 16 July 2025 describes the model. The 9.x line is expected to get six years of support from the major release, which Broadcom put as “an estimated End of Service date of 17-June 2031”, and customers can buy up to one more year of Extended Support in certain cases. Within the line, Broadcom wrote that its “expectation is that initial minor releases will provide 27 months support each”, while the last minor release gets 45 months. The post does not say from which day the 27 months run, so we do not turn them into dates.

Broadcom KB 314608 (release dates), VCF 9.1 release notes (last updated 8 October 2026), VVF 9.1 FAQ, VCF blog posts of 16 July 2025 and 1 August 2025, Broadcom’s end of technical guidance list (undated); all read on 10 October 2026.

Broadcom’s 9.x support model: 27 and 45 months

Before 9.0, Broadcom followed what it calls a 5+2 model: five years of general support and, in certain cases, two more years of Extended Support to buy. For 9.x it moved to 6+1, with a major release every three years and “minor releases approximately every nine months”. That gives four minor releases per major release, and Broadcom’s own example is “VCF 9.0, 9.1, 9.2, 9.3”. On that example, 9.0 and 9.1 are initial minor releases with 27 months each, and the last one, 9.3 in Broadcom’s numbering, is the release with 45 months.

Updates inside a minor release are a separate matter. Broadcom’s KB 314608 lists 9.0.1.0 on 29 September 2025 and 9.0.2.0 on 20 January 2026 after 9.0, and 9.1.1 on 3 September 2026 after 9.1.0. The support model attaches its periods to the minor releases 9.0 to 9.3 and says nothing about these updates. We read them as part of their minor release; the lifecycle page is where to confirm it for your build.

Some components have support periods of their own. The VCF 9.1 FAQ of 3 September 2026 lists “a period of 24 months of support for vSphere Kubernetes releases (VKr)” among the benefits of the Kubernetes service, so an estate that uses it tracks two calendars.

VCF 5.2 end of life and vSAN 8 end of support

VCF 5.2 runs on vSphere 8. Broadcom’s KB 314608 lists vCenter and ESXi 8.0 Update 3 builds and NSX 4.2 in every 5.2 release, from 5.2.0.0 on 23 July 2024 to 5.2.4 on 27 May 2026, which ships vCenter and ESXi 8.0 U3j. We found no public Broadcom page with an end of general support date for VCF 5.2 itself. Its vSphere layer ends with vSphere 8, which Broadcom’s VCF blog of 1 August 2025 says “will be supported until October 2027”; the day and what stops are in our guide to the vSphere 8 end of general support.

Broadcom’s end of technical guidance list, a PDF without a date, gives 11 October 2029 for ESXi 8.0, vCenter Server 8.0 and vSAN 8.0, and 1 June 2028 for VCF 5.0 and VCF 5.1. VCF 5.2 is not on the list. For vSAN 8 general support, the only day on a public Broadcom page we read is in KB 392942, a table for Broadcom’s Telco Cloud Infrastructure 3.0 stack, which lists vSAN 8.0 U1 with end of general support on 11 October 2027 and end of technical guidance on 11 October 2029. Our vSphere 8 guide explains why we treat that table as a pointer, not proof.

One management component of the 8.x generation has a public day. KB 422643 states: “The End of General Support for VMware Aria Operations 8.18 is on October 11th, 2027.” It recommends an upgrade to VCF Operations 9.0. For vVols, the VCF 9.1 FAQ says that critical bug fixes continue for VCF 5.x “until end-of-support of those releases”, so on VCF 5.2 they end with its end of support, a date we found on no public Broadcom page.

What ends at end of general support

Broadcom’s maintenance handbook (Maint-HB-RM111, 8 June 2026) defines end of service as “the discontinuation of a version of a Broadcom Offering” and end of life as the discontinuation of the offering itself. After the published date, Broadcom “has no obligation to provide Support” for that version. Fixes already published stay available as self-service support for the rest of your maintenance term. To be eligible for support, the handbook requires customers to be “using a currently supported version”, so, on our reading, an active VVF or VCF subscription does not keep a minor release under support past its date.

The handbook also sets the warning period. Broadcom “will make reasonable efforts to provide you with a minimum of a twelve (12) month notice” before an end of service or end of life date. For an estate that upgrades cluster by cluster, treat that notice as the latest point to put the next upgrade into the maintenance calendar. Extended Support, Essential Support and what each covers are in our guide to VMware support after Broadcom.

Where the dates are published, and how to read them

For the days of 9.0 and 9.1, the place to check is Broadcom’s product lifecycle page, which needs a Broadcom support account. Read it signed in, record the date for each minor release you run together with the day you read it, and keep that record with the renewal file. The public sources around it are the VCF blog for the model, KB 314608 and the release notes for release dates, the undated end of technical guidance list for the phase after general support, and product KBs such as KB 422643 for single components.

The release dates differ by product. Broadcom’s VVF 9.1 FAQ says that vSphere Foundation 9.1 “is generally available as of May 05, 2026”, while the VCF 9.1 release notes and KB 314608 give 12 May 2026 for VCF 9.1.0. If an end date were counted from release, those seven days would matter, which is one more reason to read the date in the portal rather than add 27 months yourself. Third-party lifecycle trackers already show day dates for 9.0 and 9.1; we could not match them to a public Broadcom page, so we do not use them here.

The minor release you land on sets the next upgrade

In an estate of 10 to 60 hosts, every minor upgrade touches each vCenter instance, every host and, where present, vSAN and NSX, so each one takes several maintenance windows. The release you choose for the move off vSphere 8 decides when the next round of windows is due. The table applies Broadcom’s model to each landing point without inventing dates.

Calendar logic on Broadcom’s VCF blog of 16 July 2025 and 1 August 2025 and KB 314608; the days for 9.0 and 9.1 come only from the product lifecycle page.

Take an estate of 40 hosts in four clusters at two sites, on vSphere 8.0 U3 today. Landing on 9.1 means one upgrade from 8.0 U3 to 9.1 before October 2027 (from 8.0 U3j or later, to 9.1.1 or later, as KB 448135 explains) and at least one more upgrade before 9.1 leaves general support. Whether that second step can go straight to the last minor release of the line depends on the upgrade paths Broadcom publishes for that release when it ships. CPUs that Broadcom has deprecated for 9.x stay supported on 9.x but are due to be removed in the next major release, which puts the replacement of those hosts into the same calendar; our ESX 9 hardware requirements guide lists them.

The subscription term should cover the same calendar. The VVF 9.1 FAQ says customers with perpetual licences must move to subscription before they can upgrade to vSphere Foundation 9.1, and our renewal guide for Standard, VVF and VCF shows which tier carries 9.x.

Our VMware optimisation service includes an audit of your versions, licences and subscriptions and produces an action plan ahead of renewal and end of support, with dates. Send us the minor release each cluster runs and the date your subscription ends.

How to plan upgrades against the dates

The order below is ours; each step rests on the Broadcom documents cited above.

1. List every vCenter instance, host, vSAN cluster and NSX Manager with its build, and map each build to its minor release with KB 314608 and the release notes.
2. Sign in to Broadcom’s product lifecycle page, read the end of general support for each minor release you run and record the date with the day you read it.
3. Choose the target minor release by its end date, by the upgrade paths Broadcom documents from your build, and by the hardware and licence checks for 9.x.
4. Put the upgrade of each cluster into maintenance windows well before that date, with a restore point and a rollback plan for vCenter and the hosts.
5. Check the lifecycle page again whenever Broadcom ships a minor release or gives notice of an end of service date.

Broadcom’s KB 448135 describes a block on upgrades to 9.1.0.x from vCenter and ESXi 8.0 U3j and later and says VCF 9.1.1.0 resolves it; KB 314608 dates 9.1.1 to 3 September 2026. The full order for a vSphere 8 estate, from licence components to hosts and vSAN, is in our step-by-step guide to upgrading vSphere 8 to VCF 9.

Upgrades between releases run with our engineering partner Vixen.UNO in agreed maintenance windows, with a rollback plan at every stage. Describe your clusters and maintenance windows in the form below.

What we do

Eurokommerz and our engineering partner Vixen.UNO turn these dates into an upgrade plan for your estate. Our VMware optimisation service includes an audit of the estate, its licences, versions and subscriptions, 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. Licences and engineering come on one EU contract and invoice with Eurokommerz. The first call is free of charge; the price of the technical assessment is fixed before work begins.

FAQ