The renewal quote lands, someone in finance adds up the cores in the server inventory, and the two numbers don't match. The quote is higher. Usually by a lot.

The first instinct is that Broadcom or the reseller made a mistake. Almost always, they didn't. The gap comes from one rule that's easy to miss and hard to argue with.

The 16-Core Floor, Per CPU

VMware Cloud Foundation and vSphere Foundation are licensed per physical core, and Broadcom's core-counting article is explicit about the floor: you license a minimum of 16 cores for each physical CPU in every ESXi host you intend to license (KB 313548). The floor applies per processor, not per host and not per order.

So a CPU with 24 cores is billed as 24. A CPU with 12 cores is billed as 16. A CPU with 8 cores is still billed as 16.

Host configurationPhysical coresLicensed coresPaid for, not present
2 CPUs × 8 cores163216 (licensed is double)
2 CPUs × 12 cores24328
2 CPUs × 16 cores32320
1 CPU × 32 cores32320
2 CPUs × 10 cores203212

The last row is the one that hurts quietly. A 10-core part was a sensible buy a few years ago for a dev/test or DR cluster that didn't need much compute. Under per-core licensing, each of those hosts pays for 12 cores that don't exist, every year, for as long as the hosts stay in service.

Where the Extra Cores Hide

In a typical estate, the gap rarely sits in the production cluster. Production tends to run newer, denser CPUs that clear the floor on their own. The phantom cores pile up around the edges.

  • DR clusters built from the previous hardware generation, often lower core counts, often mostly idle.
  • Dev/test on whatever was left over after the last refresh.
  • Branch and edge hosts, where a small CPU made sense because the workload was small.
  • Management or infrastructure clusters sized for vCenter and a handful of appliances, then licensed at the same per-CPU floor as everything else. In VCF, the management domain hosts count toward the license, and a high-availability management domain needs at least four of them.

Add those up across a mid-size estate and the share gets large fast. In the fictional sample assessment on this site it's 208 of 768 licensed cores, 27%. That fictional estate runs 10- and 12-core CPUs everywhere, production included, so every cluster adds to the gap, and the two four-host management domains add 64 cores on their own. Your number will differ. It's still the number worth knowing before the renewal call, because it's the part of the bill that buys zero capacity.

The cheapest core to license is the one you stop paying for because it never existed.

What the Floor Does to vSAN

There's one consolation. vSAN capacity comes bundled per licensed core: 1 TiB of raw vSAN entitlement per VCF core, and 0.25 TiB per vSphere Foundation core, rounded up (KB 313548). Phantom cores still carry their vSAN entitlement. If you run vSAN and you're buying add-on capacity, the floor gives a little back.

It's rarely enough to offset the cores. Still worth counting, because it changes the math when you compare consolidation options.

Check the Quote for an Order Minimum Too

Separate from the per-CPU floor, distributors announced a 72-core minimum per order in March 2025, and trade press reported it withdrawn about two weeks later (heise, Licenseware). Broadcom's core-counting article lists only the per-CPU minimum. If your quote shows a total that looks rounded up to 72, ask your reseller which rule produced it and get the answer in writing.

What to Do With the Number

Count it first. Hosts, CPUs per host, cores per CPU, for every host you intend to license. The licensed core calculator does the arithmetic for one configuration at a time, and an RVTools export gets you the inputs for all of them.

Then decide whether the gap is worth closing. Sometimes it isn't: a DR cluster with two years of hardware support left may cost less to keep than to replace. Sometimes it's the single biggest line in the renewal you can actually change, usually by consolidating onto fewer hosts with higher-core CPUs before the anniversary date. That decision needs a memory check as well as a core count, because cores aren't the only thing that has to fit on fewer hosts.

Before the Renewal Call

How many licensed cores does the quote use, and how many physical cores do your hosts have?

Which clusters run CPUs with fewer than 16 cores?

When does hardware support end on those hosts?

Does the quote apply any minimum beyond the per-CPU floor?

Reported per-core prices vary widely and rarely match a real quote, so the dollar value of the gap depends on your own quote. Commercial terms come from your Broadcom account team or reseller. What you can control is walking into that conversation knowing exactly which cores you're paying for and why.