This documentation is for a release that is no longer maintained
See documentation for the latest supported version 3 or the latest supported version 4.9.2. 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.
9.2.1. 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
$ oc edit configmap kubevirt-config -n openshift-cnv
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Copy to Clipboard Copied! Toggle word wrap Toggle overflow
9.2.2. Cluster-wide live migration limits and timeouts 复制链接链接已复制到粘贴板!
Parameter | Description | Default |
---|---|---|
| Number of migrations running in parallel in the cluster. | 5 |
| Maximum number of outbound migrations per node. | 2 |
| Bandwidth limit of each migration, in MiB/s. | 64Mi |
|
The migration will be canceled if it has not completed in this time, in seconds per GiB of memory. For example, a virtual machine instance with 6GiB memory will timeout if it has not completed migration in 4800 seconds. If the | 800 |
| The migration will be canceled if memory copy fails to make progress in this time, in seconds. | 150 |