FAQ

This section provides solutions to the common issues you may encounter when using Arcfra Migration Tool. Note that the issues are supplied with common causes, which may not cover all possible ones. In actual practice, it is recommended that you troubleshoot the issue according to the cause step by step first.

What should I do if I fail to add a migration site?

Issue description

On the SITES page, after entering the information about the VMware vCenter or Arcfra cluster and clicking ADD SITE, the page prompts a failure in adding the site.

Possible causes

There may be multiple reasons for the error. You can refer to the following common causes to troubleshoot the issue first.

• The network between Arcfra Migration Tool and the site to be added is disconnected.
• The administrator username or password you entered is incorrect.
• The site to be added has encountered exceptions. For example, the disk space in the Arcfra cluster is full.
• The port 80 or port 443 of the firewall cannot be accessed.

What should I do if migrating a virtual machine during the Windows patch installation fails?

Issue description

For a virtual machine running the Windows operating system, when installing the latest Windows patch set, migrating it from VMware ESXi to AVE fails, and the system prompts that the VirtIO drivers cannot be installed. After mounting the boot disk onto it using IDE, the system freezes during the Booting From Hard Disk process, and the operating system cannot be accessed.

Possible cause

Migrating virtual machines during the Windows patch installation causes the registry reading failure after migration, which results in driver injection failure.

Solution

It is recommended to start the migration task after the Windows patch installation is completed.

What should I do if the virtual machine migration task prompts a failure in injecting virtual machine drivers?

Issue description

When migrating a started virtual machine, the system prompts a failure in driver injection, and the log displays generate initramfs failed!.

Possible cause

During a full data migration, if the disk root directory space on the target site is full, it might cause the failure in injecting virtual machine drivers.

Solution

It is recommended to free up the disk space before starting the migration task, or manually inject the drivers into the target virtual machine.

After migrating a virtual machine running Windows 2003 R2 and rebooting it, I try to connect it to the network, but the system freezes. What should I do?

Issue description

After migrating a virtual machine running Windows 2003 R2 and rebooting it, its virtual console becomes unresponsive. Perform the following operations on the virtual machine, and the system generates the corresponding prompts:

1. Forcibly shut down the virtual machine and unmount all virtual volumes, only keeping the system disk mounted.
2. After rebooting the virtual machine, the virtual console becomes responsive, and the system prompts that new hardware (drive) is detected. Install the driver according to the prompt.
3. After installing the driver and rebooting the system as required, shut down the virtual machine again, and mount the virtual volumes back on it.
4. Reboot the virtual machine. After booting it, there is no network icon in the lower right corner of the page. When trying to connect the virtual machine to the network, the system freezes.
5. Shut down the virtual machine and unmount all virtual volumes. Keep the system disk mounted only.
6. Reboot the virtual machine and configure the network adapter. The system prompts that the IP address you entered for the network adapter has already been allocated to another adapter.

Possible cause

When migrating a virtual machine running Windows 2003, the source virtual machine's configuration cannot be automatically deleted during migration. Consequently, the target virtual machine might contain the network adapter (NIC) configuration from the source site, which conflicts with the NIC configuration on the target site.

Solutions

1. Open the cmd window and run the following command:

   set devmgr_show_nonpresent_devices=1`

2. Continue to run the following command:

   start devmgmt.msc

3. In the Device Manager window, select View > Show hidden devices, click Network adapters, and uninstall the prompted network adapter.

4. Configure the adapter IP address. Once done, mount all virtual volumes back on the virtual machine.

5. Reboot the virtual machine, and check whether the adapter IP address is successfully configured by running ipconfig. If so, connect the virtual machine to the network. The system should run properly.

Why does the available memory of a virtual machine become less after migrating it from VMware ESXi to AVE?

Issue description

After booting the virtual machine migrated from VMware ESXi to AVE, the available memory on the virtual machine becomes less.

Possible cause

Running a virtual machine creates memory overhead. In most cases, running a virtual machine in KVM virtualization requires more memory than in VMware ESXi. Therefore, after booting the target virtual machine, its available memory becomes less.

Solution

If you have specific memory quota requirements, it is recommended to allocate a larger total memory space to the virtual machine than the usual amount.