What Should VMware Customers Ask Before Committing to VCF 9?

Before committing to VCF 9, VMware customers should ask five questions: what each patch will touch, who approves each change, what the estate actually contains, how much time is left before vSphere 8 support ends, and who will deliver the work. Faster patching is a real need, and VCF 9's ability to patch hosts without moving workloads is a real capability. But how often you patch and which platform you run on are separate decisions. Answer those five questions first, and you walk into the renewal with options.

I lead sales and client delivery at ReadyWorks, so I'm in the room when VMware renewals and migration plans get decided. This month, a post about Broadcom's VCF 9 target landed in my LinkedIn inbox, and it captured the pressure many infrastructure teams feel right now. Ram Velaga, president of Broadcom's Infrastructure Software Group, told Computer Weekly that Broadcom expects more than half of VMware's installed base, measured by processor cores, to run VCF 9 by late 2027. His reasoning is that frontier AI models now find software flaws fast enough that customers want to patch every few weeks. Broadcom's lifecycle page puts end of general support for vSphere 8, along with VCF 5.2, at October 11, 2027.

What did Broadcom actually say about patching and cost?

The Computer Weekly piece ties faster patching to AI. In his conversation on Six Five at VMware Explore 2026, Velaga frames the same need around operations:

“Customers can no longer take down time to move workloads in and out of a physical host to deal with applying patches.”

- Ram Velaga, Six Five at VMware Explore 2026

That's a problem every infrastructure team I work with already knows. AI raises how often it comes up, but the need underneath is the same: change the estate without disrupting the business.

On price, Velaga told Computer Weekly that rising costs across IT have changed how customers see Broadcom's increases. He also conceded that the transition happened because the business "was not well run" in its pricing, product delivery, and overhead. On Six Five, he described what is driving enterprise infrastructure decisions:< >

“Cost almost is a secondary observation to I've got to own this.”

- Ram Velaga, Six Five at VMware Explore 2026

That matches what I hear from clients. The teams I talk to want control first. In a renewal, control means negotiating from a clear picture of your estate, with a real alternative priced, on a timeline you set.

Which questions should you answer before you sign? 

These are the questions I'd want answered before any VCF 9 commitment, whether you renew, move, or do some of each.

1. What will each patch touch? Patching without moving workloads solves the maintenance window. The applications on a patched host can still be affected, so you need the dependencies, owners, compatibility, and lifecycle stage on every workload. That is application context, and it is what makes a fast patch cadence safe.
2. Who approves each change, and where is it recorded? Patching every few weeks means approving far more changes. As AI becomes part of finding and fixing flaws, those approvals need guardrails: role-based access on every call, a write policy the organization sets, human approval before every write, and a tamper-evident audit trail. Our CEO covered how that works in What Is a Governed AI Control Plane for IT Ops?
3. What does the estate actually contain? Most renewal conversations I see are priced against an inventory nobody fully trusts. Connecting vCenter, Nutanix, your CMDB, and other systems of record, normalised and continuously cleansed, gives you a number you can negotiate from.
4. How much time is really left? October 11, 2027 sounds far away until you count waves, change windows, and freeze periods. Working back from the date tells you when the platform decision has to be made.
5. Who will deliver the work? Whether you upgrade in place or move, a named delivery team should own execution, with your sign-off at every phase. Many enterprises run these programs with the partners they trust.

Who can help once you decide?

You don't have to work through this decision alone. ReadyWorks is a Nutanix technology alliance partner, listed in Nutanix's partner directory with Nutanix Ready validation for AHV, and VirtualReady tracks migration status through Nutanix Move. We also work with Microsoft [relationship to confirm: marketplace listing, partner program, co-sell, or integration]. If the decision is to move some or all of the estate, the work follows a clear split. On VirtualReady, ReadyAI analyses the estate, recommends, and plans the waves. A named delivery team, whether a services partner, ReadyWorks when engaged to deliver, or your own engineers, executes. AI-planned. Expert-delivered.

That model has carried data center programs for customers such as Michigan State University and RBC. Our guide to building an auditable VMware migration runbook walks through each phase, and Would Your VMware Migration Cutover Survive an Audit? covers the evidence your auditors will ask for afterward.

Walk Into the Renewal With Options

The October 2027 deadline will arrive whether your team is ready or not. What you control is how prepared you are when the renewal conversation starts. The clients who come out of these conversations in the strongest position are the ones who already know what they run, what depends on what, and what each option would take to deliver.

If you'd like help working through these five questions, start with a 15 to 30 minute call with our team. We'll talk through where your estate stands today and what each option would take, and the decision stays yours. Talk to a migration specialist who has done this.

Not ready for that step yet? Map your journey in eight questions and choose the VMware program to see your first steps, your first governed actions, and who does the work.  

Frequently Asked Questions

What should VMware customers ask before committing to VCF 9?

Ask what each patch will touch, who approves each change and where it is recorded, what the estate actually contains, how much time remains before vSphere 8 support ends, and who will deliver the work.

When does vSphere 8 support end?

Broadcom lists end of general support for vSphere 8, including ESXi 8 and vCenter 8, as October 11, 2027. VCF 5.2 reaches end of service on the same date.

Can you prepare for a VMware decision before choosing a platform?

Yes. Connecting and cleaning your systems of record and adding application context to every workload helps whether you upgrade to VCF 9, move, or do both.

Who executes a VMware migration planned with ReadyWorks?

A named delivery team: a services partner, ReadyWorks when engaged to deliver, or your own engineers. ReadyAI analyses, recommends, and plans, and you sign off at every phase.