ZStack Cloud Documentation
All
All
ZStack Cloud 4.4.0>Tutorials>Advanced Features>V2V Migration Tutorial>V2V Migration
Get PDF

V2V Migration

Currently, you can migrate VM instances from a VMware cloud platform or a KVM cloud platform to the current cloud. Before you use the Migration Service, note the following considerations.

VMware Source Platform Considerations

If the source cloud platform is VMware, note the following:
  • Before migrations, perform data synchronization to manually synchronize the latest status of resources in the vCenter that you took over.
  • You can perform bulk V2V migrations for VM instances, and customize configurations of the migrated VM instances.
  • The supported vCenter versions include 5.0, 5.1, 5.5, 6.0, 6.5, 6.7, and 7.0. Note that the version of the vCenter server must be consistent with that of the ESXi host.
  • The supported VM systems of the source vCenter include RHEL/CentOS 4.x, 5.x, 6.x, 7.x, SLES 11, 12, 15, Ubuntu 12, 14, 16, 18, Windows 7, and Windows Server 2003 R2, 2008 R2, 2012 R2, 2016, 2019.
  • The VM instances will be forced to shut down during the V2V migration. Therefore, pay attention to the business impact.
    Note: The system firstly attempts to shut down the VM instances gently. If the shutdown fails, the system will perform force shutdown.
  • The type of the source primary storage is not enforced. The type of the destination primary storage can be LocalStorage, NFS, Ceph, or SharedBlock.
  • For Windows VM instances, the Windows VirtIO driver is automatically installed during the migration. This improves the NIC and disk efficiencies.
  • You can perform V2V migration for VM instances booted by UEFI. After the migration, these VM instances are also booted by UEFI.

KVM Source Platform Considerations

If the source cloud platform is KVM, note the following:
  • You can perform bulk V2V migrations for VM instances, and customize configurations of the migrated VM instances.
  • You can migrate the VM instances that are running or paused. Do not power off the VM instances to be migrated.
  • You can perform V2V migrations for VM instances booted by UEFI. After the migration, these VM instances are also booted by UEFI.
  • The type of the source primary storage is not enforced. The type of the destination primary storage can be LocalStorage, NFS, Ceph, or SharedBlock.
  • For different types of source primary storages or destination primary storages, the libvirt version and QEMU version must meet the following requirements:
    • If either the source primary storage or destination primary storage is Ceph, use libvirt 1.2.16 and QEMU 1.1 or their later versions.
    • If neither the source primary storage nor destination primary storage is Ceph, use libvirt 1.2.9 and QEMU 1.1 or their later versions.

Source Cloud Platform: VMware

This topic describes VMware-based V2V jobs from the following perspectives:

Create a V2V Job

