Limitations

Trilio uses a widely used tool virt-v2v for migration which is one of the open-source tools by Red Hat. The below-mentioned limitations are from this tool and thus a limitation for Trilio as well:

• virt-v2v cannot change the default kernel in the GRUB2 configuration, and the kernel configured in the VM is not changed during the conversion, even if a more optimal version of the kernel is available on the VM.

• After converting a virtual machine to KVM, the name of the VM's network interface may change, and thus requires manual configuration.

• Trilio does not support nested virtualization OpenStack deployments for VMware migration.

• For Windows VMs, post migration all the non system disk would be in offline state. You would need to login to the guest VM and manually bring all the attached disk online, follow the below steps:

1. To bring a disk online, run command prompt as an administrator.
2. Run command diskmgmt.msc
3. Right click on the offline disk and change it to Online.

• Windows VMs migrated with the Dry-Run type won't be bootable on OpenStack, as complete boot information won't be available until the guest VM is shut down.

Please refer to Post-Conversion Tasks for more information.