What is the status/roadmap of V2V (Migrating from VMware to XCPng/XO) ?

florent

@snk33 the vddk migration path is now far more than a Poc , and it gaves very good result but we are missing some key part to improve things on VSAN , since it's not too easy to setup and we are not a vmware shop

we would gladly work together if we an ensure warm migration can be made reliable even from VSAN.

How can we proceed ? If you have a xoa, would it be ok to allow us to use a tunnel so we can start a VM migration ad find the root cause ?

snk33

@florent sorry I said PoC as reference to our XCP-ng pool cluster, not vddk migration process

Sure we've got a trial license to challenge the solution so we can open a tunnel on the XOA and eventually give some VMware credentials to make some migrations tests. We've got some non-critical VMs to make warm migrations tests on without impact.

Tunnel opened -> 35803

florent

@snk33 said in What is the status/roadmap of V2V (Migrating from VMware to XCPng/XO) ?:

35803

nice I am connected
Could you launch a warm migration ? I will check the logs

snk33

@florent one VM import is in progress. It triggered a VM stop action right away

florent

@snk33 I don't see the snapshot
could you extract the .vmx and . vmsd file of the VM ?

snk33

@florent sure, I've sent a download link by chat message.

nikade

I just migrated from 2x vmware vsan hosts and 1x vmware standalone to xcp-ng in my lab and every migration resulted in a stop of the source vm. It's not a big deal for me in our lab, but I had major issues with some VM's never "finished" the migration.

Xen Orchestra, commit b89c2
Master, commit b89c2

I noticed that after the task has timed out, the VM that was migrated is often able to start, even tho it was not "finished". Is this expected?

florent

@nikade no, it should either succeed or remove the unfinished parts. Are you migrated toward a qcow2 remote ?

could you download one of the vmdk file ( it should be small ) of a VM with at least a snapshot on VSAN ?

florent

@snk33 migration were successful, we need to clarify the doc and/or the tool , the VM need to have at least one snapshot for warm migration

snk33

I can confirm the warm migration work from OVHcloud Managed vSphere from both vSAN and NFS datastores.

We just need to follow these steps :

make a snapshot of the VM on vSphere
import from VMware on XOA with VM stop actions disabled
once import is finished, remove open-vm-tools on active VM and gracefully stop the OS
new import from VMware on XOA with VM stop actions disabled -> it detects the VM has already been imported and just sync the delta
once import is finished, the VM can be started

There are still 2 drawbacks :

the network interfaces naming differs (ens192/226/etc -> eth0/eth1/eth2) so it needs some reconfiguration
the network remapping is global so in case a VM has multiple interfaces with different VLANs (ex : pfSense FW), you need to manually set networks before starting the VM

Anyway it works well and make the migration possible for us without waiting for QCOW2 because we don't have >2TB vdisks (we usually add disks and use LVM to grow FS).

Thanks @florent for your help