To create a V2V job based on the VMware platform, follow these five steps:
  1. Configure the source resources.
    Set the following parameters:
    • Name: Enter a name for the V2V job.

      The V2V job name must be 1 to 128 characters in length and can contain Chinese characters, letters, digits, hyphens (-), underscores (_), periods (.), parenthesis (), colons (:), and plus signs (+).

    • Description: Optional. Enter a description for the V2V job.
    • Source Platform: Select the source platform type. Here, select VMware.
    • V2V Conversion Host: Select a V2V conversion host.
      Note:
      • Before you can create a V2V job, add a V2V conversion host to the Cloud.
      • The type of the V2V conversion host must be consistent with that of the source cloud platform.
      • The V2V conversion host is a host in the specified destination cluster. Make sure that the hardware resources are sufficient for V2V migration.
      • If you select multiple source VM instances, note that the V2V jobs created accordingly will share the same V2V conversion host.
    • Source Cluster: Select a cluster from the vCenter that you took over as the source cluster.
    • Source VM: Select one or more vCenter VM instances from the source cluster as the source VM instance or VM instances. You can select up to 50 VM instances at a time.
      Note:
      • If you select more than one VM instance, corresponding V2V jobs will be created in bulk. Note that one V2V job corresponds to one source VM instance.
      • For Windows Server 2012 R2 and Windows Server 2016 VM instances, you need to manually disable the hibernation feature and shut down these VM instances before you create V2V jobs.
        To disable or enable the Windows hibernation feature, run the following commands:
        • Disable Windows hibernation: cmd-->“powercfg -h off”
        • Enable Windows hibernation: cmd-->“powercfg -h on”
      • If one of the source VM instances has a data volume, make sure that the disk mode of the data volume is Dependent. Otherwise, the V2V job might fail.
    Figure 1. Configure Source Resources


  2. Configure the destination resources.
    Set the following parameters:
    • Destination Zone: By default, the current zone is displayed.
    • Destination Cluster: Select a destination cluster. Then, the estimated CPU usage and memory usage are displayed.
      • Estimated CPU usage: displays the number of the used CPUs of the source VM instance and the total number of available CPUs in the destination cluster.
      • Estimated memory usage: displays the used memory size of the source VM instance and the total available memory size in the destination cluster.
    • Destination Primary Storage: Select a destination primary storage. Then, the estimated primary storage usage is displayed.
      • Estimated storage usage: displays the used storage of the source VM instance and the total available storage of the destination primary storage.
    • Compression mode: Choose whether to enable the compression mode. By default, the compression mode is enabled.
      Note:
      • Enabling the compression mode compresses the caches of the migration data and improves the cache space utilization of the V2V conversion host.
      • If the destination primary storage is Ceph, we recommend that you do not use the compression mode.
    Figure 2. Configure Destination Resources


  3. Configure the network mapping.
    In this step, consider the following:
    • The source VM instance has a NIC attached.
    • The source VM instance does not have a NIC attached.
    1. If the source VM instance has a NIC attached,
      Set the following parameters:
      • Destination Network: Select a destination network as needed. The destination network is the network attached to the specified destination cluster.
    2. If the source VM instance does not have a NIC attached, go to the next step to manually configure the destination NIC.
    Figure 3. Configure Network Mapping


  4. Configure the destination VM instance.
    In this step, consider the following:
    • The VM instance has a NIC attached.
    • The VM instance does not have a NIC attached.
    1. If the VM instance has a NIC attached,
      configure the destination VM instance by setting the following parameters:
      • Start VM After Migration: Choose whether to automatically start the destination VM instance after the migration.
      • Use Source MAC and IP: Choose whether to use the source MAC and IP addresses. By default, these addresses are not used.
        Note:
        • If not used, you can customize the MAC and IP addresses for the destination NIC. If you do configure them, the destination MAC address will be the same as the source MAC address after migration, and the IP address of the destination NIC will be allocated by the system.
        • If used, the destination NIC will use the MAC and IP addresses of the source NIC in the next step. If the source NIC does not have an IP address, the IP address of the destination NIC will be allocated by the system.
      • VM Configuration: Select the VM instance to be configured. You can configure the VM instance by setting the following parameters:
        • Name: Set the name of the destination VM instance.
        • NIC: Configure the NIC information.
          • Network: Select the network for the destination VM instance.
          • IP Address: Optional. Configure the IP address of the destination NIC.
            Note: If not configured, the IP address of the destination NIC will be allocated by the system.
          • MAC Address: Optional. Configure the MAC address of the destination NIC.
            Note: If not configured, the MAC address of the destination NIC will be the same as that of the source NIC after migration.
      • Boot Partition: If the VM instance to be migrated has multiple boot partitions, specify one as the root volume for the VM instance.
      Note:
      • Go to the next step if no further modification is needed.
      • Before you migrate a VM instance to the current cloud, make sure that the VM instance has at least one NIC attached.
    2. If the VM instance does not have a NIC attached,
      configure the destination VM instance by setting the following parameters:
      • Start VM After Migration: Choose whether to automatically start the destination VM instance after the migration.
      • VM Configuration: Select the VM instance to be configured. You can configure the VM instance by setting the following parameters:
        • Name: Set the name of the destination VM instance.
        • NIC: Configure the NIC information.
          • Network: Select the network for the destination VM instance.
          • IP Address: Optional. Configure the IP address of the destination NIC.
          • Note: If not configured, the IP address of the destination NIC will be allocated by the system.
          • MAC Address: Optional. Configure the MAC address of the destination NIC.
            Note: If not configured, the MAC address of the destination NIC will be the same as that of the source NIC after migration.
        • Boot Partition: If the VM instance to be migrated has multiple boot partitions, specify one as the root volume for the VM instance.
      Note: Before you migrate a VM instance to the current cloud, make sure that the VM instance has at least one NIC attached.
    Figure 4. Configure Destination VM


  5. Confirm and submit.
    Figure 5. Confirm and Submit


Manage a V2V Job

On the main menu of ZStack Cloud, choose Platform O&M > Migration Service > V2V Migration. Then, the V2V Migration page is displayed.

The following table lists the actions that you can perform on a V2V job.
Action Description
Reboot V2V Job Reboot a V2V job if the job failed.
Note:
  • If migration data caches exist, rebooting the V2V job can improve the migration efficiency.
  • You can set the period for retaining the migration data caches in the global setting.
Edit V2V Job Modify the name and description of a V2V job.
Delete V2V Job Delete a V2V job after migration.

V2V Job Details

