Kubermatic Virtualization VM Migration
Overview
See Kubermatic Virtualization (KubeV) run your virtual machines on your own hardware before you move off your current hypervisor. We install the platform (kube-ovn for networking, KubeVirt for compute) on your hosts, connect it to your VLANs and storage, and migrate two demo VMs, one Ubuntu Server and one Windows Server, from your existing environment.
Goal
Hard evidence that KubeV can replace your current virtualization platform: VM lifecycle, live migration and host-failure recovery proven on your hardware, a documented migration path, and a list of production go-live prerequisites.
Who it is for
Infrastructure and platform teams looking for an alternative to their current hypervisor who want to see migration work before they plan it.
Content
- 01
Design validation and sizing
Topology, VLAN and IP plan, sizing with the KubeV Sizing Tool, and source environment assessment.
- 02
Platform installation
KubeV with a three-node etcd control plane.
- 03
Networking, isolation and storage
VPC, subnets, IPAM, VLAN attachment, isolation rules and live-migration-ready storage.
- 04
VM operations
Lifecycle, live migration and host-failure recovery.
- 05
Migration
Two demo VMs migrated from your source hypervisor.
- 06
Touchdown
Enablement, results and go-live prerequisites.
Typical Activities
- Design validation workshop with your platform and network teams
- Sizing and hardware bill of materials from the KubeV Sizing Tool
- Network mapping from source port groups to platform networks, storage mapping to storage classes
- Disk import and conversion (for example VMDK or VHDX)
- Guest preparation, including virtio drivers and guest agent for Windows
- Live migration of a running VM between hosts and a simulated host failure
- Post-migration validation: boot, reachability, data and test workload
Deliverables
| Area | What you receive |
|---|---|
| Design and sizing | Topology, sizing record, hardware bill of materials, frozen success criteria |
| Platform | HA KubeV installation with Git-managed configuration |
| Networking and storage | Configured networks and isolation, live-migration-ready storage, as-built network docs |
| Migration | Two migrated demo VMs, documented procedure and observed duration per VM |
| Resilience | Live migration and host-failure results |
| Closure | Runbooks, results report, go-live prerequisites |
Prerequisites
- Hypervisor hosts racked and powered, with VT-x or AMD-V enabled
- Host OS installed (Ubuntu 24.04 LTS or agreed alternative)
- Storage backend with ReadWriteMany or Block volume mode
- VLANs trunked to every host, LACP/MLAG and out-of-band management
- IP addressing and firewall rules in place
- VPN or jump host access and a shared Git repository
- Admin access and VM inventory for your source environment
- A project manager plus platform and network counterparts
Why this Accelerator?
- Proof on your hardware and against your current hypervisor.
- Both Linux and Windows guests migrated end to end.
- Resilience you can see: live migration and host failure, tested live.
- A migration baseline: documented procedure and timings to plan the real move.
- No lock-in to the test: your existing environment stays untouched.
What's not included
Production use or SLA, migration of your production VMs, in-guest administration and licensing, physical infrastructure, fabric routing, and decommissioning of the source platform.
Optional extensions
Kubermatic Virtualization VM Migration (Production), further migration waves, KKP on KubeV, KubeLB, GPU or SR-IOV, and managed 24/7 operations.