Oracle Licensing in VMware After Broadcom Changes

The Broadcom Shock: VMware Licensing Transformed Overnight

When Broadcom completed its 69 billion dollar acquisition of VMware in November 2023, it wasn't just a change of ownership. It was a restructuring of the entire licensing model that powers enterprise virtualisation. The shift from perpetual licenses to a pure subscription model triggered reported price increases ranging from 150 to 1,500 percent for some customers, with organisations reporting their VMware costs multiplying by 10 times their previous annual spend.

For enterprises running Oracle workloads on VMware, this transformation creates a secondary problem: Oracle licensing in VMware after Broadcom changes compounds the pain. Oracle classifies VMware as a soft partitioning platform, meaning Oracle must be licensed on all physical cores in the cluster, not just the cores consumed by individual Oracle databases. On top of VMware's subscription shock, organisations now face the prospect of massive Oracle licensing bills they may not have anticipated.

A practical example illustrates the exposure. Imagine a single Oracle database running on just 4 vCPUs within a VMware cluster that contains 10 hosts with 32 cores each. That's 320 total physical cores in the cluster. Under Oracle's soft partitioning rules, you must license all 320 cores. At the current Oracle database licensing rate of approximately 47,500 dollars per processor license, you're looking at 160 processor licenses times 47,500 equals 7.6 million dollars. That single 4 vCPU database just created a 7.6 million dollar licensing obligation.

Oracle Licensing VMware Broadcom: Understanding Soft Partitioning Risk

The core issue hinges on how Oracle defines partitioning. Oracle recognises only three hard partitioning methods that allow licensing of specific vCPUs: Oracle VM, Solaris Zones, and IBM LPAR. VMware is not on this list. VMware Enterprise Licensing Agreement classifies as soft partitioning, which means every physical core in the cluster counts toward your Oracle licensing obligation. This applies whether your Oracle databases actually use those cores or not.

The mechanics are straightforward: when you deploy Oracle inside a VMware virtual machine, Oracle doesn't care about the VM boundary. Oracle's licensing audit tools inspect the physical layer and count cores there. The presence of Oracle software on a hypervisor cluster triggers cluster-wide licensing across all physical cores, not just the vCPUs allocated to individual VMs.

Our Oracle virtualisation licensing risk assessment tool is specifically designed to identify this exposure before an audit team discovers it. Many organisations don't realise their Oracle licensing liability until after the fact. By that time, the gap between what they've paid and what they owe creates substantial audit risk.

The timing is critical because Broadcom's minimum core requirement has shifted to 72 cores per VMware cluster licence as of April 2025. This compounds the Oracle liability further. Smaller VMware deployments that previously required minimal licensing now trigger 72-core pack requirements, which in turn trigger Oracle cluster-wide licensing across all 72 cores for any cluster containing Oracle.

Broadcom's Pricing Transformation Amplifies Oracle Exposure

Before Broadcom's acquisition, many organisations operated VMware under perpetual licensing models where their upfront capital costs were amortised. Annual maintenance and support were fixed and predictable. When Broadcom forced the transition to subscription licensing, the financial model flipped. The same infrastructure that cost 100,000 dollars upfront now costs 150,000 to 1,500,000 dollars annually, depending on workload class and service level.

The Oracle licensing VMware Broadcom situation became exponentially more expensive because these two vendor cost increases occur simultaneously. You're not replacing perpetual VMware costs with subscriptions and adding Oracle separately. You're experiencing both a 10x VMware cost increase and discovering that Oracle licensing on that VMware cluster is cluster wide, not workload specific.

Read our detailed analysis of Broadcom VMware licensing changes explained to understand the full scope of VMware's subscription model shift. The interaction between these two licensing frameworks is where most organisations get exposed. You focus on renegotiating VMware costs and miss the Oracle liability sitting underneath.

The Hard Partitioning Migration Strategy: 80-95% Oracle Licence Reduction

The remediation path exists, though it requires investment and planning. Migrating from soft partitioning to hard partitioning can reduce your Oracle licensing obligation by 80 to 95 percent. The three recognised hard partitioning solutions Oracle accepts are Oracle VM (an Oracle-owned hypervisor), KVM with specific configuration, and IBM LPAR for mainframe deployments.

For most enterprises running on Broadcom VMware, the practical solution is migration to Oracle VM. This is not a trivial project. Migration to a new hypervisor platform involves infrastructure re-architecting, application testing, and operational retraining. The total project cost typically ranges from 100,000 to 300,000 dollars depending on workload complexity and organisational size.

However, the payback period is aggressive. An enterprise facing a 7.6 million dollar annual Oracle licensing obligation can fund a 250,000 dollar hard partitioning migration and break even in just 20 days. The annual savings of 6 to 7 million dollars pays for the project almost immediately. Even accounting for ongoing Oracle VM support costs, the financial case is compelling for any organisation with significant Oracle exposure on VMware.

The Oracle license consulting services team at Redress works with enterprises to model hard partitioning migration paths specific to their environment. This includes identifying which workloads should migrate first, sequencing the transformation, and validating that the migration actually achieves the projected licensing reduction. An independent advisor ensures the migration is done correctly the first time.

Oracle Cloud VMware Solution (OCVS) and the March 2026 Transition

Oracle also operates its own VMware offering through Oracle Cloud VMware Solution. As of March 2026, OCVS is transitioning from a bundled model to a Bring Your Own License (BYOL) approach. This creates a third decision point beyond just Broadcom VMware versus hard partitioning migration.

For some organisations, shifting Oracle workloads to OCVS and bringing their own VMware licenses might offer negotiating leverage. Oracle customers can sometimes get better pricing on their Oracle licenses when bundling them with infrastructure consumption. However, this only works if your Oracle licensing terms are negotiated as part of an infrastructure deal, and it requires that Broadcom's VMware licensing rates are competitive with whatever your Oracle infrastructure costs would be otherwise.

The reality is that by 2026, the vendor consolidation in the virtualisation space has narrowed options considerably. Broadcom has consolidated the VMware partner ecosystem from over 4,500 VSCPs down to approximately 12 Pinnacle partners and 300 Premier partners. Product consolidation has collapsed roughly 8,000 VMware SKUs into bundled VCF and VVF offerings. The marketplace is less fragmented than it was, which means less room for negotiation and fewer alternative paths.

This is exactly why independent advisory is valuable. We can model your options objectively. That includes whether staying on Broadcom VMware with Oracle's BYOL on Oracle infrastructure is cheaper than hard partitioning migration, or whether a hybrid approach splitting workloads between platforms makes financial sense. Vendor Shield, our subscription advisory service, keeps this analysis fresh as vendor pricing and your infrastructure evolves.