Oracle Virtualisation Licensing After Broadcom:
VMware, Hyper-V, KVM Rules — and Why Your VMware Exit Strategy Needs Oracle Licensing Analysis

The Broadcom Acquisition Changed the VMware Licensing Landscape — and Elevated Oracle Licensing Risk

Broadcom's acquisition of VMware in 2023 and the subsequent licensing changes — migration from perpetual to subscription, elimination of standalone product SKUs, mandatory transition to VMware Cloud Foundation bundles — created significant cost pressure for organisations with large VMware estates. Many enterprises responded by accelerating VMware exit strategies: migrating workloads to public cloud, evaluating Nutanix and Microsoft Hyper-V as hypervisor alternatives, or moving Oracle workloads to OCI. These transitions have direct Oracle licensing implications that compound the VMware cost disruption.

This guide covers the updated Oracle virtualisation licensing picture for 2026: Oracle's hard/soft partitioning rules on VMware vSphere (now under Broadcom), why the Broadcom acquisition specifically elevated Oracle licensing risk for VMware customers, Oracle's treatment of Hyper-V and KVM (the most common VMware alternatives), and the licensing implications of migrating Oracle workloads to OCI or alternative hypervisors as part of a VMware exit. For Oracle container licensing in Kubernetes environments, see our companion Oracle container licensing guide. For virtualisation licensing risk assessment, our Oracle advisory team provides comprehensive Oracle virtualisation reviews.

Oracle's Core Virtualisation Licensing Rule: Hard vs Soft Partitioning

Oracle's position on virtualisation licensing has been consistent since its 2006 partitioning policy documentation and has not changed despite multiple hypervisor technology changes. The rule:

If a virtualisation technology allows Oracle Database to migrate between physical hosts — either automatically (live migration, vMotion, DRS) or manually — all physical hosts in the cluster or pool where Oracle can run must be fully licensed, regardless of how many hosts Oracle actually runs on at any given time. This is soft partitioning. If a technology provably restricts Oracle to a defined physical CPU set that cannot be changed without physical intervention or Oracle-recognised administrative action, only those CPUs need to be licensed. This is hard partitioning.

Oracle recognises only two primary technologies as hard partitioning for x86/x64 environments: Oracle VM Server for x86 (OVM) and Oracle Solaris Zones on SPARC. All other x86 hypervisors — VMware vSphere, Microsoft Hyper-V, Citrix XenServer, KVM, and Nutanix AHV — are classified as soft partitioning. The licensing implication for any soft partitioning environment: license the full physical processor count (applying core factors) of every host in the cluster or resource pool where Oracle can be placed.

VMware After Broadcom: Why Oracle Licensing Risk Increased

Oracle's virtualisation licensing policy pre-dated Broadcom and applied equally to VMware vSphere before the acquisition. Why did the Broadcom acquisition increase Oracle licensing risk for VMware customers?

The primary mechanism is the VMware licensing model change. Under the pre-Broadcom perpetual VMware model, many organisations had VMware vSphere licenses covering defined clusters — and while they may have been technically under-licensed for Oracle (by not licensing every host in the DRS cluster), the fixed VMware estate created at least a definable boundary. The Broadcom subscription model eliminated per-host and per-cluster granularity in many licensing structures, and the VCF bundle changes altered how infrastructure capacity is tracked and reported. The administrative controls some organisations used to document Oracle VM placement became less precise as VMware's own licensing documentation changed.

More directly: the VMware cost increases from Broadcom have driven many organisations to rapidly expand VMware estates to VCF bundles (to minimise per-VM cost under the new subscription structure), consolidate to fewer, larger vSphere clusters (to reduce subscription costs), and accelerate DRS-enabled automation across expanded clusters — each of which expands the physical host footprint that Oracle licensing rules require to be fully licensed. An organisation that expanded from a 10-host to a 30-host DRS cluster as part of VCF consolidation has tripled its Oracle licensing obligation on that cluster under Oracle's soft partitioning rules.

Hyper-V: The Most Common VMware Alternative and Its Oracle Licensing Implications

Microsoft Hyper-V is the most common VMware vSphere replacement evaluated in 2024–2026 enterprise VMware exit strategies, driven by existing Microsoft licensing relationships and the integration of Hyper-V into Windows Server licensing. Oracle's treatment of Hyper-V is identical to VMware: soft partitioning, requiring full licensing of all physical hosts in the Windows Server Failover Cluster (WSFC) where Oracle VMs can run. Hyper-V's live migration capability — which is the HA mechanism that makes Hyper-V a viable vSphere alternative — is the same feature that prevents it from being Oracle hard partitioning.

For organisations evaluating Hyper-V as a VMware replacement, the Oracle licensing question to answer before migration: how many physical hosts are in the Hyper-V failover cluster that will host Oracle VMs, and how does that compare to the current VMware cluster host count? If the Hyper-V cluster is larger than the current VMware cluster (common when consolidating infrastructure), the Oracle licensing obligation increases with the migration.

OCI and the Hard Partitioning Path for Oracle Workloads

Oracle Cloud Infrastructure offers two paths to hard partitioning for Oracle Database workloads: Bare Metal instances (single-tenant physical servers, licensed at OCPU count by Oracle's cloud pricing) and Dedicated VM Hosts (physical servers dedicated to a single customer, with Oracle VMs placed exclusively on that host). Both approaches satisfy Oracle's hard partitioning requirement because the physical infrastructure is dedicated — no other customer's workloads share the physical CPUs allocated to Oracle.

The OCI licensing economics for VMware exit candidates depend on whether BYOL applies (existing on-premises Oracle licenses applied to OCI) and the OCPU count required. For organisations with existing Oracle processor licenses and active support contracts, OCI BYOL Dedicated VM Hosts provide the hard partitioning boundary with significantly lower new license spend compared to building out a dedicated OVM cluster on-premises. For virtualisation risk assessment and OCI migration planning support, our Oracle advisory team provides independent analysis. Book a virtualisation risk assessment before your VMware exit decision is finalised.