Live migration limits and timeouts - Live migration | OpenShift Virtualization

Configuring live migration limits and timeouts
Cluster-wide live migration limits and timeouts

Live migration limits and timeouts are applied so that migration processes do not overwhelm the cluster. Configure these settings by editing the kubevirt-config configuration file.

Configuring live migration limits and timeouts

Configure live migration limits and timeouts for the cluster by adding updated key:value fields to the kubevirt-config configuration file, which is located in the openshift-cnv namespace.

Procedure

Edit the kubevirt-config configuration file and add the necessary live migration parameters. The following example shows the default values:

$ oc edit configmap kubevirt-config -n openshift-cnv

Example configuration file

apiVersion: v1
data:
  default-network-interface: masquerade
  feature-gates: DataVolumes,SRIOV,LiveMigration,CPUManager,CPUNodeDiscovery,Sidecar,Snapshot
  migrations: |-
    parallelMigrationsPerCluster: "5"
    parallelOutboundMigrationsPerNode: "2"
    bandwidthPerMigration: "64Mi"
    completionTimeoutPerGiB: "800"
    progressTimeout: "150"
  machine-type: pc-q35-rhel8.3.0
  selinuxLauncherType: virt_launcher.process
  smbios: |-
    Family: Red Hat
    Product: Container-native virtualization
    Manufacturer: Red Hat
    Sku: 2.6.0
    Version: 2.6.0
kind: configmap
metadata:
  creationTimestamp: "2021-03-26T18:01:04Z"
  labels:
    app: kubevirt-hyperconverged
  name: kubevirt-config
  namespace: openshift-cnv
  resourceVersion: "15371295"
  selfLink: /api/v1/namespaces/openshift-cnv/configmaps/kubevirt-config
  uid: <uuid>

Cluster-wide live migration limits and timeouts

Migration parameters
Parameter	Description	Default
`parallelMigrationsPerCluster`	Number of migrations running in parallel in the cluster.	5
`parallelOutboundMigrationsPerNode`	Maximum number of outbound migrations per node.	2
`bandwidthPerMigration`	Bandwidth limit of each migration, in MiB/s.	64Mi
`completionTimeoutPerGiB`	The migration is canceled if it has not completed in this time, in seconds per GiB of memory. For example, a virtual machine instance with 6GiB memory times out if it has not completed migration in 4800 seconds. If the `Migration Method` is `BlockMigration`, the size of the migrating disks is included in the calculation.	800
`progressTimeout`	The migration is canceled if memory copy fails to make progress in this time, in seconds.	150