For Windows and Linux guest VMs, you must install the required drivers to the source VMs and then perform a new replication operation.
You can make the following changes to source VMs before performing the replication operation. When performing replication operation for an Active Directory domain controller, upgrade the PV drivers as described in Upgrade a Domain Controller (AWS PV Upgrade).
VM's having GPT Data volumes with BIOS firmware (Legacy Mode) are supported.
-
Windows source VMs:
-
Configure your host firewall (Windows firewall or similar) to allow access to RDP and Network discovery. Otherwise, you cannot access your instance after the conversion is complete.
-
Enable Remote Desktop Protocol (RDP).
-
Ensure that there is a minimum of 2 GB free space on the C: drive.
-
EBS Direct replication is not supported if the boot OS for the source VM uses GUID Partition Table (GPT) partitioning. Use the import method instead.
-
-
Linux source VMs:
-
Linux VM's must use the old network interface naming, such as eth0, instead of ens192, or enp1s0 etc. See Ethernet Naming Conventions for RHEL, CentOS, Oracle Linux, and Suse Linux.
-
Enable Secure Shell (SSH) for remote access.
-
The host firewall (such as Linux iptables) must permit access to SSH.
-
Ensure that Linux VMs use GRUB (GRUB legacy) or GRUB 2 as the bootloader.
-
Linux VMs must use one of the following for the root file system: ext2, ext3, ext4, Btrfs, JFS, or XFS.
-
Linux VM /etc/fstab entries should use UUIDs instead of device names, because device names might change during replication.
-