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?
Tracked it down to it thinking there was a pool version mismatch... then when I tried to transition to a new master it would fail with Xmlrpc_client.Connection_reset ... digging deeper it was complaining that it couldn't restore from the wrong version.
Lots of head banging later... I setup a backup for the pool metadata and forced the backup immediately. TADA... I can now change the master with no issues at all.
@ronan-a said in XOSTOR hyperconvergence preview:
@peter_webbird We've already had feedback on CBT and LINSTOR/DRBD, we don't necessarily recommend enabling it. We have a blocking dev card regarding a bug with LVM lvchange command that may fail on CBT volumes used by a XOSTOR SR. We also have other issues related to migration with CBT.
Is the problem still occurring on latest XCP-ng / XOSTOR version ? Not being able to use CBT on XOSTOR is a big issue for backup/replication.
