Does Oracle recognise VMware as hard partitioning?
Oracle does not recognise VMware as hard partitioning, because its partitioning policy classifies VMware as soft partitioning, a category the policy says cannot be used to limit how many processors must be licensed. To Oracle, soft partitioning means the boundaries are set in software and could in principle be changed, so the policy refuses to let those boundaries cap your licensing. The practical result is that a finding can claim every physical host in a cluster a virtual machine could reach, not just the hosts where Oracle ran.
This single classification drives the largest inflated findings in Oracle licensing. A handful of Oracle virtual machines on a large cluster become a demand to license every core in that cluster, multiplied by the core factor table. It is also the most disputable finding, because the entire claim rests on a policy classification rather than a contractual term. The full virtualization picture sits in the Oracle virtualization licensing guide.
The soft partitioning label is a policy position, not a contractual fact. It produces the cluster wide claim, and it is also the weakness in that claim, because policy classifications do not override what your signed agreement actually says.
What does Oracle accept as hard partitioning?
Oracle accepts only specific technologies as hard partitioning, the named physical and engineered methods its policy lists, and it excludes the common hypervisors most enterprises run. The policy treats certain processor level and engineered system partitioning approaches as hard, meaning they can bound licensing, while placing VMware, Hyper V, and KVM in the soft category. The list is Oracle's own, published in the policy document, and it is narrow by design.
This matters because buyers reasonably assume that a technical boundary, a VMware cluster that physically never ran Oracle on most hosts, should limit their exposure. Under the policy it does not, because the policy only credits the methods on its list. The treatment of the other soft hypervisors follows the same logic and is covered in our cluster and hypervisor content. The key point is that the hard versus soft line is drawn by Oracle policy, and policy is contestable.
| Technology | Policy classification | Effect on the claim |
|---|---|---|
| VMware | Soft partitioning | Cluster wide claim |
| Hyper V | Soft partitioning | Cluster wide claim |
| KVM | Soft partitioning | Cluster wide claim |
| Listed engineered methods | Hard partitioning | Bounded to the partition |
Why is the partitioning policy not the contract?
The partitioning policy is not the contract because it is a separate document Oracle publishes and updates on its own, and in most agreements it is not incorporated as a binding term of the signed Oracle Master Agreement. Where a policy paper and the contract conflict, the contract governs. This is the legal hinge of every VMware dispute, and it is why the buyer move always begins with reading the agreement rather than accepting the policy as a rule you agreed to.
Auditors present the partitioning policy as though it were a term of your contract. Frequently it is not. The agreement defines the licensed programs, the metrics, and the obligations, and it rarely states that a soft partitioning hypervisor requires licensing every host in a cluster. When the contract is silent, the policy cannot create an obligation the contract never contained. That same principle runs through every cluster wide dispute, detailed in disputing cluster wide virtualization claims.
How does the cluster wide claim form?
The cluster wide claim forms when Oracle combines the soft partitioning classification with the mobility of virtual machines to argue that every host is a place Oracle could run. Because a virtual machine can migrate across the cluster, Oracle asserts that every physical host must be fully licensed, applying the core factor table across all of them. On a large cluster the multiplier is enormous, turning a few Oracle hosts into a demand spanning dozens of servers.
The collection scripts reinforce the claim, because they can sweep an entire virtualization layer and report every core as if Oracle were deployed across it. Running those scripts is a decision, not an obligation, and submitting their raw output concedes the cluster wide premise before negotiation begins. How the scripts overcount across virtualized estates is set out in how scripts overcount in virtualized estates.
How does the soft partitioning distinction defend you?
The soft partitioning distinction defends you because it is the very thing that makes the cluster wide claim a policy argument rather than a contractual entitlement, which means it can be contested by anchoring to your agreement and reconciling to actual deployment. Once you establish that the partitioning policy is not incorporated into your contract, the claim loses its foundation, and the obligation becomes what the agreement actually says about the programs you licensed.
- Read the agreement and confirm whether the partitioning policy is incorporated
- Where it is not, decline to accept the soft partitioning classification as obligation
- Map actual Oracle installation and runtime to specific hosts
- Document host affinity, segregation, or sub clusters that bounded mobility
- Reconcile the claim to documented deployment, not cluster topology
Whether the partitioning policy binds you is contract dependent. Some agreements reference partitioning terms directly. The dispute always begins by reading your specific signed agreement rather than assuming the general position holds.
A worked example
Consider an anonymized retailer running Oracle on six hosts within a forty eight host VMware cluster, segregated into a dedicated resource group with affinity rules. Oracle's opening finding applied the soft partitioning classification and claimed the full cluster.
| Stage | Position |
|---|---|
| Opening finding, all 48 hosts under the policy | $11.2M |
| After contract anchoring and host reconciliation | $2.6M |
The agreement did not incorporate the partitioning policy, and the six Oracle hosts sat in a documented, segregated resource group. Reconciled to those hosts, the defended position fell roughly 77 percent, within the 60 to 80 percent range a line by line review typically achieves. This example is illustrative and anonymized, and outcomes depend on your estate, your contract and your evidence.
Your next step
The soft partitioning classification is the reason VMware findings are so large and the reason they are so disputable. An independent buyer side review tests the policy against your specific contract and reconciles the claim to real deployment. Our advisors work on a Fixed Fee or Gainshare basis with no risk to you, and we reduce your Oracle exposure or we reimburse our service fee.
Read the Oracle virtualization licensing guide for the full partitioning policy versus contract distinction, then test it against your own cluster.