What Broadcom Changed — and What It Didn't

Broadcom completed its acquisition of VMware in November 2023 at a purchase price of 61 billion dollars. The commercial changes that followed were significant: Broadcom eliminated perpetual VMware licences, moved all products to subscription-based bundles under the VMware Cloud Foundation (VCF) brand, discontinued over 50 standalone products, and significantly raised pricing for enterprise customers. Many VMware customers saw their annual cost increase by 3 to 5 times under the new VCF subscription model.

What Broadcom's changes did not alter: Oracle Corporation's Partitioning Policy, published in January 2017, has not been updated in response to the Broadcom acquisition. VMware vSphere ESXi — whether licensed under old perpetual terms or the new VCF subscription — remains classified as soft partitioning under Oracle's policy. Every host in your VMware cluster that can run Oracle software must still be fully licensed. The oracle licensing vmware broadcom situation is commercially different from the pre-acquisition environment; it is not legally different from Oracle's perspective.

This distinction is critical for enterprises evaluating their VMware exit options. A VMware cluster running on new VCF subscription terms is subject to the same Oracle licence counting rules as a cluster licensed under the old perpetual model. Your annual Oracle licence exposure has not decreased because your VMware commercial terms have changed.

For detailed guidance on how Oracle counts licences across virtualisation environments, see our oracle licensing virtualisation guide and our hard versus soft partitioning analysis.

The VMware Exit Wave and Oracle Audit Risk

Broadcom's aggressive pricing changes triggered a significant VMware exit wave throughout 2024 and into 2025. Large enterprises that had invested heavily in VMware for 10 to 15 years began accelerating evaluations of alternatives: Nutanix AHV, Microsoft Hyper-V, Red Hat OpenShift Virtualisation, Proxmox, and migration to cloud providers including OCI, AWS, and Azure.

The Oracle audit risk created by VMware exit is specific and serious. When enterprises decommission their VMware clusters, they also decommission the vCenter servers and their associated log databases. The vCenter event logs contain the complete migration history — DRS moves, vMotion operations, HA failovers — that LMS auditors rely on to reconstruct historical Oracle software deployment across the cluster.

Once the VMware infrastructure is decommissioned and the vCenter logs are gone, Oracle LMS cannot directly reconstruct the historical deployment topology. However, Oracle can argue that the absence of exculpatory evidence supports the worst-case licence position. The correct approach is to conduct a full Oracle licence audit readiness assessment before decommissioning VMware infrastructure, export and preserve the relevant vCenter logs and configuration data, and ensure your Oracle licence position is defensible before the evidence disappears.

Oracle's Current Enforcement Position on VMware

Oracle LMS has not announced any change to its VMware enforcement position following the Broadcom acquisition. In our experience across Oracle engagements in 2024 and 2025, LMS auditors continue to request vCenter event logs and DRS migration histories as standard components of Oracle database audit evidence packages. The frequency of Oracle audits targeting VMware environments has not decreased — if anything, the disruption in the VMware market has created more audit triggers as enterprises change their virtualisation configurations during VMware exit projects.

An important nuance: VCF subscription does not create any new hard partitioning capability. VCF bundles vSphere, vSAN, NSX, and Aria management under a subscription model, but the underlying ESXi hypervisor remains soft partitioning. Buying VCF does not change your Oracle licence position.

Oracle's audit team has also been increasingly focused on identifying enterprises that are in mid-transition during VMware exit projects. The rationale is straightforward: if you are decommissioning VMware, you are either migrating workloads to a new hypervisor or to the cloud. Either way, your Oracle licensing configuration is changing. Oracle's LMS team sees this as an opportunity to initiate a full audit of both your pre-transition and post-transition Oracle environment. The timing of a VMware migration — whether to a new hypervisor or to cloud — should therefore factor in the possibility of an Oracle audit window opening during the transition period.

For a comprehensive understanding of Oracle's audit strategy and your defensive options, refer to our oracle license audit defence playbook.

Migration Paths That Resolve Oracle Virtualisation Exposure

For organisations in active VMware exit discussions, the Oracle licence position should be a factor in the alternative platform selection, not an afterthought. Four paths that provide improved Oracle licence compliance:

Path 1 — Oracle OCI with BYOL: The cleanest resolution. OCI VM shapes provide sub-capacity counting. Migrating Oracle Database from VMware clusters to OCI typically reduces Oracle processor licence requirements by 60 to 80 percent whilst eliminating the soft partitioning exposure. This path is commercially and technically the most attractive for enterprises with significant Oracle Database deployments. See our oracle BYOL OCI licensing guide for cost modelling and implementation strategies.

Path 2 — Oracle VM for x86 (OVM): A dedicated OVM cluster for Oracle Database workloads, with remaining workloads migrating to the chosen alternative hypervisor. OVM is free but requires operational investment to manage a separate hypervisor environment. For enterprises with smaller Oracle Database footprints, OVM provides a pragmatic middle ground between BYOL reduction and operational simplicity.

Path 3 — Nutanix AHV: Nutanix AHV is also soft partitioning under Oracle's policy. Moving from VMware to Nutanix AHV does not resolve the Oracle licence compliance issue — it moves it to a different hypervisor. Organisations evaluating Nutanix as their VMware alternative need to understand this clearly. Your Oracle licence exposure persists regardless of whether you run Oracle Database on VMware ESXi or Nutanix AHV.

Path 4 — IBM Power with dedicated LPARs: For Oracle Database workloads currently running on x86/VMware, migration to IBM Power with AIX dedicated LPARs provides genuine hard partitioning. The infrastructure cost is higher, but the licence reduction can be substantial for large deployments. This path is most viable for enterprises with significant Oracle Database workloads and the capital budget to support Power infrastructure. Refer to our oracle licensing virtualisation guide for hard partitioning framework details.

What to Do Before Your VMware Exit Project Starts

Step-by-step actions: First, export vCenter event logs covering the full three-year audit look-back period and store them securely outside the VMware infrastructure. Second, conduct an Oracle licence audit readiness assessment against your current VMware cluster topology — identify how many Oracle processor licences are technically required under Oracle's policy. Third, compare that figure to your actual licence entitlements and quantify the gap. Fourth, determine whether the gap should be remediated before VMware exit (via ULA, BYOL migration, or OVM deployment) or whether the risk can be managed through a negotiated settlement if Oracle audits during the transition period. Fifth, select your new virtualisation platform with Oracle licence compliance factored into the decision.

The sequence matters: most enterprises reverse this order — they choose their VMware alternative first, then discover the Oracle licence implications. Reversing the sequence saves significant time and cost. An enterprise that exports vCenter logs and runs an Oracle audit readiness assessment before selecting a VMware alternative is equipped to negotiate the Oracle compliance impact into the cost-benefit analysis of each alternative platform. An enterprise that selects their new platform first, then discovers an Oracle licence gap, faces a much costlier remediation period and loses leverage to negotiate the remediation cost into the platform selection decision.

Redress has guided enterprises through this sequence across Oracle, Microsoft, SAP, and Broadcom software. Our oracle total cost optimisation guide provides a framework for sequencing and costing the VMware exit decision. Our oracle ULA complete buyers guide addresses ULA as a remediation vehicle if your audit readiness assessment identifies a gap. And our oracle knowledge hub contains every resource you need to plan your exit.