Oracle licensing on VMware in 2026: soft partitioning, Broadcom & audit exposure

Running Oracle on VMware is one of the largest sources of licensing exposure in enterprise IT — not because of a technical fact, but because of a policy position. Understanding the distinction is the key to not over- or under-reacting to it.

Soft partitioning, in Oracle’s view

Oracle classifies VMware (and most hypervisor-level core limiting) as soft partitioning, which it does not accept as a way to reduce licensing. Its position is that you must license every physical core where an Oracle VM couldrun — which, with vMotion and shared clusters, can extend across an entire cluster or even multiple clusters, far beyond where Oracle is actually installed.

It’s important to be precise: this is Oracle’s contractual policy position, set out in its partitioning policy document, not a settled point of law or a technical necessity. It has been contested. But it is the basis on which Oracle counts, so it drives real exposure.

Why it’s gotten hotter

Post-Broadcom consolidation has many organizations re-architecting their VMware estates, and Oracle reviews increasingly ask for VMware topology specifically. A cluster change made for VMware-cost reasons can move your Oracle exposure at the same time — in ways that aren’t obvious unless you map the two together.

What you can actually measure

• Where Oracle is installed, and on which hosts and clusters.
• Which of those hosts are virtualized, so the soft-partitioning question is visible rather than buried.
• The difference between where Oracle runs and where Oracle’s policy might count it.

RenewalIntel flags where Oracle is installed on virtualized hosts so the exposure is in front of you, not discovered in a review. Whether Oracle’s soft-partitioning policy entitles them to count a whole cluster in your situation is a contract question for you and your advisor — RenewalIntel shows you the deployment facts that conversation should start from.