Nutanix and IBM sub-capacity eligibility.

Eligible technology is only the first gate

IBM publishes which virtualization technologies qualify for sub-capacity licensing, and the Nutanix AHV hypervisor sits among the supported environments. Running on an eligible technology matters because the alternative, running on something IBM treats as ineligible, voids sub-capacity outright and defaults the count to the full physical capacity of the host. So clearing the eligibility gate is necessary. It is just not sufficient.

The conditions that apply everywhere apply on Nutanix too. Sub-capacity requires ILMT, or an approved tool such as Flexera One ITAM or HCL BigFix Inventory, deployed within 90 days of first eligible deployment, running continuously, with quarterly reports retained for two years. Miss any of these and IBM defaults to full-capacity charging regardless of how supported the hypervisor is. Eligibility opens the door; the measurement discipline keeps you through it.

Where Nutanix estates run into trouble

• ILMT does not see the AHV topology correctly. If the tool cannot resolve which virtual cores a VM occupies on the cluster, the sub-capacity figure it reports may be wrong in either direction, and a wrong figure is a contestable figure under audit.
• VM mobility across the cluster. Workloads that move between nodes need continuous measurement so the peak core consumption is captured. A snapshot view can understate or, worse, leave gaps an auditor reads as full capacity.
• Mixed clusters. Where AHV nodes coexist with other hypervisors or bare metal, the boundary of what is eligible and how it is counted gets blurred, and inventory has to keep the distinction clean.
• Agent coverage gaps. A broken or missing ILMT agent on any node voids the sub-capacity claim for that period, the same silent exposure that affects every platform.

Defending a Nutanix sub-capacity position

The defense begins by confirming eligibility on the record, then proving continuous, accurate measurement of the virtual cores the IBM software actually used across the cluster. Because the count follows the virtual cores rather than the physical Nutanix hardware, a clean ILMT history can be the difference between licensing a handful of cores and being charged for an entire node. Where the data has gaps, the work is to reconstruct the defensible position and challenge any full-capacity assumption the auditor has applied to an eligible, well instrumented environment.