Your VMware renewal came back multiplied: what changed and what your options are

The same servers. The same number of virtual machines. Nothing about the business has changed since last year. Then the renewal quote arrives at twice what you paid, or more.

That is not an error in the quote and not an invention of your reseller. It is the arithmetic of a licensing model that changed completely. Here is the new model, and how to work out your own number before you ask anybody for a price.

What changed: from a licence you own to a term you rent

Broadcom acquired VMware in late 2023 and, in December of that year, announced the end of perpetual licence sales. A perpetual licence is the kind you buy once and keep, paying a support contract afterwards if you want one. What is sold now is a subscription for a fixed term: it ends, and you either renew or lose the right to run it.

The difference is not only the price but the nature of the line item. What used to be a one-off purchase sitting on the balance sheet as an asset is now a recurring annual cost for as long as the platform runs. Businesses that bought perpetual licences before the change did not lose them — but they lost the ability to buy more, and to extend support on them indefinitely.

The sixteen-core rule, which is where the multiplication starts

Licensing is now counted per core, not per processor. Broadcom's Specific Program Documentation for VMware Cloud Foundation states it plainly — "licensed on a per Core license metric with a minimum licensing requirement of 16 Cores per Processor" — a floor of sixteen core licences per processor, and the same floor applies to VMware vSphere Foundation and to the vSphere editions.

This is the crux. Take a server that is very common in mid-sized companies: two processors, eight cores each. Sixteen physical cores in total. Under the new rule you do not pay for sixteen — you pay for thirty-two, because each processor carries the full floor even when only half of it is populated.

That is the multiplication, exactly, and it appears nowhere as a line on the quote. It shows up as a larger total, so it reads like the price went up, when what went up is the number of units you are buying.

A second number that appears in quotes but not in Broadcom's documents

Since April 2025 a minimum of seventy-two cores per order has been widely reported, meaning a smaller order is priced at seventy-two regardless.

We will put that in the form it deserves: the sixteen-core-per-processor floor is written into Broadcom's published documentation. The seventy-two-core figure we did not find there — it appears as a channel and distributor policy, and minimums at the distributor level have changed more than once since 2024.

What that means in practice: do not accept or reject it on the strength of an article. Ask for the quote itself to state how many cores you are buying and why that specific number. If it exceeds the cores in your servers, you are paying for a difference whose origin you are entitled to see.

The product list collapsed into two names

The long catalogue that used to be sold piece by piece has consolidated around two bundles, and new releases now arrive only in them:

• VMware vSphere Foundation — the layer that runs and manages virtual machines, bundled with software-defined storage, the operations tooling and the Kubernetes service.
• VMware Cloud Foundation — the full stack, adding software-defined storage and networking and the automation tooling on top.

That does not mean vSphere Standard and Enterprise Plus have gone: both are still sold by subscription and both still carry current licensing documents, but at releases that stop at 8 Update 3 — the 9.1 capabilities arrive only through the two bundles above.

Here is the practical point: the cheapest thing that runs ordinary virtual machines is vSphere Standard, not vSphere Foundation. If all you run is virtual machines, with no software-defined storage and no containers, ask for the quote to price the smallest edition that covers what you actually run and set it against the bundle before you sign. The gap between them is large, and it is paid for capabilities you may never switch on.

Count your cores before you ask for a quote

Open the vSphere client, or run one command against each host, and write a three-column table: host name, processors in it, cores per processor. Then for each host take the number of processors and multiply it by the larger of two numbers — sixteen, or the actual cores in that processor.

The sum of that last column is what you will be paying for. Work it out before the call rather than after it, and you enter the negotiation already knowing the right figure.

Four options, honestly

One: renew and pay. If the platform is stable, your team knows it, and critical systems run on it, stability has a price and paying it is a legitimate decision. Just put the new figure into next year's budget so it is not a surprise twice.

Two: consolidate onto fewer, denser hosts. Because the floor is charged per processor, a two-socket box with eight-core processors is the worst possible shape under this rule. Running the same workload on fewer hosts with larger processors reduces the number of processors paying a floor. That needs careful memory and capacity arithmetic before any purchase, and it can justify a new server that pays for itself out of the licensing difference.

Three: move platform. Hyper-V if your workloads are mostly Windows, Proxmox if they are mostly Linux. The honesty this deserves: migration is not free. It is a project with downtime, it needs every system tested after it moves, it needs the backup estate rebuilt on tooling that supports the new platform, and it needs a team learning different tools. Cost that once and set it against the renewal difference over three years, not one.

Four: move part of it to cloud. This suits particular workloads rather than everything, and it usually meets latency and egress costs — and, in Egypt, the question that comes before both: where the data resides.

Before any decision: three questions

What is each host actually running? Plenty of estates carry virtual machines nobody uses and nobody switched off. Powering those down before you count can change the whole decision.

When does your current term end? A decision taken three months out has options. One taken a week out has one.

How old is the hardware itself? A server near the end of its vendor support turns the two questions into one — which is what the server selection guide works through.

ZEMAVO Technology supplies the servers and builds the virtual estates that run on them, and we can count the cores with you and put all four options against your own figures. Read about VMware and server supply, or send us your core table.