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.
Phases
- 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
What our engineers and your team work through together.
Design validation workshop
With your platform and network teams
Sizing
Hardware bill of materials from the KubeV Sizing Tool
Network and storage mapping
Source port groups to platform networks, storage to storage classes
Disk import and conversion
For example VMDK or VHDX
Guest preparation
Including virtio drivers and guest agent for Windows
Resilience tests
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 |
|---|---|---|
| 01 | Design and sizing | Topology, sizing record, hardware bill of materials, frozen success criteria |
| 02 | Platform | HA KubeV installation with Git-managed configuration |
| 03 | Networking and storage | Configured networks and isolation, live-migration-ready storage, as-built network docs |
| 04 | Migration | Two migrated demo VMs, documented procedure and observed duration per VM |
| 05 | Resilience | Live migration and host-failure results |
| 06 | Closure | Runbooks, results report, go-live prerequisites |
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.
Prerequisites
What your side provides. We confirm everything together during design validation and sizing.
Infrastructure
- 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
Access & Tooling
- VPN or jump host access
- A shared Git repository
- Admin access and VM inventory for your source environment
People & Goals
- A project manager
- Platform and network counterparts
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.