Oracle on Nutanix, the cluster boundary is the bill
Nutanix AHV runs production Oracle well; the problem was never the platform. Oracle's counting rule looks straight past the virtual machine: AHV has never appeared on the approved hard partitioning list, so under the soft partitioning position the license follows every processor the database could run on, and the cluster design, not the database team, decides the exposure.
Prepared by Redress Compliance · August 7, 2026 · Oracle advisory. Based on 25 to 35 Oracle on Nutanix estates reviewed 2024 to 2025.
Executive summary
The KVM lineage does not rescue AHV.
Oracle approved Oracle Linux KVM configured with Oracle's own pinning method, a named product and a named procedure, not KVM as a category, and no Nutanix document can put AHV on Oracle's list: Nutanix's pinning guides are useful engineering and carry no Oracle licensing weight.
The lineage argument has never won an audit we have seen.
The unbounded count is the catastrophe number. Six nodes of dual socket 32 core servers is 384 physical cores, 192 Processor licenses after the 0.5 core factor, and $9.12 million at Enterprise Edition list plus $2.0 million of annual support, before options.
The same database on a dedicated three node cluster of 16 core servers is 24 licenses and $1.14 million: the boundary you multiply by decides everything.
Only a physically separate cluster survives the audit.
Live migration does not cross a Nutanix cluster boundary, which is why the dedicated cluster is the containment that holds.
Affinity policies shorten the argument but do not change the rule, and 1 in 3 estates could not evidence their policies for the audit window because nobody exported them before the letter arrived.
Where a dedicated cluster existed, the licensable count landed 40 to 60 percent below the opening claim and the argument was over in one meeting.
Two costs nobody prices: the CVM and the options stack. Every AHV node runs a Controller VM at roughly 8 to 12 vCPUs, about 18 of a three node cluster's 48 licensed cores, roughly $427,500 of Oracle license paying for storage overhead.
And options multiply the same count: a RAC, Partitioning, Multitenant, Diagnostics and Tuning stack adds about $1.55 million at list on 24 licenses, which is the mechanism that turns a boundary error into an eight figure finding.
Same database, three cluster designs, three bills
| Design | Cores in scope | Processor licenses | EE list | Annual support |
|---|---|---|---|---|
| Oracle VMs in the shared 6 node cluster, 64 cores per node | 384 | 192 | $9,120,000 | $2,006,400 |
| Dedicated 3 node Oracle cluster, 64 cores per node | 192 | 96 | $4,560,000 | $1,003,200 |
| Dedicated 3 node Oracle cluster, 16 cores per node | 48 | 24 | $1,140,000 | $250,800 |
| The same 24 licenses as Named User Plus at the 25 per processor floor | 48 | 600 NUP | $570,000 | $125,400 |
Core density is a licensing decision, not a procurement one. Buying the same 32 core part for an Oracle node that you buy for a general virtualization node is how estates end up at nine figures of accumulated support.
The cheapest Oracle license on Nutanix is the core you never put in the Oracle cluster; everything else is damage control.
Whose document changes your position, and whose does not
| Document | Who wrote it | Contractual weight |
|---|---|---|
| Your ordering document and master agreement | Oracle and you | Binding: the only place a partitioning right can be created |
| The Oracle partitioning policy PDF | Oracle, unilaterally | Policy only, expressly not part of any agreement: predicts the opening claim, does not settle it |
| Nutanix best practice guides | Nutanix | None for Oracle licensing: engineering guidance that makes your defense simple |
| Verbal comfort from an account team | A person who will change roles | None: get it into an amendment or discard it |
The Oracle virtualization licensing brief
The partitioning positions across VMware, Nutanix, and Hyper V: the approved list, the cluster arithmetic, the evidence file, and the containment designs that survive audits.
Get the white paper →The policy cuts both ways, and the CVM cuts only one
The partitioning policy says it is educational and not part of any agreement, and buyers hear only half of what that means.
Oracle cannot hold the policy up as a contract term, so a claim built purely on it is arguable and worth discounting in settlement.
Equally, you cannot hold it up as a shield when it suits you, and both sides end up arguing what the contract's Processor definition means on your hardware, arithmetic that runs on the core factor.
The Controller VM cost cuts one way only: every AHV node runs a CVM owning storage services at 8 to 12 vCPUs, roughly six physical cores of scheduling capacity per node that Oracle counts regardless of who consumes them, nine Processor licenses on a three node cluster.
Paying Oracle for storage overhead.
Size Oracle nodes with the CVM tax in the count.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across Oracle on Nutanix estates, 2024 to 2025
Across roughly 25 to 35 Oracle on Nutanix estates Fredrik Filipsson reviewed in 2024 and 2025, the exposure came from cluster design, not from anything the database team did wrong:
Oracle sitting in mixed workload clusters, the opening claim covering every node in them.
Where the boundary already existed, the count landed 40 to 60 percent below the claim and closed.
The evidence gap was the recurring self inflicted wound: affinity policies that operations could not evidence for the audit window, because nobody exported them before the letter arrived.
The quarterly discipline is an export of cluster membership, VM placement, and policy configuration, dated and filed, the same evidence rhythm the virtualization licensing analysis prescribes for VMware and the Hyper V guide for Microsoft stacks.
And the standing alternative deserves its line: the same 24 licenses bought as Named User Plus, where the population fits the 25 per processor floor, halve the license bill again, the metric decision the license types guide works in full.
Your first five moves
- Build the dedicated Oracle cluster, physically separate, because live migration stops at the cluster boundary and so does the argument.
- Size Oracle nodes on low core count parts: the 16 core node versus the 64 core node is the difference between $1.14M and $4.56M for the same database.
- Count the CVM tax in the design, 8 to 12 vCPUs per node of licensed cores doing storage, and size the cluster accordingly.
- Export the evidence quarterly: cluster membership, placement, and policies, dated and filed before any letter arrives.
- Price the NUP alternative where the population fits, and scope the options stack to the same contained count. The Oracle practice runs the defense with you.
Frequently asked questions
Does Oracle recognize Nutanix AHV as hard partitioning?
No. Oracle's partitioning policy names a short closed list, physical domains, capped Solaris zones, capped IBM partitioning, and Oracle's own hypervisors configured with Oracle's pinning method, and AHV has never appeared on it.
Under the soft partitioning position, the license follows every processor the database could run on.
Doesn't AHV's KVM lineage qualify it?
No: Oracle approved Oracle Linux KVM, a named product running Oracle Linux with Oracle's documented pinning procedure, not KVM as a category. A different vendor's distribution, scheduler, and management plane is a different product, and the lineage argument has never won an audit we have seen.
What does Oracle on a shared Nutanix cluster cost?
The whole cluster: six nodes of dual socket 32 core servers is 384 physical cores, 192 Processor licenses at the 0.5 factor, $9.12 million at Enterprise Edition list plus $2.0 million of annual support, before options.
The same database on a dedicated three node cluster of 16 core servers is 24 licenses and $1.14 million.
Do Nutanix affinity policies contain Oracle licensing?
They shorten the argument without changing the rule: the containment that survives an audit is a physically separate cluster, because live migration does not cross a Nutanix cluster boundary.
Where affinity policies matter is evidence, and 1 in 3 estates could not produce theirs for the audit window because nobody exported them before the letter arrived.
What is the Nutanix Controller VM cost in Oracle licensing?
Every AHV node runs a CVM owning storage services, typically 8 to 12 vCPUs, roughly six physical cores of scheduling capacity that Oracle counts regardless of who consumes them.
On a three node Oracle cluster that is about nine Processor licenses, roughly $427,500 at list, paying Oracle for storage overhead, which is why the CVM belongs in the node sizing.
How do database options change the Nutanix exposure?
They multiply it: options and packs license per Processor on the same count as the database, so a RAC, Partitioning, Multitenant, Diagnostics and Tuning stack adds about $1.55 million at list on a contained 24 license count, and eight figures on an unbounded one.
The boundary decision prices the options estate as much as the database.
