What is the status/roadmap of V2V (Migrating from VMware to XCPng/XO) ?
-
Has there been any progress/decision on the V2V improvements for recent vsphere versions ?
-
@florent is working on various improvements yes.
-
Great news ! Thanks @olivierlambert and @florent and let me know if you need some information on the vmware side.
-
@afk said in What is the status/roadmap of V2V (Migrating from VMware to XCPng/XO) ?:
Great news ! Thanks @olivierlambert and @florent and let me know if you need some information on the vmware side.
yes we are prototyping with vddk , it should open some interesting possibilities. stay tuned, hopefully by the end of the summer (I am saying it again : for a prototype)
as a shameless plug, we are looking for users with VSAN to ensure we don't break thing for it
-
@florent said in What is the status/roadmap of V2V (Migrating from VMware to XCPng/XO) ?:
@afk said in What is the status/roadmap of V2V (Migrating from VMware to XCPng/XO) ?:
Great news ! Thanks @olivierlambert and @florent and let me know if you need some information on the vmware side.
yes we are prototyping with vddk , it should open some interesting possibilities. stay tuned, hopefully by the end of the summer (I am saying it again : for a prototype)
as a shameless plug, we are looking for users with VSAN to ensure we don't break thing for it
If you need some beta tester we have a running XCP-ng PoC and need to challenge V2V process from VMware with many VMs on vSAN.
The lack of warm migration is a big issue for us since it would require a significant downtime to migrate some customers' VMs.
We also have NFS datastores that could help but our VMware infrastructure being managed by OVHcloud, we cannot have direct access to NFS to setup XOA remote (unless we just can't figure out the settings to put).
-
@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 ?
-
@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
-
@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 -
@florent one VM import is in progress. It triggered a VM stop action right away
-
@snk33 I don't see the snapshot
could you extract the .vmx and . vmsd file of the VM ? -
@florent sure, I've sent a download link by chat message.
-
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 b89c2I 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?
-
@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 ?
-
@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
-
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
-
@florent no im using EXT local SR. I tried downloading a VMDK and it worked fine, so not really sure whats going on.
I also tried from an esxi 8 host within the same network, same thing, I could also download a vmdk from it.
-
@snk33 Excellent news!
