Answer 8 questions to assess your Oracle licensing exposure on VMware, Hyper-V, and other virtualisation platforms.
5-10x
VMware Licence Multiplier
8
Questions
3 min
To Complete
Question 1 of 8Oracle Virtualisation Advisory
Question 1 of 8
⚙️
Which virtualisation platforms run Oracle workloads in your environment?
Oracle's licensing treatment varies dramatically by virtualisation technology.
Oracle VM (OVM) or Oracle Linux KVM only
Oracle-approved hard partitioning
Hyper-V (capped VMs)
Licence only the host servers in the cluster
VMware vSphere
Oracle claims all cores in all clusters
VMware with Oracle on multiple large clusters
Question 2 of 8
🖥️
How many ESXi hosts are in the cluster(s) running Oracle?
Oracle's position is that ALL physical cores in ALL hosts in the cluster must be licensed — not just the host running the Oracle VM.
Not on VMware (or isolated single-host)
2–8 hosts in the cluster
8–32 hosts in the cluster
32+ hosts or multiple large clusters
Licensing exposure could be in the tens of millions
Question 3 of 8
🔒
Have you implemented any containment strategies (DRS rules, dedicated clusters)?
While Oracle doesn't officially recognise VMware DRS affinity rules, containment can reduce audit exposure.
Dedicated physical cluster for Oracle only
Strongest containment position
DRS affinity rules pinning Oracle VMs to specific hosts
Oracle VMs can move freely across the cluster
No containment — Oracle mixed with all other workloads
Question 4 of 8
📋
Do you have documentation proving where Oracle VMs have run historically?
In an audit, Oracle may ask for historical vMotion logs. If VMs have moved across hosts, those hosts may be in scope.
Yes — full vMotion logs and VM placement history retained
Partial — some logging but not comprehensive
Minimal — default vCenter logs only
No documentation of VM movement history
Question 5 of 8
📊
How many total physical cores are in the cluster(s) where Oracle VMs could run?
This is the number Oracle would use to calculate your licence requirement.
Under 100 cores
100–500 cores
500–2,000 cores
2,000+ cores
At $47,500/processor × 0.5 core factor, exposure exceeds $20M+
Question 6 of 8
🔄
Are you planning to migrate Oracle workloads off VMware?
Moving Oracle to physical servers, OVM, or cloud can eliminate virtualisation licensing risk entirely.
Yes — migration underway to dedicated physical or OVM
Planning — migration approved but not started
Considering — no firm plans yet
No — Oracle will remain on VMware indefinitely
Question 7 of 8
📜
Do you have an Oracle ULA that covers your VMware deployments?
A ULA provides unlimited deployment rights during the term. This can offset VMware exposure but affects certification.
Yes — active ULA covering all relevant products
ULA covers some but not all products on VMware
No ULA — standard per-processor licensing
ULA expired and we certified — VMware was not fully addressed
Question 8 of 8
🛡️
Have you sought independent advice on your virtualisation licensing position?
Oracle's virtualisation policy is their most disputed and commercially aggressive position. Expert guidance is essential.
Yes — independent advisor engaged
Internal legal/procurement has reviewed
No — relying on Oracle's guidance
Oracle's guidance maximises their revenue
No — haven't addressed virtualisation licensing
Need Expert Oracle Licensing Guidance?
Redress Compliance provides independent Oracle licensing advisory services to enterprises worldwide. No vendor relationships. No conflicts of interest. Just results.