Escaping Rising VMware Costs: Migrating to Oracle Linux KVM
Changes to VMware licensing have pushed many organizations' renewal quotes sharply higher. This paper sets out a low-risk, wave-based path to Oracle Linux KVM with Oracle Linux Virtualization Manager, and explains why it can also lower Oracle Database licensing costs.
1Challenge
Since VMware's acquisition, its licensing has moved to subscription-only bundles priced per core, with minimum core counts and fewer stand-alone products. Many organizations now see renewal quotes far above what they paid before, often for bundled capabilities they don't use.
- Budget shock: hypervisor cost per host has risen sharply, especially for estates with high core-count servers.
- Forced bundling: customers pay for management, networking and storage features they may never deploy.
- Oracle licensing exposure: Oracle treats VMware as soft partitioning, so Oracle Database and Middleware running on vSphere may have to be licensed for every physical core the VM could run on. That can mean every host in the cluster or more.
- Migration fear: teams worry about downtime, unfamiliar tools and losing operational maturity built up over a decade.
2Solution
Oracle Linux KVM, managed through Oracle Linux Virtualization Manager (OLVM), is an enterprise-grade, open-source-based platform with no separate per-core hypervisor license. Support is part of Oracle Linux Premier Support. Oracle also recognizes properly configured KVM CPU pinning as hard partitioning, so Oracle software can be licensed only for the cores assigned to it.
A phased migration framework
Discover & assess
Export VM inventory, resource use, OS versions, storage and network topology. Rank workloads by complexity and business criticality, and find VMware-specific dependencies such as VMware Tools, vSAN, NSX and backup agents.
Design the target platform
Size KVM hosts and OLVM engine HA, choose storage domains (NFS, iSCSI, FC, Gluster), map vSphere port groups to logical networks, and integrate identity, monitoring and backup.
Build & pilot
Stand up the cluster with automation (Ansible), build golden templates, and migrate a pilot wave of low-risk VMs to prove conversion, performance and operating procedures.
Migrate in waves
Convert VMs with OLVM's VMware import or
virt-v2v. Swap guest drivers for VirtIO, validate each VM against agreed checks, and keep the source VM powered off but available for fast rollback.Optimize & license-align
Apply CPU pinning for Oracle workloads to use hard partitioning, consolidate hosts, and retire VMware licenses as clusters empty.
| VMware concept | Oracle Linux KVM / OLVM equivalent |
|---|---|
| vCenter | OLVM engine (web UI, REST API, Ansible modules) |
| ESXi host | Oracle Linux KVM host (UEK kernel) |
| vMotion / DRS / HA | Live migration, scheduling policies, HA VMs |
| Datastore | Storage domain (NFS, iSCSI, FC, Gluster) |
| Port group / vDS | Logical network / VLAN |
| Templates & snapshots | Templates, snapshots, cloning |
3Results
Organizations that follow this approach typically see:
No hypervisor license fees
Per-core hypervisor subscriptions are replaced by Oracle Linux support, often at a much lower cost per host.
Oracle license relief
Hard partitioning limits Oracle Database licensing to pinned cores instead of whole clusters.
Low-disruption cut-over
Wave-based migration with rollback keeps outages within planned maintenance windows.
Automation-ready platform
REST APIs and Ansible modules support infrastructure-as-code operations from the first day.
This white paper is general, educational guidance. Results depend on each organization's environment, contracts and scope. Product names are trademarks of their respective owners and are used for identification only.
Want to apply this to your environment?
We'll review your situation and outline a tailored plan, with no obligation.