As customers look to OpenShift Virtualization as an alternative to other virtualization platforms, having the ability to move an unsupported (any OS that is not supported by virt-v2v) to OpenShift virt and let the customer find the proper settings to make the VM image run in OpenShift virt.  

If the MTV tool just copied all the source disks, and created a virtual machine definition that copied the all the relevant source VM details (CPU/Memory/Mac Addresses, etc), but did NOT power it on. This would allow the end user to tweak the configuration and boot the machine.

Current process to make this work is to

1. export VM as an OVA
2. use qemu-img to convert from VMDK to QCOW2
3. upload qcow2 image to cluster
4. manually create vm definition

One other alternative we have found is to:

1. create a bootable fedora disk
2. attach that disk as the primary disk on the VM we want to migrate
3. use the MTV tool to migrate the vm
4. delete the "fake" fedora boot disk
5. update the migrated VM to boot from the original boot disk
6. modify the VM to use OS supported disk controller and network controller

The second option allows the customer to use MTV as the migration tool.

This feature is required to support things like "Appliance" VMs, or VMs that are based on other Linux distributions. End user will need to figure out how to get the vm image to run in OCP-V, this is just to make the vm base disk copy easier. Perhaps using "virt-v2v-copy-to-local" would be the best way to do this. (https://libguestfs.org/virt-v2v-copy-to-local.1.html)