V2V - Stops at 99%
-
Got most of them working, except 2 of the bigger ones.
-
@nikade we'll got them ( on monday )
could you remind me the exact size of the disks ? to check for an alignment issue -
@florent it was 2 windows vm's, both with 100gb but not even 50% filled.
Edit: All Linux VM's worked tho.
-
@nikade TBF I was expecting from multi TB VM imported through qcow2
-
@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. -
@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-serverXXXXthe logs are in a stderr file in $tmpDir ( they can be quite big )
-
@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! -
@nikade I believe that you can still find the entries in the journalctl output.
-
@Danp Yeah? How?
Let me know if you want me to grab some logs for you guys, if it's still interesting. -
@nikade can you try a journalctl | grep 'nbdkit logs' ?
new branch with more fixes ( feat_exposes_esxi_export ) the main fix is a >= that should have been a > https://github.com/vatesfr/xen-orchestra/pull/9411/changes#diff-f0de876ee608dac8d272996fbb8fa63ec76473bd260ad5abf1995a805866d1beR130 hopefully I am not paid by the character. Don't forget to do a yarn build at the root of your XO and restart it.
this also expose a way to export a disk from an esxi/vsphere with xo-cli.
First install xo-cli with
npm install -g xo-cliand register it https://docs.xen-orchestra.com/architecture#xo-cli-clixo-cli.mjs esxi.exportDisk host=ipOfEsxiOrVsphere user=EsxiLogin password='PlzDontEnter!' vm=3 disk='scsi0:0' @=/mnt/ssd/export/out.qcow2 format=qcow2You can check that the export is valid with
qemu-img check /mnt/ssd/export/out.qcow2
