I am doing a VMware VM migration PoC for a customer using MTV 2.6 on OCP 4.15.8 with CNV 4.15.1 . It is a single VM with 4 disks - one for the root disk and the rest forming a LVM volume group. The migration completes "successfully" and the VM boots up, but goes into emergency mode, because it cannot mount the logical volumes from the volume group. Upon inspecting the disks, it was found that there is no partition nor LVM headers in those three LVM group disks.

I think it is caused by not having proper symbolic links in the /var/tmp/v2v folder in the virt-v2v pod. I have attached a screenshot of the folder structure while the `nbdcopy` is progressing. The `nbdkit` process is targetting the /var/tmp/v2v/[vm-name]-sd[?] , while the symbolic links created are /var/tmp/v2v/[vm-name]-sda[*] 

Currently the PoC is blocked because of this bug.