Hyper Converged Infrastructure (HCI/aSV)

Sangfor HCI and aSV provide a unified infrastructure combining compute, storage, networking, and built-in security to simplify deployment, operations, and services.
{{ $t('productDocDetail.guideClickSwitch') }}
{{ $t('productDocDetail.know') }}
{{ $t('productDocDetail.dontRemind') }}
6.11.1R1
Hyper Converged Infrastructure (HCI/aSV) {{ breadTitle }} User Manual Virtual Machine Configuration Guidance Virtual Machine Management Virtual Machine Hot Migration (Supporting Batch Operation)
{{sendMatomoQuery("Hyper Converged Infrastructure (HCI/aSV)","Virtual Machine Hot Migration (Supporting Batch Operation)")}}

Virtual Machine Hot Migration (Supporting Batch Operation)

{{ $t('productDocDetail.updateTime') }}: 2026-01-05

Description

This section instructs the administrator to migrate the virtual machine to other nodes or datastores in the cluster without shutting down.

Precautions

  1. Support node migration and storage migration when the virtual machine is shut down.
  2. Supports bulk migration of VMs and supports setting Concurrent Migration Tasks.

• Max Concurrent Migration Tasks per Datastore: Range: 1-50, default: 1.

• Max Concurrent Migration Tasks per Node: Range: 1-50, default: 2.

  1. During batch migration, the virtual machine's target storage and operation location to be migrated must be consistent. Therefore, it is temporarily impossible to set the storage and operation location separately for each virtual machine.
  2. Before configuring the migration network, ensure that the interface of the source running node and the destination running node must be configured with IP to ensure that the migration network is available. Otherwise, it is grayed out.
  3. During batch migration and datastore migration, the maximum bandwidth link is used by default, there is no migration speed limit, and the setting of migration network and migration speed is not supported.
  4. Only when the virtual machine's datastore is virtual storage can the migration network and migration speed be configured.
  5. VMs with GPUs and raw disk mappings do not support hot migration.
  6. After CPU Throttling is enabled, the IOPS of the VMs will be significantly reduced during the migration.
  7. Shared virtual disks do not support cross-datastore live migration.

Prerequisites

The source and destination node management interfaces to be migrated are operating.

Steps

  1. Select the virtual machine to be migrated in the virtual machine list on the Compute page.

  1. Click More > More > Migrate, and enter the Migrate VM page. Select a Migrate Type, click Next, and specify a destination datastore and a destination node.

 

  1. Click Advanced, configure the Network and Migration Speed, and select Enable compressed transmission and CPU Throttling as needed.

• Network: Automatically identifies the interface bandwidth. When the bandwidths of the management interface, overlay network interface, and storage network interface are inconsistent, the interface with the highest bandwidth is recommended first. When the bandwidths of the interfaces are consistent, they are recommended under the rule of overlay network interface > storage network interface > management interface.

• Migration Speed: Unlimited by default. You can set the maximum speed before or during the hot migration to be at least 10 MB/s and at most the bandwidth of the physical interface of the migration network.

• Enable compressed transmission: If enabled, hot migration will be accelerated but additional CPU resources (up to four threads) may be used.

• CPU Throttling: Recommended to be enabled when the platform is busy or under heavy workloads. If enabled, the CPU performance of VMs will be limited to reduce the data generation speed to ensure efficient VM migration.

  1. Click OK to start the migration, which will take a few minutes to complete.
  2. Go to the Scheduling History page of the VM to view the migration details by chain or by list.