Virtualization lets you run many workloads on fewer servers and move them freely between hosts. Licensing does not always follow. Some publishers license the physical hardware a workload could run on, not just the virtual machine it runs in today. And virtualization platforms themselves are licensed per core, with minimums that can make small hosts surprisingly expensive.
Two layers of licensing
Virtualized server estates carry two separate licensing questions, and both can surprise you:
The hypervisor and management software, licensed per physical core with minimums. See VMware after Broadcom.
Operating systems, databases and middleware running in the VMs, each with its own rules about virtual environments.
Why virtualization multiplies the count
When a publisher counts the physical cores of every host a workload could run on, a single small virtual machine in a large cluster can require licensing the entire cluster. Database and middleware publishers are where this matters most. See Oracle license audits and IBM sub-capacity licensing.
VMware licensing after Broadcom
VMware's products are now sold as subscriptions licensed per physical core. Every CPU must be licensed for at least 16 cores, even if it has fewer, and from April 10, 2025, each order must cover at least 72 cores.
See VMware licensing after Broadcom for more detail.
How to control virtualization licensing
- Know each publisher's rules
For virtual environments, before deploying anything licensed by core or processor.
- Isolate licensed workloads
On dedicated hosts or clusters where rules require host-level licensing, and document the isolation.
- Right-size hosts
To the core counts that licensing minimums make efficient.
- Track VM mobility
Automatic migration and disaster-recovery failover can extend licensing scope.
- Review before expanding
Adding a host to a cluster can add licensing requirements for every workload in it.
Before adding a host or cluster
How MI One helps
Frequently asked questions
Do all publishers license the whole host?
No. Rules differ widely. Some license per virtual machine; others per physical host or cluster.
Can moving to the cloud remove these issues?
It changes them. Cloud deployments have their own licensing rules, especially for bring-your-own-license scenarios.
Who should approve cluster changes from a licensing view?
The SAM function should be a reviewer in the infrastructure change process for any cluster running core-licensed software.
Sources
- Techzine, "Broadcom raises minimum requirement for VMware licenses: from 16 to 72 cores," April 2025. https://techzine.eu/news/infrastructure/130027/broadcom-raises-minimum-requirement-for-vmware-licenses-from-16-to-72-cores
- heise online, "VMware: Companies will have to license 72 instead of 16 cores in future," April 2025. https://heise.de/-10335733