On the V2V Migration page, click on the name of a V2V job. Then, the details page of the V2V job is displayed. On the details page, you can view the V2V job status and the basic information about the source VM instance and destination VM instance.

Figure 6. V2V Job Details



Source Cloud Platform: KVM

This topic describes KVM-based V2V jobs from the following perspectives:

Create a V2V Job

To create a V2V job based on the KVM platform, follow these five steps:
  1. Configure the source resources.
    Set the following parameters;
    • Name: Enter a name for the V2V job.
    • Description: Optional. Enter a description for the V2V job.
    • Source Platform: Select KVM.
    • V2V Conversion Host: Specify a V2V conversion host.
      Note:
      • Before you can create a V2V job, add a V2V conversion host to the Cloud.
      • The type of the V2V conversion host must be consistent with that of the source cloud platform.
      • The V2V conversion host is a host in the specified destination cluster. Make sure that the hardware resources are sufficient for V2V migration.
      • If you select multiple source VM instances, note that the V2V jobs created accordingly will share the same V2V conversion host.
    • Source Host IP: Enter the IP address of the source host.
    • Source Host SSH Port: Set the SSH port of the source host. Default: 22.
    • SSH Username: Enter the username. Default: root.
    • SSH Password:
      • If you select Password, enter the SSH password. You can log in to the source host through the SSH password authentication.
      • If you select PrivKey, enter the corresponding SSH private key. You can log in to the source host through the SSH private key authentication.
        Note: Before you select this option, create an SSH private key for the source host in advance.
    • Virsh Info:
      • By default, this checkbox is not selected, indicating that the virtual resources of the source host are not remotely accessed through virsh.
      • If selected, you need to enter the SASL Username and SASL Password when the remote libvirtd requires Simple Authentication and Security Layer (SASL) authentication. You can securely connect to the remote libvirtd only after passing the verification.
        • SASL Username: Enter the corresponding SASL username.
        • SASL Password: Enter the corresponding SASL password.
    • Get Source VM Info: Obtain information about the running or paused VM instances that are available for migration.
    • Source VM: Select one or more KVM VM instances from the source host.
      Note:
      • You can select up to 50 VM instances at a time.
      • Do not power off the VM instances to be migrated.
      • If you select more than one VM instance, corresponding V2V jobs will be created in bulk. Note that one V2V job corresponds to one source VM instance.
    • Pause Running VM:
      • By default, this checkbox is not selected, indicating that the VM instances continue to run during the migration. This ensures the business continuity of the source VM instances.
      • If selected, the source VM instances will be paused when the migration starts, and the data written to the disk at that time will be migrated. After the migration is completed, you need to manually start the paused source VM instances.
      Note: For VM instances with high I/O, we recommend that you pause them before migration to ensure the data integrity.
    Figure 1. Configure Source Resources


  2. Configure the destination resources.
    Set the following parameters:
    • Destination Zone: By default, the current zone is displayed.
    • Destination Cluster: Select a destination cluster. Then, the estimated CPU usage and memory usage are displayed.
      • Estimated CPU usage: displays the number of the used CPUs of the source VM instance and the total number of available CPUs in the destination cluster.
      • Estimated memory usage: displays the used memory size of the source VM instance and the total available memory size in the destination cluster.
    • Destination Primary Storage: Select a destination primary storage. Then, the estimated primary storage usage is displayed.
      • Estimated storage usage: displays the used storage of the source VM instance and the total available storage of the destination primary storage.
    • Compression mode: Choose whether to enable the compression mode. By default, the compression mode is enabled.
      Note:
      • Enabling the compression mode compresses the caches of the migration data and improves the cache space utilization of the V2V conversion host.
      • If the destination primary storage is Ceph, we recommend that you do not use the compression mode.
    Figure 2. Configure Destination Resources


  3. Configure the network mapping.
    In this step, consider the following:
    • The source VM instance has a NIC attached.
    • The source VM instance does not have a NIC attached.
    1. If the source VM instance has a NIC attached,
      Set the following parameters:
      • Destination Network: Select a destination network as needed. The destination network is the network attached to the specified destination cluster.
    2. If the source VM instance does not have a NIC attached, go to the next step to manually configure the destination NIC.
    Figure 3. Configure Network Mapping


  4. Configure the destination VM instance.
    In this step, consider the following:
    • The VM instance has a NIC attached.
    • The VM instance does not have a NIC attached.
    1. If the source VM instance does not have a NIC attached,
      configure the destination VM instance by setting the following parameters:
      • Start VM After Migration: Choose whether to automatically start the destination VM instance after the migration.
      • VM Configuration: Select the VM instance to be configured. You can configure the VM instance by setting the following parameters.
        • Name: Set the name of the destination VM instance.
        • NIC: Configure the NIC information.
          • Network: Select the network for the destination VM instance.
          • IP Address: Optional. Configure the IP address of the destination NIC.
            Note: If not configured, the IP address of the destination NIC will be allocated by the system.
          • MAC Address: Optional. Configure the MAC address of the destination NIC.
            Note: If not configured, the MAC address of the destination NIC will be the same as that of the source NIC after migration.
      Note:
      • Go to the next step if no further modification is needed.
      • Before you migrate a VM instance to the current cloud, make sure that the VM instance has at least one NIC attached.
    2. If the VM instance has a NIC attached,
      configure the destination VM instance by setting the following parameters:
      • Start VM After Migration: Choose whether to automatically start the destination VM instance after the migration.
      • VM Configuration: Select the VM instance to be configured. You can configure the VM instance by setting the following parameters:
        • Name: Set the name of the destination VM instance.
        • CPU: Set the number of CPU cores for the destination VM instance. The number must be an integer ranging from 1 to 1024.
        • Memory: 16MB~100TB。: Set the memory size for the destination VM instance. The memory must be an integer ranging from 16 MB to 100 TB.
        • Platform: Select the image platform type.
          The image platform determines the platform used for creating VM instances. You can set whether to use KVM VirtIO drivers (including disk drivers and NIC drivers).
          • Linux: If VirtIO is enabled, the image operating system (OS) will have a VirtIO driver attached. If VirtIO is disabled, the OS, such as RHEL 5.8, will use a QEMU device instead.
          • Windows: If VirtIO is enabled, the image OS will have a VirtIO driver attached. If VirtIO is disabled, the OS will use a QEMU device instead.
          • Other: If VirtIO is enabled, the image OS will have a VirtIO driver attached. If VirtIO is disabled, the OS will use a QEMU device instead. This type of platform is compatible with some operating systems of earlier versions that do not support VirtIO drivers.
        • VirtIO: Choose whether to enable VirtIO based on your operating system and platform.
        • Volume: Select the volume to be migrated and set a name for the volume.
        • NIC: Configure the destination NIC information by setting the following parameters:
          • Network: Select the network for the destination VM instance.
          • Specify IP: Optional. Configure the IP address for the destination NIC.
            Note: If not configured, the IP address of the destination NIC will be allocated by the system.
          • MAC Address: Optional. Configure the MAC address for the destination NIC.
            Note: If not configured, the MAC address of the destination NIC will the same as that of the source NIC.
      Note: Before you migrate a VM instance to the current cloud, make sure that the VM instance has at least one NIC attached.
    Figure 4. Configure Destination VM


  5. Confirm and Submit.
    Figure 5. Confirm and Submit


