Xen Orchestra 5.110 V2V not working
-
Starting to play with the imported VM, and there are 2 snapshots, both from the import process. I'm going run the VM with them for now and then try deleting them once I see it's working.
-
@farokh If my understanding it correct : it migrated the source VM correctly , without breaking anything on esxi side, but it would be better if the V2V gives more feedback to the user ?
Also, you would like to be able to select different networks as target ? -
@florent That's a good summary, however, V2V did power off the VM before starting the import, which defeats the point of a warm migration, and the power off is abrupt, not allowing the OS to cleanly shutdown, which means that there's a potential for data loss.
Thank you.
Edit: I was just looking at the blog post for 5.110 and I noticed this:
The interface has been polished as well. There’s now a progress bar visible from the start of the migration, speed metrics are recorded in the VDI, and snapshots are created at each step. This allows the process to pause and resume safely without needing to create multiple VMs. Finally, UEFI VMs are no longer forced into Secure Boot mode, avoiding previous boot issues.I guess I'm confused as to why I didn't see any of this?
-
@farokh do you have at least one snapshot on the source ? The data migrated while the VM is running are the data before the last snapshot
The power off is effectively a call to powerOff, is there a better alternative (that can work with or without the vmware tools installed) ?
the progress bar are visible in the task view, or on the disk tab on the VM being imported ( not yet in the form , this will probably wait for the XO6 version of this page )
-
@florent Yes, I made sure that I had a snapshot.
I guess my main question is why the VM is being powered off? It's supposed to be a warm migration, meaning the VM is running while the data is migrated, correct?
But, assuming that you have to power the VM down, and I haven't done any programming or scripting with ESXi, but I can tell you that the web interface can tell if the VM has the tools installed. If the tools are installed, you should be able to send a Shutdown request, which should shut the machine down gracefully, allowing the OS to perform tasks prior to powering off. You can wait a few minutes and if the machine hasn't powered off yet, you could then issue the power off command to stop it.
Next time I test a migration, I'll check the task and/or disk to see the status.
Thanks.
-
Hi, just wondering if there's any update on why the VMs are being shutdown for the migration.
Thanks.
-
We made a patch release of XOA, improving some aspects. Have you tried it?
-
@olivierlambert No, I wasn't aware. I'll take a look.
Thanks. -
Is there a blog or forum post about the updates? I can't seem to find anything.
Thanks.
Edit: and without the VMWare tools, there's no way to do a clean shutdown. It's, again, simply powered off.
-
Tried it again, on a different VM. I took a snapshot, and made sure that the VMWare tools were uninstalled.
The job was started at 10:57, it's now 18:42 and the job is still running.
At 12:30, the VM was shutdown and has been shut down since then.
Edit: So the import completed at some point (something like 7-8 hours), but the original VM was never started up again.
-
@florent is working on improving the details of each step so you know what's going on.
-
@farokh the VM (from source or target) are not started automatically
After the migration, the VM from on the xcp-ng host shoud be ready to start, with snapshot corresponding to the steps of the replication
this is not automatic because, for now, we put a lot of work on the disk data transfer, but there is much to do around it to ensure the VM start exactly as intended : guest tools, advanced network or storage configuration.
-
@florent The VM I ws referring to was the one on the ESXi host.
If you're providing a warm migration, then that VM should be running during the transfer.
If for whatever reason a warm migration can't be done, then the user should be made aware of that.
At this point, just to be safe, I'm going to make the assumption that the VM to be migrated has to be powered off.
