Running Oracle Database on VMware vSphere raises the host-fabric question: does the licence cover the deployed virtual machine or the entire vSphere cluster the VM could migrate to. The Admodum read on the policy memorandum, the affinity-rule discipline and the audit-quality position.
An Oracle Database virtual machine running on VMware vSphere can technically migrate, via vMotion, across all hosts in the vSphere cluster (and, depending on the vSphere version, across all clusters in the vCenter). The host-fabric question is whether the Oracle licence covers the host the VM is currently deployed on, or the wider fabric of hosts the VM could deploy on.
The contractual position rests on the Oracle Master Agreement and the Ordering Document. Neither names VMware; both speak of the "installed" location of the Programs. The interpretive question is whether "installed" means the specific host running the workload at a point in time, or the wider fabric of hosts authorised to host the workload.
The wider editorial sits in the Oracle pillar; the Broadcom acquisition context sits at Oracle and VMware under Broadcom; the partitioning policy context sits at the partitioning policy.
The publisher's position is set out in an internal policy memorandum (the partitioning policy document). The memorandum reads the wider fabric as the licensing surface: every host the VM could vMotion to is, in the publisher's reading, a host requiring Oracle licences.
The memorandum is publisher policy, not a contractual instrument. The contractual position remains the Oracle Master Agreement and the Ordering Document. The memorandum is the position the LMS audit teams apply when they engage; it is not the position a court would necessarily reach on the contractual interpretation.
The buyer-side discipline is to read the memorandum as the audit posture (the position the LMS team will assert), and to plan the contractual and architectural response accordingly. The wider LMS audit anatomy reads the position; the LMS settlement position reads the response.
The principal architectural mitigation is the affinity rule. VMware vSphere supports DRS (Distributed Resource Scheduler) affinity rules at the cluster level. A "must-run-on" rule binds a VM (or a VM group) to a defined subset of hosts in the cluster; the VM cannot vMotion outside the host group.
The buyer-side discipline implements DRS must-rules for every Oracle Database VM, mapped to a defined Oracle host group (a subset of hosts inside the cluster that are licensed for Oracle). The must-rule is operationally enforceable; the audit-time read against the rule is the licensed host group, not the wider cluster.
The discipline carries two operational requirements. First, the rule must be a must-rule, not a should-rule (a should-rule is advisory; vSphere will violate it under load). Second, the rule must be audit-quality: documented in vCenter, exported regularly as evidence, reviewed at every cluster reconfiguration.
The scope of vMotion mobility has evolved across vSphere versions. In vSphere 5.0 and earlier, vMotion was confined to the cluster. In vSphere 5.1 and later, cross-vCenter vMotion became available (with vSphere 6 expanding it further). In vSphere 6.7 and 7.x, long-distance vMotion across geographic boundaries became routine.
The publisher's audit position has tracked the technical scope: the wider the vMotion fabric, the wider the asserted licensing surface. In a vSphere 5 cluster, the assertion sits at the cluster level. In a vSphere 6 or 7 deployment without affinity discipline, the assertion can extend to all hosts in the vCenter (and, in some readings, across vCenters connected by Enhanced Linked Mode).
The buyer-side discipline is to map the actual vMotion scope (configured in vSphere) against the asserted vMotion scope (in the publisher's reading) and to align the two through affinity rules, version pinning, or architectural separation of the Oracle workloads from the wider vSphere fabric.
Broadcom acquired VMware in November 2023. The acquisition reset the commercial construct: VMware perpetual licensing was discontinued, the product portfolio was consolidated into the VCF (VMware Cloud Foundation) bundles, the licensing model moved to per-core subscription with a sixteen-core minimum per CPU.
The reset has changed the conversation for buyers who run Oracle on VMware. The vSphere subscription rate has risen materially for many buyer profiles; the architectural alternatives (Nutanix AHV, Red Hat OpenShift Virtualisation, Proxmox, hyperscaler-native virtualisation, and physical-only deployment) have entered serious consideration; the multicloud delivery of Oracle Database (Database@Azure, Database@AWS, Database@Google Cloud) provides an additional path off the on-premises virtualisation stack altogether.
The wider Broadcom-VMware practice and the broader virtualisation alternatives sit in the Broadcom / VMware practice; the Multicloud alternative read sits at Oracle Multicloud.
The buyer-side artefacts to hold against Oracle on VMware are: the vSphere cluster topology map (hosts, vCenters, ELM relationships, vMotion-enabled boundaries), the Oracle host group map (the subset of hosts licensed for Oracle workloads), the DRS must-rule export per Oracle VM (audit-grade evidence of the affinity discipline), the vSphere version history (against the published vMotion-scope changes), the cumulative Schedule A entitlement against the host-group core count and the contract-time language on installed location.
The audit-time conversation is then a documented position: the buyer asserts the host group as the licensing surface, presents the DRS must-rule evidence, presents the version-controlled vMotion scope, and reads the entitlement against the host-group core count. The publisher's wider-fabric assertion meets the buyer's evidenced narrower-fabric position; the negotiation settles on the documented position rather than on the policy memorandum's default reading.
The wider engagement sits in the Oracle practice; the aggregated reading list sits in the Oracle knowledge hub; active renewal moments route to the Renewal Programme; active audit moments route to Audit Defence.
The wider hard versus soft partitioning read inside the same policy memorandum.
The Broadcom reset and the four architectural alternatives read in plain language.
A senior Admodum Oracle advisor will read your vSphere topology and DRS posture against the cumulative entitlement on a private call. Active audit moments route to Audit Defence.