Difficulty: beginner
Estimated Time: 15min

Live Migration is a common virtualization feature supported by KubeVirt where virtual machines running on one cluster node move to another cluster node without shutting down the guest OS or its applications.

This scenario demonstrates how to migrate a VM from one node to another in a KubeVirt cluster.

For more information, see the KubeVirt Project's Live Migration Lab

Well done, you have completed the KubeVirt demo!

We hope you enjoyed it, for more information about KubeVirt, please do check https://kubevirt.io!

Live Migration in KubeVirt

Step 1 of 2

Create a VM and set up a service.

Wait for KubeVirt to deploy

The setup for this scenario includes installation of KubeVirt and the virtctl utility.

Before we can start, we need to wait for the Kubernetes cluster and KubeVirt initialization script to run. (a command prompt will appear once everything is ready).

Check the kubevirt-config

When KubeVirt finishes deploying, list out the KubeVirt Custom Resource "kubevirt" in the "kubevirt" namespace.

In addition to emulated virtualization (a requirement in this environment), a feature gate has also been added to make live migration possible.

kubectl -n kubevirt get kubevirt kubevirt -o yaml

Launch the test VM

This scenario will use the same VirtualMachine YAML definition from the first lab. Run the following code to create the VM.

kubectl apply -f https://kubevirt.io/labs/manifests/vm.yaml

Run the following to start the VM.

virtctl start testvm

The testvm virtual machine should start running on node01. Check which node the VM is on with:

kubectl get vmi

Once the VM reaches the Running phase, you should see something like:

NAME     AGE   PHASE     IP           NODENAME
testvm   17s   Running   10.244.1.7   node01

For more detailed information, you can also view the virt-launcher Pod(s) with:

kubectl get pods -o wide

NAME                         READY   STATUS    RESTARTS   AGE   IP           NODE     NOMINATED NODE   READINESS GATES
virt-launcher-testvm-676tr   2/2     Running   0          80s   10.244.1.7   node01   <none>           <none>

Make note of the VM's node, and move ahead to the next step.