Free tool · parsed in your browser
VMware to KubeVirt Readiness Report
Upload an RVTools export or describe your VMs. The report scores every VM for a move to a KubeVirt-based platform such as OpenShift Virtualization, Harvester or Kubermatic, sorts them into Ready, Ready with changes and Keep as VM for now, lists the platforms with their Ledger scores, sizes the cluster and sequences the move in four phases.
Parsed in your browser. VM names are hashed before anything is sent; hostnames, IPs, folders, notes and the file never leave your computer. The server gets counts, sizes, OS families, flags and hashed ids. Free, three written plans per day.
How the report is built
1. The file stays with you
The RVTools workbook is read in your browser: vInfo, vDisk, vUSB, vSnapshot, vTools and vHost. Names become SHA-256 hashes; hostnames, IPs, folders and notes are dropped.
2. Each VM is scored in code
100 minus a named deduction for every condition the KubeVirt user guide, OpenShift Virtualization, Migration Toolkit for Virtualization or Harvester documentation covers. 80 and above is Ready, 50 to 79 is Ready with changes, under 50 or a guest past vendor support is Keep as VM for now.
3. Platforms come from the Ledger
The On-Prem Kubernetes Ledger scores 20 distributions from public records. This page lists the ones whose record names a KubeVirt product, with the Ledger Index, licence model and what you add on top.
4. The plan is written from the numbers
Our engine turns the anonymised summary into a short summary, the change per deduction, the reason the keep group stays, four phases, five risks and three next steps. It never computes a number.
Go deeper
- On-Prem Kubernetes Ledger: every distribution scored, year by year.
- OpenShift vs VMware and the Kubernetes distributions report.
- Velero backup for Kubernetes: protect the VMs once they run as pods.
- VMware Exit Planner: the same RVTools file, costed across every exit route.
- Infrastructure Fact Checker and the tools page.
Frequently asked questions
Which VMs can move from VMware to KubeVirt?
Most Linux and current Windows Server guests with plain virtual disks and one or two NICs move with little change. VMs with PCI or GPU passthrough, RDM or shared disks, USB devices, guests past vendor support or pending snapshots score lower. Each deduction links to the KubeVirt, OpenShift Virtualization or Harvester page that documents the limit.
What leaves my browser when I upload an RVTools file?
The file is parsed on your computer. VM names are replaced by a SHA-256 hash before anything is sent. Hostnames, IP addresses, folders, annotations and the file itself never leave the browser. The server receives counts, sizes, OS families, feature flags and the hashed ids, and saves that summary with the report behind the share link.
How is the node count calculated?
From the total vCPU and RAM of the VMs in scope, divided by the usable capacity of one node after the system reserve, at the overcommit ratio you set, plus the spare nodes and control plane nodes you set. Storage is the provisioned disk plus headroom, multiplied by the replication factor. Every assumption is an editable field and recomputes in the page.