Broadcom replaced per CPU VMware licensing with per core licensing in 2024. The new metric carries a 16 core minimum per CPU. Buyer side framework to do the math on actual estates and plan the per core spend.
Broadcom retired per CPU VMware licensing in 2024 and moved every VMware bundle to per core. The new metric assesses license cost against every active core on every CPU. A 16 core minimum per CPU per subscription applies regardless of actual core count.
This piece reads as a per core math reference. Use it with the new licensing model, the change impact piece, the VMware advisory page, and the audit defense guide.
Per core licensing simplifies the rate card for Broadcom and aligns the metric with the rest of the enterprise software market. Microsoft, Oracle, and Red Hat all run per core metrics on their server stacks.
Every CPU in scope of a VMware subscription carries a 16 core minimum. CPUs with fewer than 16 cores still consume 16 core licenses. This is the single largest pricing nuance in the new model.
| Physical cores per CPU | Cores billed | Effective overage |
|---|---|---|
| 8 | 16 | +8 (100%) |
| 10 | 16 | +6 (60%) |
| 12 | 16 | +4 (33%) |
| 16 | 16 | 0 |
| 24 | 24 | 0 |
| 32 | 32 | 0 |
| 64 | 64 | 0 |
Take an estate of 100 servers with 12 core CPUs. The bill counts 200 CPUs at 16 cores each, or 3,200 cores. Consolidating to 50 servers with 32 core CPUs counts the same 3,200 cores. The capital cost of new servers usually pays back inside 12 to 18 months.
The count is per physical CPU per active host. Hyper threading is not counted. Logical processors are not counted. Powered off hosts are not counted unless the host runs intermittent workloads.
VMware per core licensing applies at the host level. VM core allocation does not affect the bill. The license follows the underlying host hardware, not the virtual machine configuration.
Estates with many low core count CPUs feel the largest impact. Consolidating onto fewer denser CPUs cuts the licensed core count by 30 to 50 percent on many estates.
Right sizing the estate before the renewal locks in 18 to 34 percent savings on most estates. The work runs in three steps: audit the CPU inventory, model the consolidation, plan the refresh.
The eight step checklist below moves a VMware estate from a default per CPU mindset to a per core optimized footprint. Open it 9 to 12 months before the renewal.
Every CPU in scope of a VMware subscription carries a 16 core minimum. A CPU with 8 physical cores still consumes 16 core licenses. A CPU with 24 physical cores consumes 24 core licenses. The minimum applies per CPU per subscription regardless of the actual core count installed in the server.
No. Hyper threads and logical processors do not count. The license metric reads physical cores only. A 16 core CPU with hyper threading enabled shows 32 logical processors to the operating system but consumes 16 core licenses, not 32. The simplification helps capacity planning across modern Intel and AMD CPUs.
The count is host level, not VM level. Every active host in the cluster counts the physical cores on every CPU. VM core allocation is irrelevant. Allocating 4 vCPUs to a VM does not change the licensed core count. The license follows the host hardware.
Yes. N+1 capacity is in scope. Failover hosts that can run production workloads in a failover scenario consume the licensed core count even when idle. Customers running large N+1 reserves should factor the reserve into the renewal envelope and the right sizing plan.
Yes. Consolidating onto fewer higher density CPUs cuts the licensed core count by 30 to 50 percent on many estates. The capital cost of newer servers usually recovers inside 12 to 18 months on the license savings alone. The consolidation should align with the renewal cycle for maximum impact.
Per core licensing usually lifts the budget on high core count CPUs. Estates running 32 to 64 core CPUs pay more per host than under per CPU. Low core count estates face the 16 core minimum overage. Most enterprises see a 60 to 250 percent renewal cost swing.
Redress runs the per core review as part of the VMware renewal engagement. The work pulls the CPU inventory, computes the licensed core count, models the consolidation, and lays out the renewal envelope. The deliverable is the optimized footprint, the multi year cost forecast, and the residual clause map.
Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.
A buyer side framework for the next Broadcom VMware renewal cycle. Per core math, 16 core minimum impact, consolidation playbook, and the residual clause checklist.
Used across five hundred plus enterprise software engagements. Independent. Buyer side. Built for VMware customers running VCF, VVF, vSphere Enterprise Plus, or vSphere Standard estates.
Open the white paper in your browser. Corporate email only.
Open the Paper →We audited 240 ESXi hosts spread across six data centers. The per core minimum overage sat at 38 percent of the new bill. Consolidating onto 64 core CPUs across 90 hosts pulled the licensed core count down by 47 percent and paid back in 14 months.
We have run 500+ engagements across 11 publishers. Every engagement starts with one conversation.
Per core licensing benchmarks, consolidation patterns, 16 core minimum impact across estates, bundle tier renewal benchmarks, Nutanix and alternative platform displacement patterns, and the wider Broadcom commercial leverage signals across every renewal cycle.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
