Ensure that your Microsoft Hyper-V environment meets the following prerequisites for migration to Hyper-V:
Use PlateSpin Migrate Client or PlateSpin Migrate Web Interface to migrate workloads to Hyper-V targets. See Table 2-14, Supported Target Hyper-V Platforms for the Migrate Web Interface and Migrate Client.
NOTE:For automated migration of workloads to Hyper-V using the PlateSpin Migrate Web Interface, only Windows workloads are supported. To migrate Linux workloads to Hyper-V hosts, use the PlateSpin Migrate Client.
You can use Hyper-V as the target virtualization platform in fully automated workload virtualization. You can use VMs in Hyper-V as targets for semi-automated (X2P) migrations.
Your source workload must be supported by PlateSpin Migrate and Hyper-V.
See Microsoft Windows Server with Hyper-V
in Table 2-14, Supported Target Hyper-V Platforms for the Migrate Web Interface and Migrate Client.
For semi-automated (X2P) migrations to VMs on Hyper-V, see also Section 24.0, Prerequisites for Semi-Automated (X2P) Migrations.
Your network environment must meet the requirements for access, discovery, and migration described in Access and Communication Requirements across Your Migration Network.
For Hyper-V target VMs with synthetic adapters, you cannot set an MTU value that is less than 1500.
For semi-automated migrations, ensure that you configure volumes on the target disks with about 50 MB of additional storage space than the source disks.
For target VMs with dynamic memory, disable the dynamic memory on the Hyper-V VM before you begin the X2P workflow. You can enable the dynamic memory on the Hyper-V VM post the migration.
Ensure that Hyper-V Integration Services are properly configured so that the Integration Services driver is automatically installed or updated on the Windows guest VMs during Windows updates. For Linux guest VMs, use a package manager to install or update Hyper-V Integration Services for Linux. They are built-in for Linux distributions, but there might be optional updates available. See Manage Hyper-V Integration Services on the Microsoft documentation website.
PlateSpin Migrate Client uses the C:\Windows\system32\vmguest.iso file on the Hyper-V host to install the Hyper-V Integration Services driver on the guest VM during migration. However, Windows Server 2016 Hyper-V does not include the C:\Windows\system32\vmguest.iso file because Hyper-V 2016 uses a different method to manage the driver for its guest VMs. Do one of the following to ensure that the Hyper-V Integration Services driver is installed on guest VMs on your Windows Server 2016 Hyper-V host:
Enable Migrate to install a Hyper-V Integration Services driver during the migration. Before you begin migrations to the Hyper-V 2016 host, copy the C:\Windows\system32\vmguest.iso file from a Windows Server 2012 R2 Hyper-V host to the same location on your Windows Server 2016 Hyper-V host.
After the migration, manually install the Hyper-V Integration Services driver on the guest VM. Use Windows Update on the Windows guest VM to add the Hyper-V Integration Services driver, or use alternative Microsoft installation methods as appropriate. For Linux guest VMs, use a package manager to install Integration Services for Linux that are built-in for the Linux distribution.See Manage Hyper-V Integration Services on the Microsoft documentation website.
For information about configuring the migration, see Migration to Microsoft Hyper-V.