VMware's move from per-processor to per-core licensing, enacted under Broadcom's ownership, represents the most consequential change to virtualisation economics since VMware first introduced per-socket pricing two decades ago. Every physical core in a host now requires its own licence unit, a 16-core-per-CPU minimum floor applies regardless of the actual silicon, and a punitive 20% late-renewal fee awaits anyone who misses an anniversary date. The result: Renewal quotes that range from uncomfortable to existential for IT budgets, with documented increases of 5x to 40x depending on hardware density and prior contractual terms.
Executive Summary
From Processors to Cores: A Licensing Sea Change
For the better part of two decades, VMware licensing was elegantly simple: one licence per CPU socket. A dual-socket server needed two licences. A four-socket host needed four. The number of cores inside each socket was irrelevant. This simplicity made capacity planning, budgeting, and compliance verification straightforward.
Broadcom's acquisition in late 2023 dismantled that model. Starting in early 2024, every new VMware subscription is metered on a per-core basis. The shift aligns VMware with a broader industry trend (Microsoft SQL Server and Oracle Database have used per-core metrics for years) but introduces a fundamentally different cost dynamic for virtualisation infrastructure.
The commercial logic is transparent. Modern server processors have evolved dramatically: AMD EPYC 9004 chips ship with up to 128 cores per socket, and Intel Xeon 6 "Sierra Forest" reaches 144 cores. Broadcom has publicly targeted growing VMware revenue from $4.7 billion to $8.5 billion within three years of the acquisition, and per-core metering is the primary mechanism to achieve that.
What Exactly Counts as a Core?
A core is a physical processor core. Hyperthreading does not double your count. Two hardware threads on one physical core still represent one licensable core. This is consistent with how Microsoft and Oracle treat hyperthreading. In virtualised environments, the licence count ties back to the physical cores powering the hypervisor layer, not the virtual CPUs assigned to guest VMs. In public cloud environments, cloud providers often label units as "vCPUs" which typically correspond to one hyperthread, meaning 2 cloud vCPUs = 1 physical core for licensing purposes. Misinterpreting this ratio is one of the most common sources of over-purchasing.
A European logistics firm assumed their Azure VMware instances' "8 vCPU" allocation meant 8 core licences per instance, across 40 instances (320 cores total). An internal review confirmed that Azure VMware's vCPUs use hyperthreading. Correct count was 160 cores, 50% fewer than initially quoted. The firm avoided approximately $240,000 in unnecessary annual subscription costs.
The 16-Core Minimum: How the Per-CPU Floor Inflates Costs
Broadcom's per-core model imposes a minimum of 16 cores per CPU socket, regardless of the actual silicon installed. If your server contains a processor with only 4, 8, or 12 physical cores, VMware licensing treats it as if it has 16. You pay for cores that do not physically exist. The rule is applied per CPU, not per server.
| Configuration | Physical Cores | Licensable Cores | Phantom Tax |
|---|---|---|---|
| 1 socket x 4 cores | 4 | 16 | 300% |
| 1 socket x 8 cores | 8 | 16 | 100% |
| 2 sockets x 8 cores | 16 | 32 | 100% |
| 2 sockets x 16 cores | 32 | 32 | 0% |
In March 2025, Broadcom communicated an even more aggressive policy: a 72-core minimum per server for all new subscriptions. The backlash was swift and Broadcom rescinded the 72-core rule. The 16-core-per-CPU minimum remains the operative rule.
How Costs Multiply: The 5x to 40x Sticker Shock
Four compounding factors explain the extreme increases: core-count explosion (a 50-host cluster with dual 64-core EPYCs moves from 100 socket licences to 6,400 core licences), mandatory bundling (VCF and VVF force customers to pay for components they may never deploy), perpetual-to-subscription conversion (the subscription that replaces perpetual often costs as much as the original perpetual licence annually, representing 3x to 5x increase over 5 years), and list-price inflation (legacy discounts of 40 to 60% off list are now 10 to 20% off or list outright).
| Scenario | Legacy Annual Spend | New Annual Spend | Multiplier |
|---|---|---|---|
| Mid-size enterprise, 64 cores | $20,000 | $100,000 | 5x |
| Public-sector, 200 cores | $100,000 | $500,000 | 5x |
| University, 500 cores, no academic discount | $40,000 | $500,000 | 12.5x |
| Large enterprise, 2,000+ cores, full VCF | $400,000 | $2,000,000 | 5x |
A UK university running VMware on approximately 500 cores paid GBP 40,000/year under an academic perpetual licence. Upon renewal, Broadcom quoted GBP 500,000/year at full commercial rates. Collective escalation with peer universities plus an RFP for alternatives resulted in a 40% reduction to approximately GBP 300,000/year. The university is migrating non-critical workloads to Proxmox.
The 20% Late-Renewal Penalty
If your VMware subscription expires before you complete the renewal, Broadcom imposes a one-time 20% surcharge on the first year's subscription cost. For context, Microsoft's comparable late-renewal penalty is approximately 3%. Broadcom's is nearly seven times steeper. On a $500,000/year subscription, that means a $100,000 penalty. On a $2 million contract, it is $400,000.
A US manufacturing firm with a $900,000/year VMware subscription was awaiting final CFO sign-off when the renewal deadline passed by 11 days. Broadcom added a $180,000 line item (20% of first-year subscription). The position was firm and contractual. The firm now begins all VMware renewal discussions 6 months before expiry.
Multi-Year Lock-Ins: Evaluating 3 to 5 Year Commitments
Three options: 5-year commitment (best per-core discount but maximum lock-in — suitable only for organisations with high confidence VMware remains their core platform through 2030+), 3-year commitment (the "sweet spot" — secures meaningful discount while limiting strategic exposure), 1-year subscription (maximum flexibility but highest per-core cost).
A multinational with 4,200 licensable cores faced a 1-year renewal quote of $3.2M (4x increase). The 5-year offer was $2.1M/year but required Cloud Foundation including NSX (unused). The CIO negotiated a 3-year vSphere Foundation deal at $2.4M/year with a clause allowing 15% core-count reduction at Year 2. 3-year total: $7.2M vs. projected $9.6M on 1-year path. The scale-down clause was the critical win.
The Most Dangerous Licensing Pitfalls
Key pitfalls: treating vCPUs as cores (causes 50-100% over-purchase), sub-16-core hardware penalty (100-300% per-host inflation — retire/consolidate sub-16-core servers), late renewal (20% first-year surcharge — implement T-180 alerts), multi-year over-commitment (15-30% wasted spend — use conservative forecasting with scale-down clauses), bundle composition changes (contractual product-list exhibit and annual review essential).
10-Step Strategic Action Plan
1. Baseline your environment exhaustively — Full inventory of every VMware host: CPU model, socket count, cores per socket, hyperthreading status.
2. Calculate your true licensable core count — Apply the 16-core-per-CPU minimum to each host. Sum across the entire estate.
3. Right-size hardware for licence efficiency — Consolidate VMs from multiple low-core hosts onto fewer high-core modern servers. Retire sub-16-core hardware aggressively.
4. Evaluate edge and ROBO alternatives — For small remote-office or edge sites running 1 to 3 VMware hosts, assess whether VMware is still cost-effective. Alternatives like Proxmox, Hyper-V, or KVM may deliver equivalent functionality at a fraction of the cost.
5. Lock renewal dates into organisational workflow — Implement automated alerts at T-180 and T-90 days.
6. Engage Broadcom early, not reactively — Begin renewal conversations at least 6 months before contract expiry.
7. Negotiate bundles vs. components deliberately — Compare VCF, VVF, and individual subscriptions against your actual usage.
8. Secure multi-year price protections — Insist on capped annual increases, scale-down rights, and explicit product-inclusion exhibits.
9. Maintain a credible Plan B — Pilot an alternative hypervisor in a non-critical environment. Issue an RFP for virtualisation alternatives.
10. Engage independent advisory support — Redress Compliance specialises in Broadcom advisory services.
Audit Preparedness: Staying Compliant
Broadcom has signalled compliance enforcement will be vigorous. Maintain an evergreen register of your licensable core count, updated at least quarterly. Avoid common audit triggers: deploying additional ESXi hosts without corresponding licence additions, and repurposing a licence from a decommissioned host without formally updating entitlements.
Looking Ahead: What CIOs Should Expect
Price increases will continue — analysts expect annual list-price increases of 5 to 15% on top of already-elevated per-core rates. Bundle compositions may shift. Audit frequency will likely increase. The alternative ecosystem is maturing — Proxmox, Nutanix AHV, and Microsoft Hyper-V are all benefiting from VMware customer dissatisfaction.