Oracle Virtualization Licensing

Oracle Database licensing on a virtualized estate is the single largest audit exposure across the Oracle customer base. The cost of weak evidence runs into eight figures on production deployments.

The rules differ across hypervisors. The defense rests on documented evidence rather than on contractual argument. The buyer side approach builds the evidence ahead of every audit conversation.

The Oracle partitioning positions by hypervisor.

Oracle publishes a partner approved hypervisor list. The list defines which hypervisors qualify as hard partitioning, which qualify under documented conditions, and which sit in the soft partitioning default.

The hypervisor matrix

The default reading at audit

The audit reviewer defaults to soft partitioning unless the customer produces the evidence. Strong evidence on the documented hypervisors moves the conversation to the documented footprint. Weak evidence pushes the conversation to the full cluster math.

VMware vSphere: the largest exposure.

VMware vSphere is not recognized as hard partitioning. Oracle reads the full physical host as the licensed footprint for any Oracle VM running on the host. The rule extends to every host in the cluster where the VM could run.

The cross cluster rule

Once an Oracle VM has been live migrated across a cluster boundary, Oracle counts every host in every cluster the VM has touched. The rule extends to vSphere Distributed Resource Scheduler enabled environments and to Storage vMotion targets.

The math when the rule applies

• Single host: One Oracle VM running on one host of 32 cores. License footprint is 32 cores.
• Single cluster: One Oracle VM on a six host cluster of 32 core hosts. License footprint is 192 cores.
• Cross cluster movement: Same VM, after one historical move to a second six host cluster. License footprint is 384 cores.

The buyer side mitigation

The mitigation runs through isolation. Pin Oracle VMs to a defined host group, disable DRS movement for the Oracle workloads, document the affinity rules, and reconcile the placement history against the documented baseline quarterly.

Nutanix AHV: the conditional recognition.

Nutanix AHV qualifies as hard partitioning with documented sub cluster isolation. The recognition was added to the Oracle partner approved hypervisor list in 2019. The condition is non negotiable.

What documentation Oracle expects

1. Cluster manifest: Every node, every socket, every core, dated.
2. Affinity rule definition: The Nutanix Prism rule pinning Oracle VMs to a defined node group.
3. Placement history: Logs showing the VM never crossed the isolation boundary across the audit window.

The Nutanix deep dive

Read our Nutanix Oracle licensing reference for the full evidence pattern, the audit triggers specific to Nutanix, and the renewal posture on the Nutanix Oracle estate.

Hyper V and KVM positions.

Microsoft Hyper V qualifies as hard partitioning under Hyper V CPU isolation when documented per the Oracle partner approved hypervisor list. The documentation requires Hyper V Manager export of the isolation configuration.

The Oracle Linux KVM position

Oracle Linux KVM qualifies as hard partitioning under documented CPU pinning. The pinning configuration must be exported, signed, and reconciled against the placement history. The same rule applies to Oracle VM Server.

Other KVM distributions

Red Hat KVM, SUSE KVM, and other distributions sit in a less defined space. The Oracle position typically defaults to soft partitioning at audit unless the customer has a specific written confirmation from Oracle on the configuration.

OCI and the partitioning question.

Oracle Cloud Infrastructure removes the partitioning question for Oracle Database workloads hosted on OCI shapes. The licensing follows the OCPU count or the BYOL math. The partitioning argument is no longer in play.

The OCI licensing models

• License Included: Oracle Database licensed by the OCPU on the OCI shape. No customer license required.
• Bring Your Own License: Customer brings the existing Oracle Database license to OCI. The BYOL math runs against the OCPU count.
• Database@Customer: Oracle Cloud Infrastructure shape sits in the customer data center. Same licensing models apply.

The buyer side reading

OCI is the cleanest answer to the partitioning question. The buyer side weighs the simplicity against the lock in to the Oracle cloud and the strategic implications for the broader cloud posture.

The defense pack that holds.

The audit reviewer asks for five evidence artifacts on virtualization. The defense pack assembles all five and stores them outside the operations team.

The five required artifacts

1. Cluster topology diagram: Signed, dated, identifying every node and the role per node.
2. Hypervisor configuration export: Affinity rules, DRS settings, CPU pinning, isolation rules.
3. VM placement history: Full move history across the audit window, exported and signed.
4. Storage vMotion log: Any storage level migration that touched the Oracle VM.
5. Change log: Cluster expansions, node replacements, and patch events tied to tickets.

Where the pack lives

The pack lives in procurement, not in operations. Operations refreshes it quarterly. Internal Audit reviews it annually. The first day of every audit window must reconcile cleanly to the documented baseline.

What to do next.

The Oracle virtualization defense rewards discipline more than any single tactic. The buyer side approach builds the evidence pack on day one and refreshes it quarterly.

The eight step Oracle virtualization checklist

1. Inventory the Oracle Database estate by hypervisor, by cluster, and by node.
2. Score each hypervisor against the partner approved list and the recognition requirements.
3. Document affinity rules, DRS settings, and CPU pinning per Oracle workload.
4. Pull VM placement history for the trailing 24 months and store it outside the cluster.
5. Reconcile the documented footprint against the Oracle order document line items.
6. Run the Oracle license calculator on the documented footprint.
7. Open the hidden Oracle audit risks reference for adjacent exposures.
8. Engage Oracle advisory ahead of the next audit window.

Frequently asked questions.