The Oracle position on VMware partitioning is a publisher policy memorandum, not a contractual instrument. The Admodum read on affinity rules, host pinning, vMotion mobility scope, the Broadcom acquisition reset and the architectural alternatives.
The VMware question is the long-running buyer-side question about how Oracle licensing reads across a VMware cluster. The publisher position is that Oracle must be licensed against every host in the fabric where the Oracle workload could run, not only against the hosts where it does run. The buyer position contests the publisher reading on the basis that VMware partitioning is not a contractual exclusion but a policy memorandum.
The question is materially important because VMware clusters are typically larger than the Oracle deployment within them. A four-VM Oracle deployment that sits on a forty-host VMware fabric would, under the publisher reading, require licensing for the full forty hosts. Under the buyer reading, with architectural constraints in place, the licensable scope can be the smaller deployed footprint.
The wider editorial sits in the Oracle pillar; the deeper read on the partitioning policy sits at partitioning policy.
Oracle’s partitioning policy is set out in a document titled “Oracle Partitioning Policy”, available on the publisher’s website. The document distinguishes between hard partitioning (approved) and soft partitioning (excluded). Hard partitioning includes named technologies (PowerVM logical partitions, Solaris Containers, IBM LPAR, selected hard-CPU pinning). Soft partitioning includes all hypervisor-based partitioning, including VMware ESXi.
The structural reading of the document is that it is a publisher policy, not a contractual instrument. The policy is referenced by Oracle’s licence management services and by the account team, but it is not, on its own terms, contractually binding on the buyer unless the buyer’s specific contract has incorporated it by reference.
The buyer-side discipline is to read the specific OMA / OLSA and Schedule A documents for any incorporation clause. Where the contract does not reference the policy, the policy is publisher commentary; where the contract references the policy, the buyer reads the precise reference and the effect.
The buyer-side architectural response to the policy position is the affinity-rule discipline. VMware affinity rules pin specific VMs to specific hosts: the Oracle VM is constrained to run only on a named subset of hosts in the cluster, and the cluster is configured to prevent the Oracle workload from spilling onto any other host.
The discipline carries two operational requirements. Affinity rules must be configured as DRS (Distributed Resource Scheduler) host-affinity rules at the cluster level, not as VM-level guidance. The rules must be set to “must” rather than “should”, so that DRS will not violate them even under host failure.
Where the discipline is consistently in place, the buyer can argue that the licensable scope is the named host subset, not the full cluster. The argument is more credible where it is supported by audit-quality artefacts: a documented architectural policy, change-control records, configuration screenshots, and an internal audit of compliance with the policy.
VMware’s vMotion (and related vSphere features such as Storage vMotion, vSphere HA, vSphere DRS) carry version-by-version mobility scope. Older vSphere versions limit vMotion to a single cluster; newer versions extend it across clusters within a vCenter, and the newest extend it across vCenters within a region. The publisher’s policy reading scales the licensable fabric with the mobility scope.
The buyer-side discipline tracks the vSphere version and the mobility scope explicitly. A vSphere environment configured to limit vMotion to within a single cluster carries a smaller licensable fabric than the same environment with cross-cluster vMotion enabled. The architectural choice to disable broader vMotion is therefore also a licensing choice.
The deeper read on the broader VMware position sits at VMware on Oracle and the wider Broadcom pillar reading at the Broadcom / VMware pillar.
The November 2023 Broadcom acquisition of VMware reset the VMware commercial position. Perpetual licences ended, the SKU portfolio was rationalised into VCF and VVF bundles, pricing moved from per-CPU to per-core (with a 16-core minimum per CPU), and the partner channel was reduced in scope. The reset materially changed the VMware total cost of ownership and pushed many buyers to revisit the VMware position alongside the Oracle position.
The combined effect is that the Oracle-on-VMware question is now also a VMware-on-Broadcom question. The buyer-side response often runs the two positions in parallel: the Oracle licensing risk on the VMware fabric, and the VMware commercial risk under the new Broadcom envelope. Both push toward the architectural-alternative reading below.
The deeper read on the Broadcom reset sits at the Broadcom / VMware pillar and on Cisco-Broadcom interactions in the wider portfolio at the Broadcom / VMware practice.
Where the Oracle-on-VMware position is no longer commercially or technically attractive, the buyer-side architectural alternatives read in five families. Nutanix AHV (the Nutanix-native hypervisor) carries the Nutanix “approved partitioning” position. Red Hat OpenShift Virtualisation runs KVM-based VMs alongside containerised workloads. Proxmox (open-source KVM) sits in the cost-optimised tier. Hyperscaler-native deployment (AWS Outposts with Oracle BYOL, Azure Oracle Database, GCP Bare Metal Solution) avoids the question by removing VMware. Physical-only Oracle hosts (no virtualisation) avoid the question by removing virtualisation entirely.
Each alternative carries a migration cost, a steady-state cost, an operational complexity and a licensing-position implication. The choice is engineering and commercial, not licensing-only. The wider engagement sits in the Oracle practice with cross-reference into the Broadcom / VMware practice; the aggregated reading list sits in the Oracle knowledge hub; the audit-defence programme sits at audit defence.
A senior Admodum Oracle advisor will read your VMware fabric, the vMotion scope and the Broadcom-side commercial reset on a private call. Active audits route to the Audit Defence programme.