Life after oVirt / RHV
oVirt powered a lot of serious infrastructure, and Red Hat Virtualization gave it an enterprise home. With RHV discontinued and the project's future quieter than it once was, many estates are choosing their next platform — and would prefer not to land on the same treadmill of per-core subscriptions they just left.
Why oVirt estates find this familiar
SkyVirtHCI follows the same school of design: a management engine over a cluster of hosts, VM-centric administration, live migration, HA, templates and snapshots, storage domains (here: datastores over a built-in replicated pool), and logical networks. The concepts map almost one-to-one; the difference is that storage and networking are part of the product rather than separate infrastructure you must bring.
What you gain in the move
| oVirt / RHV | SkyVirtHCI | |
|---|---|---|
| Storage | External domains (NFS/iSCSI/FC/Gluster) | Built-in replicated pool from local disks; external NFS/block still attachable |
| Data protection | Snapshots; backup via third parties | Incremental backups, immutable copies, DR replication and recovery plans included |
| Lifecycle | Engine + hosts upgraded by hand, in order | Orchestrated rolling upgrades with preflight checks |
| Beyond VMs | VM-focused | Containers and Kubernetes provisioning built in |
| Project risk | Uncertain roadmap | Actively developed product |
The migration is the easy part
The connector speaks to your oVirt engine directly: it authenticates against the engine API, lists every VM, and imports the ones you choose — disk conversion, network mapping and datastore placement handled per VM. No export domains, no intermediate storage to find. The migration guide walks through it.
A sensible exit plan
- Pilot three nodes alongside the oVirt estate.
- Import a first wave of low-risk VMs through the engine connector.
- Validate operations — backup restore, host failure, upgrade — on the pilot.
- Move in waves; keep oVirt running until its last VM is gone.
Common questions
Can SkyVirtHCI import VMs directly from the oVirt engine?
Yes. The migration connector authenticates against the oVirt/RHV engine API, discovers VMs and imports them directly — no export domains needed.
Will oVirt concepts map to SkyVirtHCI?
Closely. Clusters, hosts, templates, snapshots, logical networks and storage domains all have direct equivalents; the main difference is that resilient storage and SDN are built into the product.
Does SkyVirtHCI use per-core subscription licensing like RHV did?
No. There is no per-core metering; the platform ships complete, without feature editions.