Chapter 11. Live migration

1. The default value of

   0

   is unlimited.

Procedure

1. In the OpenShift Container Platform console, click Virtualization VirtualMachines from the side menu.

2. You can initiate the migration from this page, which makes it easier to perform actions on multiple virtual machines on the same page, or from the VirtualMachine details page where you can view comprehensive details of the selected virtual machine:

   • Click the Options menu next to the virtual machine and select Migrate.
   • Click the virtual machine name to open the VirtualMachine details page and click Actions Migrate.
3. Click Migrate to migrate the virtual machine to another node.

Procedure

1. Create a

   VirtualMachineInstanceMigration

   configuration file for the virtual machine instance to migrate. For example,

   vmi-migrate.yaml

   :

   apiVersion: kubevirt.io/v1
   kind: VirtualMachineInstanceMigration
   metadata:
     name: migration-job
   spec:
     vmiName: vmi-fedora

2. Create the object in the cluster by running the following command:

   $ oc create -f vmi-migrate.yaml

Procedure

1. Create a

   NetworkAttachmentDefinition

   manifest.

   Example configuration file

   apiVersion: "k8s.cni.cncf.io/v1"
   kind: NetworkAttachmentDefinition
   metadata:
     name: my-secondary-network 

   1

   
     namespace: openshift-cnv 

   2

   
   spec:
     config: '{
       "cniVersion": "0.3.1",
       "name": "migration-bridge",
       "type": "macvlan",
       "master": "eth1", 

   3

   
       "mode": "bridge",
       "ipam": {
         "type": "whereabouts", 

   4

   
         "range": "10.200.5.0/24" 

   5

   
       }
     }'

   1

   The name of the NetworkAttachmentDefinition object.

   2

   The namespace where the NetworkAttachmentDefinition object resides. This must be openshift-cnv.

   3

   The name of the NIC to be used for live migration.

   4

   The name of the CNI plugin that provides the network for this network attachment definition.

   5

   The IP address range for the secondary network. This range must not have any overlap with the IP addresses of the main network.

2. Open the

   HyperConverged

   CR in your default editor by running the following command:

   oc edit hyperconverged kubevirt-hyperconverged -n openshift-cnv

3. Add the name of the

   NetworkAttachmentDefinition

   object to the

   spec.liveMigrationConfig

   stanza of the

   HyperConverged

   CR. For example:

   Example configuration file

   apiVersion: hco.kubevirt.io/v1beta1
   kind: HyperConverged
   metadata:
     name: kubevirt-hyperconverged
   spec:
     liveMigrationConfig:
       completionTimeoutPerGiB: 800
       network: my-secondary-network  

   1

   
       parallelMigrationsPerCluster: 5
       parallelOutboundMigrationsPerNode: 2
       progressTimeout: 150
   ...

   1

   The name of the Multus NetworkAttachmentDefinition object to be used for live migrations.

4. Save your changes and exit the editor. The

   virt-handler

   pods restart and connect to the secondary network.

Procedure

1. In the OpenShift Container Platform console, click Virtualization VirtualMachines from the side menu.
2. Select a virtual machine to open the VirtualMachine details page.

Procedure

1. In the OpenShift Container Platform console, click Virtualization VirtualMachines from the side menu.
2. Click the Options menu beside a virtual machine and select Cancel Migration.

Procedure

1. Add the

   evictionStrategy: LiveMigrate

   option to the

   spec.template.spec

   section in the virtual machine configuration file. This example uses

   oc edit

   to update the relevant snippet of the

   VirtualMachine

   configuration file:

   $ oc edit vm <custom-vm> -n <my-namespace>

   apiVersion: kubevirt.io/v1
   kind: VirtualMachine
   metadata:
     name: custom-vm
   spec:
     template:
       spec:
         evictionStrategy: LiveMigrate
   ...

2. Restart the virtual machine for the update to take effect:

   $ virtctl restart <custom-vm> -n <my-namespace>

Procedure

1. Create a

   MigrationPolicy

   CRD for your specified group of VMIs. The following example YAML configures a group with the labels

   hpc-workloads:true

   ,

   xyz-workloads-type: ""

   ,

   workload-type: db

   , and

   operating-system: ""

   :

   apiVersion: migrations.kubevirt.io/v1alpha1
   kind: MigrationPolicy
   metadata:
     name: my-awesome-policy
   spec:
     # Migration Configuration
     allowAutoConverge: true
     bandwidthPerMigration: 217Ki
     completionTimeoutPerGiB: 23
     allowPostCopy: false
   
     # Matching to VMIs
     selectors:
       namespaceSelector: 

   1

   
         matchLabels:
           hpc-workloads: "True"
           xyz-workloads-type: ""
       virtualMachineInstanceSelector: 

   2

   
         matchLabels:
           workload-type: "db"
           operating-system: ""

   1

   Use namespaceSelector to define a group of VMIs by using namespace labels.

   2

   Use virtualMachineInstanceSelector to define a group of VMIs by using VMI labels.