VMware is now sold as per-core subscriptions, and the two bundles most teams compare are VMware Cloud Foundation (VCF) and VMware vSphere Foundation (VVF). Every physical CPU counts as at least 16 licensed cores, and each bundle includes a fixed amount of vSAN storage per core. This guide explains what is confirmed in Broadcom's own documents, what is only reported by resellers, and how to calculate your own core count before a renewal quote arrives.
Who this is for and what you will have at the end
This is for IT managers, sysadmins and small-business owners who run vSphere and need to understand a renewal or a new quote. You will end with a worked core count for your hosts, a vSAN capacity check, a clear view of what VCF and VVF each include, and a list of questions to put to your reseller in writing.
This article explains licensing mechanics. It does not quote prices. Broadcom's public product pages we opened do not state prices, and quotes vary by reseller, term and region.
What changed: perpetual licenses to subscriptions
Broadcom's VVF FAQ says VVF 9.1 moves to subscription-based license files, and that "Customers with perpetual licenses must transition to subscription-based licensing before they can upgrade to the version 9.1 platform." The same FAQ says version 9.0 will only be available for VMware Cloud Foundation and VMware vSphere Foundation.
In practice that means:
- Upgrading to the 9.1 platform needs a subscription license.
- Ask each quote for its term, because renewal dates become a planning item for the infrastructure team and for finance.
- The unit you buy is a core, not a CPU socket as in older VMware licensing.
What VCF and VVF include
Both bundles come from Broadcom's current product pages. The lists below show what each page names and may change with new releases.
| Item | VCF (per the VCF 9.1 FAQ on vmware.com) | VVF (per the VVF FAQ on vmware.com) |
|---|---|---|
| vSphere | Yes | Yes (vSphere Enterprise Plus and vCenter Standard) |
| vSAN | Yes | Yes |
| NSX | Yes | Not listed in the FAQ components |
| vSphere Kubernetes Service | Yes | Yes |
| VCF Operations | Yes | Yes (formerly Aria Suite Standard) |
| VCF Automation | Yes | Not listed |
| HCX | Yes | Not listed |
| VCF Private AI Services | Yes | Not listed |
The VCF page also lists advanced services that are sold separately and are not part of the core VCF offering: Advanced Cyber Compliance, Advanced Security, Load Balancing, Application Services, Data Services, Network Observability, Business Operations, Identity Security and vSAN add-on capacity.
A simple way to decide between them: if you only need virtualization, central management, vSAN and Kubernetes, VVF's list covers that. If you need software-defined networking with NSX, private-cloud automation or HCX for migrations, those appear only in the VCF list. Check the current feature comparison from Broadcom before choosing, because component lists change between releases.
How cores are counted
Broadcom's knowledge base article "Counting Cores for VMware Cloud Foundation and vSphere Foundation and TiBs for vSAN" sets out the rule. Licensing is based on the total number of physical CPU cores across all ESXi hosts you intend to license. The article states that you must license "a minimum of 16 physical cores for each CPU (physical processor)."
The counting steps
- List every ESXi host you plan to license.
- For each host, list each physical CPU and its core count.
- Raise any CPU below 16 cores to 16.
- Add up all CPUs across all hosts.
Hyper-threading does not change the count, because the rule counts physical cores.
Worked example from Broadcom's article
Broadcom gives a two-host example: Host A has two CPUs with 8 cores each, so each CPU counts as 16 and the host counts as 32. Host B has two CPUs with 24 cores each, which counts as 48. The total is 80 licensed cores.
A second example with three hosts
The inputs below are made up for illustration and use the same rule.
| Host | CPUs x cores per CPU | Counted cores per CPU | Licensed cores |
|---|---|---|---|
| esx01.contoso.com | 2 x 12 | 16 | 32 |
| esx02.contoso.com | 2 x 16 | 16 | 32 |
| esx03.contoso.com | 2 x 32 | 32 | 64 |
| Total | 128 |
Notice that esx01 has 24 physical cores but is licensed for 32. Consolidating onto fewer, higher-core hosts can remove this rounding waste, but it changes your failure domain, so decide it on availability grounds as well as licensing.
vSAN capacity: what is included and what you pay extra for
vSAN is licensed by capacity in TiB, separately from the compute core count. Broadcom's article states that "VCF provides 1 TiB of vSAN entitlement for each VCF core purchased" and "VVF provides 0.25 TiB of vSAN entitlement for each VVF core purchased (rounded up to the next TiB)."
vSAN licensing is based on the total raw physical storage contributed by all ESXi hosts in your vSAN clusters. If raw capacity exceeds the included entitlement, you need vSAN add-on capacity for the difference. If the entitlement is larger than what you use, the excess is aggregated and no add-on is needed. The entitlement can also be spread across clusters in ratios different from the core split.
Worked vSAN example
Using Broadcom's 80-core example and a hypothetical 100 TiB of raw vSAN capacity:
| Bundle | Entitlement (80 cores) | Raw capacity | Add-on needed |
|---|---|---|---|
| VCF | 80 x 1 = 80 TiB | 100 TiB | 20 TiB |
| VVF | 80 x 0.25 = 20 TiB | 100 TiB | 80 TiB |
With the 128-core example above and 100 TiB raw: VCF entitles 128 TiB, so no add-on; VVF entitles 32 TiB, so 68 TiB of add-on. If you do not use vSAN at all, this table is irrelevant and the entitlement simply goes unused.
The 72-core question: what is confirmed and what is not
Reports of a 72-core minimum have caused the most confusion, so here is the timeline as the sources describe it.
- Late March 2025: the Born City blog reported that Broadcom would require at least 72 cores per product line or order, based on a letter passed on by the distributor Arrow and on information from three distributors.
- Afterward, commenters and a German reseller quoting Arrow said the minimum order quantity was unchanged and that 16 cores per CPU continued. On April 11, 2025 the blog wrote that the requirement "has probably been withdrawn."
- Broadcom's core-counting article, which we opened for this guide, states only the 16-core per CPU minimum and no minimum order quantity. The page shows no update date.
- A UK reseller, boxxe, published a post about changes from 1 December 2025 that says a 72-core minimum purchase now applies and that the update applies to the UK only. That is a reseller source, not a Broadcom document, so treat it as a claim to verify.
The practical conclusion: the 16-core per CPU rule is confirmed by Broadcom. A minimum purchase can differ by region, reseller and date, so request the exact minimum in writing as part of the quote. For scale, two dual-socket hosts with 8-core CPUs count 4 CPUs x 16 = 64 cores under the 16-per-CPU rule.
Planning a renewal: a checklist
Gather your facts
- Export the host list from vCenter with CPU model, socket count and cores per socket.
- Note which hosts are in vSAN clusters and the raw capacity contributed by each.
- Record which features you use today: NSX, Kubernetes, HCX, Aria or VCF Operations, so you know whether VVF is enough.
Compute
- Apply the 16-cores-per-CPU rule to every host.
- Compare your raw vSAN TiB to the per-core entitlement for each bundle.
- Compute the bundle comparison as cores times the quoted per-core price, using the price each quote states.
Ask in writing
- What is the minimum purchase quantity for my region and reseller?
- What is the subscription term, and is the quote for a fixed term?
- Which components are in the bundle on the date of the quote?
- How is vSAN add-on capacity priced?
- What happens to hosts I add mid-term?
Know your options
Some teams review alternatives alongside renewal. That is a separate project with its own costs for migration, backup integration and retraining, so compare a full-cost estimate and not only the license line.
Troubleshooting common surprises
A quote shows more cores than your CPUs physically have
This is normally the 16-core floor. Check each CPU: a 12-core CPU is billed as 16. Confirm by recounting with the table method above.
vSAN shows as under-licensed
Compare total raw capacity across all vSAN clusters against the entitlement, not usable capacity. The licensing basis is raw physical storage contributed by all hosts.
You cannot upgrade to 9.1 with an old license
Per the VVF FAQ, perpetual license holders must transition to subscription-based licensing first.
A compute-only cluster has unused vSAN entitlement
The VVF FAQ says capacity is pooled across the environment and that unused capacity from compute-only clusters can apply to vSAN-enabled clusters.
Related reading
If you manage vCenter, see VMware vCenter CVE-2026-123890: Check If You Are Hit and Patch Now for the current security advisory.
What we checked
- Opened Broadcom's knowledge base article on counting cores for VCF and VVF on 2026-11-20. It states the 16-physical-cores-per-CPU minimum, the 80-core example, 1 TiB of vSAN per VCF core and 0.25 TiB per VVF core (rounded up to the next TiB). The page shows no update date.
- Opened the VCF page and the VVF FAQ on vmware.com on 2026-11-20 and copied the component lists into the comparison table. The VVF FAQ states the perpetual-to-subscription requirement for 9.1.
- Recalculated Broadcom's example: (2 x 16) + (2 x 24) = 32 + 48 = 80 cores; our own example: 32 + 32 + 64 = 128 cores.
- Recalculated vSAN entitlements: 80 x 1 = 80 TiB and 80 x 0.25 = 20 TiB; 128 x 0.25 = 32 TiB. Add-ons: 100 - 80 = 20, 100 - 20 = 80, 100 - 32 = 68.
- Cross-checked the 72-core claim against the Born City posts of March 30 and April 11, 2025, and the boxxe reseller post about 1 December 2025. Those are not Broadcom documents; the Broadcom article states no minimum order.
- Broadcom's specific program documentation PDFs could not be read in this run, so no claim in this article relies on them. No prices are quoted because no official price page was found.
- Not tested on a live vSphere environment; the figures follow Broadcom and VMware documentation as of 2026-11-20 and may change.
Last tested: 2026-11-20
References
- Counting Cores for VMware Cloud Foundation and vSphere Foundation and TiBs for vSAN (Broadcom KB)
- VMware Cloud Foundation (vmware.com)
- VMware vSphere Foundation FAQs (vmware.com)
- Born City: VMware by Broadcom, 72 core licensing claim withdrawn (11 April 2025)
- boxxe: VMware by Broadcom product changes, 1 December 2025 (UK reseller)
Comments
Questions and tips are welcome. Comments are checked by the EpiFive team before they appear; please do not share passwords, phone numbers or other private details.