The VMware and ULA Survival Guide

What is inside

A worked field guide to VMware at certification

VMware is the single most expensive misunderstanding in an Oracle ULA exit. Teams assume a cluster boundary limits what Oracle can count. Oracle's position is the opposite, and the gap between those two views is measured in processors. This guide sets out the rule, the architecture that contains it, and the evidence file that makes your number hold.

What the guide covers

• The partitioning stance in plain terms, and why the cluster, not the VM, is the unit Oracle reaches for.
• Where a whole cluster gets swept in, with a worked processor example using core factors.
• The isolation playbook: dedicated clusters, host affinity, and the documentation that supports them.
• The maximization angle, where a broad cluster that genuinely runs Oracle lifts a defensible count.
• A pre certification VMware checklist you can run against your own estate.
• What changes by hypervisor version, and why the answer depends on your specific architecture and contract.

An indicative cluster sweep

Scope claimed	Hosts in scope	Cores	Core factor	Processor licenses
Two VMs you intended to license	2	32	0.5	16
Full cluster Oracle could reach	16	512	0.5	256

The figures are indicative. The point is the multiple: an unisolated cluster can turn a 16 processor expectation into a 256 processor argument. In a defense that is exposure. In a maximization, the same breadth, when the workloads are genuinely yours to count, is value. Which one applies depends on your architecture and your contract wording.

For the wider mechanics, the gated guide sits alongside our pillar, the Oracle ULA certification guide, and pairs with the renewal path in ULA renewal negotiation.