Manage a V2V Job

On the main menu of ZStack Cloud, choose Platform O&M > Migration Service > V2V Migration. Then, the V2V Migration page is displayed.

The following table lists the actions that you can perform on a V2V job.
Action Description
Reboot V2V Job Reboot a V2V job if the job failed.
Note:
  • If migration data caches exist, rebooting the V2V job can improve the migration efficiency.
  • You can set the period for retaining the migration data caches in the global setting.
Edit V2V Job Modify the name and description of a V2V job.
Delete V2V Job Delete a V2V job after migration.

V2V Job Details

On the V2V Migration page, click on the name of a V2V job. Then, the details page of the V2V job is displayed. On the details page, you can view the V2V job status and the basic information about the source VM instance and destination VM instance.

Figure 6. V2V Job Details


Download

Already filled the basic info? Click here.

Enter at least 2 characters.
Invalid mobile number.
Enter at least 4 characters.
Invalid email address.
Wrong code. Try again. Send Code Resend Code (60s)

An email with a verification code will be sent to you. Make sure the address you provided is valid and correct.

Download

Not filled the basic info yet? Click here.

Invalid email address or mobile number.

Email Us

contact@zstack.io
ZStack certification training consulting
Enter at least 2 characters.
Invalid mobile number.
Enter at least 4 characters.
Invalid email address.
Wrong code. Try again. Send Code Resend Code (60s)

Email Us

contact@zstack.io

The download link is sent to your email address.

If you don't see it, check your spam folder, subscription folder, or AD folder. After receiving the email, click the URL to download the documentation.

The download link is sent to your email address.

If you don't see it, check your spam folder, subscription folder, or AD folder.
Or click on the URL below. (For Internet Explorer, right-click the URL and save it.)

Thank you for using ZStack products and services.

Submit successfully.

We'll connect soon.

Thank you for choosing ZStack products and services.

English

© 2021, Shanghai Yunzhou Information and Technology Ltd. All Rights Reserved.

Back to Top