Contents
Key takeawaysIs AHV hard partitioning?What a Nutanix cluster costsThe Controller VM costContaining the licenseChecking your own exposureWhat we saw in 2024 and 2025What Oracle will sayWhat to do nextFAQOracle treats Nutanix AHV as soft partitioning, so the license covers every core in the cluster an Oracle VM could run on. The cluster design decides whether the same database costs $1.14 million or $9.12 million at list.
- AHV is not on Oracle's list. Oracle's approved hard partitioning list is closed, and neither AHV nor its KVM lineage qualifies, so every core in the cluster counts.
- Shared clusters are expensive. Six dual socket 32 core nodes mean 192 Processor licenses at Enterprise Edition list, eight times the count of a dedicated three node design.
- A dedicated cluster is the containment that holds. The same database on three 16 core nodes needs 24 licenses, and audits we worked settled 40 to 60 percent below the opening claim where such a cluster existed.
- The CVM uses licensed cores. Each node's Controller VM runs at 8 to 12 vCPUs, roughly $427,500 of license on a three node cluster paying for storage services.
- Options follow the same count. A RAC, Partitioning, Multitenant, Diagnostics and Tuning stack adds about $1.55 million on 24 licenses and far more on an unbounded cluster.
- Cross cluster live migration needs watching. Newer AHV releases can move running VMs between clusters, so keep the Oracle cluster out of those pairings.
- Evidence decides the audit. Export cluster membership, VM placement and affinity policies every quarter, before any audit letter arrives.
Is Nutanix AHV an Oracle approved hard partitioning technology?
No. AHV has never appeared on Oracle's approved hard partitioning list, so Oracle treats it as soft partitioning and licenses every core in the cluster the database could run on, whatever size the Oracle VM is. AHV runs production Oracle well. The exposure comes from Oracle's counting rule and from how the cluster around the database is designed.
The 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. VMware, Hyper V, AHV and every other hypervisor fall outside it. For how the approved technologies are set up, see our guide to implementing hard partitioning.
Doesn't AHV's KVM heritage count for anything?
It does not. Oracle approved Oracle Linux KVM, a named product running Oracle Linux and pinned with Oracle's documented procedure. It never approved KVM as a category, and AHV has its own distribution, scheduler and management plane, which makes it a different product.
We have never seen the lineage argument win an audit. Nutanix's pinning and placement guides are sound engineering, and they help you run Oracle well, but no Nutanix document can put AHV on Oracle's list. If you want KVM with hard partitioning, the route is Oracle Linux KVM itself, covered in Oracle licensing on KVM and OLVM.
Which documents actually change your position?
Only your contract. The policy PDF predicts what Oracle will claim in an audit, and everything else is supporting evidence at best.
| 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. It predicts the opening claim and does not settle it |
| Nutanix design and sizing guides | Nutanix | None for Oracle licensing. Engineering guidance that makes your evidence easier to present |
| Verbal comfort from an account team | A person who will change roles | None. Get it into an amendment or discard it |
The policy states that it is educational and not part of any agreement, and buyers usually hear only half of what that means. Oracle cannot enforce it as a contract term, so a claim built purely on the policy is arguable and worth discounting in a settlement. You cannot hold it up as a shield when it suits you either.
In practice both sides end up arguing what the Processor definition in your agreement means on your hardware. That arithmetic runs through the core factor, which is 0.5 per core for the Intel Xeon and AMD EPYC processors inside Nutanix nodes.
How to Prepare for Your Oracle SaaS Negotiation
How much does Oracle on a Nutanix cluster cost?
On a shared cluster you pay for the whole cluster. Six nodes of dual socket 32 core servers hold 384 physical cores, which the 0.5 factor turns into 192 Processor licenses. At the Enterprise Edition list price of $47,500 that is $9.12 million, plus about $2.0 million a year in support, before any options.
The same database on a dedicated three node cluster of 16 core servers needs 24 licenses and $1.14 million. Support in the table is Oracle's standard 22 percent of the license fee, taken from the technology price list.
| 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 |
Why is core density a licensing decision?
Because Oracle multiplies every core you place in the Oracle cluster. The second and third rows run the same database on the same three nodes. Only the processor part differs, and the denser part quadruples the license bill to $4.56 million.
Infrastructure teams tend to standardize on one dense part for every node, since it is cheaper per core for general virtualization. Buying that same 32 core part for Oracle nodes is how a large Oracle footprint builds up nine figures of support over its life. Size Oracle nodes to the measured peak load instead.
Is Named User Plus or Standard Edition 2 cheaper on Nutanix?
Often, when your user population allows it. Enterprise Edition Named User Plus has a floor of 25 users per Processor, so the 24 license cluster needs at least 600 NUP. At $950 each that is $570,000, half the Processor price. The license types guide works through the metric choice in full.
- When NUP fits. You can count every person and device that touches the database, including users behind application servers. Customer facing systems rarely qualify; see NUP counting and minimums.
- When SE2 fits. Standard Edition 2 costs $17,500 per socket on servers with two sockets or fewer, so a dedicated three node dual socket cluster is $105,000 at list. It is capped at 16 CPU threads per database and cannot use Enterprise Edition options or packs, which limits it to smaller databases; see the Standard Edition 2 guide.
How do database options change the Nutanix numbers?
They multiply them. Options and management packs are licensed per Processor on the same count as the database, so the cluster boundary sets their price as well. A common stack of Real Application Clusters, Partitioning, Multitenant, Diagnostics Pack and Tuning Pack lists at $64,500 per Processor.
| Option or pack | Per Processor | Dedicated cluster, 24 licenses | Shared cluster, 192 licenses |
|---|---|---|---|
| Real Application Clusters | $23,000 | $552,000 | $4,416,000 |
| Partitioning | $11,500 | $276,000 | $2,208,000 |
| Multitenant | $17,500 | $420,000 | $3,360,000 |
| Diagnostics Pack | $7,500 | $180,000 | $1,440,000 |
| Tuning Pack | $5,000 | $120,000 | $960,000 |
| Total | $64,500 | $1,548,000 | $12,384,000 |
On the contained count the stack adds about $1.55 million. On the unbounded count it adds more than $12 million, and that is how a boundary error becomes an eight figure audit finding. Confirm which options are actually in use before you price anything, using our options pricing guide and the Diagnostics and Tuning Pack guide.
Oracle Virtualization Licensing Brief
The partitioning rules for VMware, Nutanix and Hyper V, with cluster cost examples and the evidence auditors ask for.
Get the white paper →What does the Nutanix Controller VM cost in Oracle licenses?
About nine Processor licenses on a three node cluster, roughly $427,500 at list. Every AHV node runs a Controller VM (CVM) that owns the storage services, typically at 8 to 12 vCPUs. That is roughly six physical cores of scheduling capacity per node, and Oracle counts those cores regardless of who consumes them.
On the dedicated three node cluster of 16 core servers, the CVMs take about 18 of the 48 licensed cores. You license all 48 and roughly 30 remain for the database. In effect, more than a third of the Oracle bill pays for storage overhead.
How should you size an Oracle node with the CVM in the count?
Say your database needs about 30 physical cores at peak, spread over a three node cluster. A design team that forgets the CVM buys 10 core parts, licenses 30 cores and finds the database short of capacity. The table compares that mistake with two correct designs.
| Design | Licensed cores | Processor licenses | EE list | Cores left after the CVMs |
|---|---|---|---|---|
| Three 10 core nodes, CVM ignored | 30 | 15 | $712,500 | About 12, far short of the need |
| Three 16 core nodes, CVM counted | 48 | 24 | $1,140,000 | About 30, matching the need |
| Four 16 core nodes | 64 | 32 | $1,520,000 | About 40, with headroom |
Each added node brings its own CVM, so extra nodes buy less database capacity than the raw core count suggests. Confirm the CVM size with your Nutanix team before the hardware order goes in.
Can a dedicated cluster or affinity policy contain the Oracle license?
A physically separate Nutanix cluster can, and it is the containment we have seen hold in audits. Affinity policies on their own cannot.
AHV live migrates VMs between nodes inside a cluster, and by default a VM does not move to another cluster, so the licensed boundary and the technical boundary are the same line. The dedicated cluster design guide sets out the equivalent approach on VMware.
Does cross cluster live migration change the boundary?
It can. Current AHV releases support live migration between clusters, either through Nutanix Disaster Recovery with synchronous replication or through On-Demand Cross-Cluster Live Migration in Prism Central, documented from AHV 6.8 onward. Once an Oracle VM can move live to another cluster, expect Oracle to argue that the other cluster's cores are in scope.
Keep the Oracle cluster out of any cross cluster live migration pairing and out of synchronous protection policies shared with general clusters. Write that decision into your evidence file, with the configuration export that shows it.
Why we would not rely on affinity rules to cap the count
A common suggestion from infrastructure teams and some resellers is to tie Oracle VMs to a few licensed hosts with VM to host affinity and license only those hosts. We disagree. An administrator can change affinity in a minute, and Oracle's policy gives it no weight, so the opening claim still covers every node in the cluster.
Affinity still helps as evidence of where the VMs actually ran. But a workload big enough to justify careful affinity design is usually big enough to justify its own cluster, and that is where we would spend the effort.
Affinity rules shorten the argument with Oracle. A separate cluster ends it.
How do you check your Nutanix exposure before Oracle does?
Pull the same data Oracle's auditors will ask for and reconcile it before any letter arrives. Most of it comes from Prism and from the acli command line on a CVM.
- Cluster membership. Run acli host.list on each cluster, or export the host list from Prism, to record which nodes form the cluster that hosts Oracle.
- Physical cores per node. Take socket and core counts from the Prism hardware view or from lscpu on the AHV host. The core factor applies to these physical cores, never to the vCPUs a VM shows.
- VM placement. List every VM running Oracle software, including test, development and standby copies, and the cluster each one sits in.
- Affinity settings. acli vm.get shows a VM's host affinity, and Prism Central lists VM to host affinity policies with the categories they use. Export both.
- Cross cluster paths. Record every protection policy, recovery plan and cross cluster live migration setting that touches the Oracle cluster.
- Options in use. Check DBA_FEATURE_USAGE_STATISTICS in each database so the options count is based on usage, not on what happens to be installed.
Date each export and store it outside Nutanix, every quarter. The virtualization licensing analysis prescribes the same evidence rhythm for VMware, and the Hyper V guide does so for Microsoft stacks. Auditors' view of pinning records is covered in soft partition pinning evidence.
What have we seen in Oracle on Nutanix audits in 2024 and 2025?
Across roughly 25 to 35 Oracle on Nutanix environments I reviewed in 2024 and 2025, the exposure came from cluster design. The database teams had rarely done anything wrong. The cost was set earlier, when someone decided which cluster the Oracle VMs would live in.
- Shared clusters were common. In 30 to 50 percent of the environments, Oracle sat in mixed workload clusters and the opening claim covered every node in them.
- Dedicated clusters settled quickly. Where the boundary already existed, the licensable count landed 40 to 60 percent below Oracle's opening claim, and the argument closed in one meeting.
- Evidence was the recurring gap. About 1 in 3 environments could not show their affinity policies for the audit window, because no one had exported them before the letter arrived.
That last pattern was self inflicted and cheap to prevent. A quarterly export of cluster membership, VM placement and policy configuration is a small job. Rebuilding that history after the letter arrives rarely convinces an auditor. If you are moving off VMware, our VMware to Nutanix migration analysis covers where the Oracle cluster belongs in the plan.
What will Oracle say about Nutanix, and how should you answer?
Expect the audit team to open with the policy and the full cluster count. These are the lines we hear most often on AHV, with replies that keep the discussion on facts.
- "AHV is soft partitioning, so every host in the cluster is licensable." Accept the policy reading for that cluster, then show the membership export proving which hosts form it, and ask Oracle to name any path by which the VMs could reach other hosts.
- "Prism Central manages all your clusters, so all of them are in scope." Prism Central is a management console. Show that no cross cluster live migration or synchronous protection policy links the Oracle cluster to the others.
- "The partitioning policy requires you to license every host." The policy says it is not part of your agreement. Ask Oracle to point to the clause in your ordering document or master agreement that supports the count.
- "Your affinity rules could change at any time." Agree, and rest your position on the cluster boundary, using the affinity history only as supporting evidence.
- "We can close this if you sign a larger agreement." Settle the compliance number on the contained count first, then judge any new purchase on its own merits. Our note on what to do when the audit letter arrives covers the sequence.
- A named licensed environment. Ordering document language that identifies the Oracle cluster by name and node serial numbers, because the contract is the only place a partitioning right can exist.
- Written assurances. Any comfort the account team gives about Nutanix, put into a signed amendment before the renewal closes.
- Option scope. Options and packs listed against the same named cluster, so a later count cannot widen them separately.
Oracle does not grant cluster language often. Ask anyway at renewal or on a new purchase, when your bargaining position is strongest.
What to do next
- Map where Oracle runs. List every Nutanix cluster that hosts an Oracle VM of any kind, with its node and core counts, and price the unbounded count so you know the exposure.
- Build the dedicated Oracle cluster. Make it physically separate, and keep it out of cross cluster live migration and synchronous protection pairings with general clusters.
- Size Oracle nodes on low core count parts. Buy the processor for the database's measured peak, even when the virtualization standard calls for a denser part.
- Count the CVM in the design. Budget each node's Controller VM as licensed cores doing storage work, and size the cluster with that in the model.
- Export the evidence quarterly. Cluster membership, VM placement and policy configuration, dated and filed outside Nutanix before any letter arrives.
- Price the alternatives. Test Named User Plus and Standard Edition 2 where the population and features fit, and scope the options stack to the contained count. The Oracle practice runs the audit defense with you, and the AHV soft partition exposure note goes further on the audit side.
Want a second opinion on your Oracle position? Our Oracle licensing consultants are former Oracle insiders who now work only for buyers.
Frequently asked questions
Does Oracle recognize Nutanix AHV as hard partitioning?
No. AHV has never been on Oracle's approved list, so Oracle applies its soft partitioning rules and licenses every processor the database could run on. Nutanix can document pinning and placement, but only Oracle's own policy or your signed contract can change how Oracle counts.
Doesn't AHV's KVM lineage qualify it?
No. The approval names Oracle Linux KVM running Oracle Linux with Oracle's documented pinning procedure. Sharing ancestry with that product gives AHV no standing, and in the audits we have worked the lineage argument has never reduced a count, so spend the negotiating time on the cluster boundary.
What does Oracle on a shared Nutanix cluster cost?
You license the whole cluster. For six dual socket 32 core nodes, that is 384 cores and 192 Processor licenses, with support near $2.0 million a year at list. Moving the database to three dedicated 16 core nodes cuts the license need to 24 Processors.
Do Nutanix affinity policies contain Oracle licensing?
Not on their own. Affinity shortens the discussion but does not change Oracle's rule, and a physically separate cluster is what survives an audit. The policies still matter as evidence, provided you exported them for the whole audit window rather than trying to reconstruct them afterward.
What is the Nutanix Controller VM cost in Oracle licensing?
Oracle licenses the physical cores the CVM uses, so storage services carry a license cost. On a three node Oracle cluster the CVMs take about 18 cores, which is nine Processor licenses. Build that overhead into node sizing rather than discovering it when the database runs short of capacity.
How do database options change the Nutanix exposure?
Every option and pack is counted on the database's Processor number, so a boundary error is repeated once per option. The five option stack costs $64,500 per Processor at list, which is why an unbounded cluster with a full options stack reaches eight figures.
Can I move Oracle VMs between Nutanix clusters without new licenses?
Only if the target cluster is already licensed. Oracle licenses every host a database runs on or could run on, so live migrating an Oracle VM into a general cluster, even once, gives an auditor grounds to count that cluster as well.