V2V - Stops at 99%

florent

@Vanny we are still working on the issue which seems to be partly due to the new V2V code, and partly to qcow2 supports.

Note that the v2v tool is a convenient tool, but there are a lot of good tools out there, and some may better fit your needs after testing.

olivierlambert

FYI, Vanny is a representative from Vinchin

nikade

Got most of them working, except 2 of the bigger ones.

florent

@nikade we'll got them ( on monday )
could you remind me the exact size of the disks ? to check for an alignment issue

nikade

@florent it was 2 windows vm's, both with 100gb but not even 50% filled.

Edit: All Linux VM's worked tho.

florent

@nikade TBF I was expecting from multi TB VM imported through qcow2

nikade

@florent Sorry to dissapoint you
Can you remind me where the vmware-import logs are stored on the XO machine? I can see if I still have them for you, it could be an alignment issue.

florent

@nikade this is a good news : that will be easier to test and debug.

during an import you should have a nbdkit logs of ${diskPath} are in ${tmpDir} where diskPath is the datastore/diskname.vmdk and tmpDir is something like /tmp/xo-serverXXXX

the logs are in a stderr file in $tmpDir ( they can be quite big )

nikade

@florent Oh shoot! So only during the actual vmware import? I guess they're gone now then
Sorry I couldn't be of more help!

Danp

@nikade I believe that you can still find the entries in the journalctl output.