Oracle virtualization risk. Mapped, scored, and capped.

Oracle virtualization risk is the single largest line on most Oracle audits we have advised. The risk does not come from license shortage. It comes from a policy interpretation that Oracle applies but the customer contract does not require.

This assessment decomposes the risk by hypervisor, scores your estate against a five level model, and shows the levers that cap the audit cost. The benchmarks come from 240 Oracle virtualization audit engagements over the last five years.

The partitioning policy in plain terms

Oracle distinguishes between hard partitioning and soft partitioning. Hard partitioning binds Oracle to a physical subset of a server. Soft partitioning, in Oracle policy, does not. The customer must license every physical core on every host that could ever run Oracle.

What Oracle treats as hard partitioning

• Physical partitions. Solaris Dynamic Domains, IBM LPARs, and dedicated hardware partitions.
• Oracle VM Server for x86. When configured with CPU pinning and the approved configuration files.
• Oracle Linux KVM. When deployed under the Oracle Linux Virtualization Manager with pinning.
• Solaris Zones. Capped containers with resource pools.
• Trusted partitioning on engineered systems. Exadata and Oracle Database Appliance configurations.

What Oracle treats as soft partitioning

• VMware vSphere. Across every version, including with DRS rules and vSphere Affinity.
• Microsoft Hyper V. Including dynamic memory and processor compatibility settings.
• Nutanix AHV. Despite host pinning and node affinity rules.
• Red Hat KVM and OpenShift Virtualization. Without Oracle Linux Virtualization Manager.
• Citrix Hypervisor. All versions and all configurations.

Hypervisor by hypervisor: risk view

VMware vSphere

The largest single audit risk line on most enterprises. Oracle LMS asks for full vCenter inventory. The default interpretation expands Oracle license requirements across every host the Oracle virtual machine could run on through vMotion.

vSphere version	Oracle position	Buyer side counter
vSphere 5.0 and 5.1	License all hosts in the data center	Cluster level scope was contract default
vSphere 5.5 to 6.5	License all hosts where VM could run	DRS host affinity rules bound the scope
vSphere 6.7 to 7.0	License all hosts across all vCenter linked mode	Audit logs prove no cross cluster movement
vSphere 8.0	License all hosts across linked vCenters globally	Same as 6.7 to 7.0, plus host hash binding

Microsoft Hyper V

Hyper V audit exposure is lower because Microsoft does not aggregate hosts the way vCenter does. Oracle LMS still applies the soft partitioning policy and the buyer side counter is the same.

Nutanix AHV

Nutanix host affinity and node pinning are documented features. Oracle does not recognize them in policy. The buyer side counter relies on Nutanix configuration evidence to prove that the Oracle workload never executed outside the bound nodes.

Red Hat KVM and OpenShift Virtualization

Open source KVM is exposed unless deployed under Oracle Linux Virtualization Manager. OpenShift Virtualization carries the same risk as VMware on a per node basis.

Oracle Cloud Infrastructure

OCI carries the lowest virtualization risk. Oracle treats OCI compute as a known partitioning model and offers BYOL math that bounds the license cost. Workload migration to OCI is a defense lever, not just a procurement choice.

The risk scoring model

Score your Oracle virtualization estate against five levels. The score informs the defense, the contract clauses, and the migration roadmap.

The five risk levels

Level	Profile	Median exposure	Defense difficulty
L1	Oracle on dedicated physical hosts	$0	Low, evidence already exists
L2	Oracle on isolated VMware cluster, never moves	$200,000 to $800,000	Moderate, requires DRS evidence
L3	Oracle on shared cluster with host affinity rules	$1.4M to $4.2M	High, contested every time
L4	Oracle on shared cluster, no affinity, linked vCenter	$3.6M to $12M	Very high, full vMotion replay required
L5	Oracle across multiple vCenters and data centers	$8M to $35M	Extreme, every host across the estate in scope

How to compute your score

1. Count Oracle Database VMs. Include every instance running Enterprise Edition or Standard Edition 2.
2. Map the vCenter or hypervisor manager. Identify every host in scope of vMotion or migration.
3. Pull the DRS or affinity rules. Confirm whether the Oracle workload is bound to a subset of hosts.
4. Check the vCenter linked mode. Linked vCenters expand the audit scope to every connected cluster.
5. Assign the level. The highest level reached on any factor defines the overall score.

The evidence pack the buyer side brings

Every successful virtualization defense rests on the evidence pack. Without the pack, Oracle owns the narrative. With the pack, the customer owns it.

Five evidence artifacts

• Cluster topology export. The full host, cluster, and resource pool tree from vCenter as of the audit date.
• DRS and affinity rule export. Configuration that proves the Oracle VM was bound to a specific host subset.
• vMotion log replay. Twelve months of vMotion events showing actual VM movement.
• Order document index. Every Oracle order document that defines the licensing scope.
• Internal architecture decision records. Documentation that supports the design intent of host isolation.

The defense levers that cap the cost

Six levers cap virtualization audit cost. Each lever works on its own. Together they typically reduce the LMS opening number by 70 percent.

The six levers

1. Partitioning policy challenge. Issue a written position that policy is not contractual.
2. Cluster scope evidence. Provide the cluster topology and DRS rules in writing.
3. vMotion log replay. Demonstrate the Oracle VM never executed outside the bound hosts.
4. Order document scope reference. Map every Oracle order document to the named license scope.
5. Settlement decomposition. Demand line item settlement with the partitioning charge separated.
6. Migration roadmap. Offer a credible migration to hard partitioned hardware or OCI as a settlement input.

What to do next

1. Pull the vCenter cluster topology for every Oracle workload across the estate.
2. Export the DRS and affinity rule configuration as of the current date.
3. Capture twelve months of vMotion event logs.
4. Map every Oracle order document to the contractual license scope.
5. Score the estate against the five level model in this assessment.
6. Engage independent buyer side advisory before responding to any Oracle LMS letter.
7. Download the Oracle ULA Decision Framework if Oracle frames the audit as a ULA conversation.

Frequently asked questions