◆ White Paper

The VMware Licensing Survival Guide.

Oracle's partitioning policy does not recognise VMware as hard partitioning, so an audit claims every host the software could run on across the cluster. This white paper shows why that claim rests on policy rather than the contract, and how a contract first defense brings it down.
01 What is inside

A buyer side playbook for Oracle on VMware.

Six to ten pages of substance: the problem stated plainly, the mechanics with real numbers, a defense framework, and a checklist you can run against your own estate before an audit lands.

  • Why Oracle treats VMware as soft partitioning and what that means for scope
  • The cluster wide claim, vMotion history, and how each is contested
  • The contract versus policy distinction that often carries the number
  • How collection scripts overcount across virtualization layers
  • A pre audit checklist and an evidence file template

Independent line by line review of findings typically cuts claims 60 to 80 percent, and virtualization is where some of the largest reductions sit. For the full method, read the Oracle virtualization licensing guide.

◆ Download

Get the guide

Enter a work email and we will send the white paper. You can subscribe to The License Position when you download.

Independent buyer side advisory. New York and London.

02 The core problem

Why a VMware estate creates Oracle exposure.

Oracle distinguishes hard partitioning, which can limit licensable cores, from soft partitioning, which in Oracle's view cannot. Oracle's partitioning policy does not recognise VMware, Hyper V or KVM as hard partitioning. From that position Oracle argues you must license every physical host the software could be moved to, which in a modern cluster with vMotion can mean the entire estate.

The critical point for buyers is that this argument rests on a policy paper, not on the signed agreement. The policy document is not the contract, and contract language beats policy. Cluster wide claims are frequently overstated, and the defensible scope depends on your architecture, your configuration, and what can actually be demonstrated rather than on Oracle's default assumption that everything is licensable everywhere.

Oracle's own collection scripts can overcount across virtualization layers, so the output is reviewed before submission rather than handed over as found. The white paper walks through each of these points with worked numbers and gives you the evidence file template to build your own defensible position.

◆ FAQ

Questions about Oracle on VMware.

No. Oracle's partitioning policy does not recognise VMware, Hyper V or KVM as hard partitioning, which is why Oracle claims you must license every host the software could run on across the cluster.
It rests on a policy document, not the contract. The signed agreement usually governs and contract language beats policy, so cluster wide claims are frequently overstated and reducible. This is a contract dependent point worth establishing early.
Running the scripts at all is a decision, not an obligation, and the output can overcount across virtualization layers. We review script output before anything is submitted.
◆ The License Position

Read Oracle's next move before they make it.

A short weekly note on Oracle audits, Java, ULAs and negotiation. One development, why it matters, and one move you can make this week.

Read across enterprises in New York, London and beyond.