Xen Orchestra 5.110 V2V not working
-
@florent Yes, I had a snapshot, that isn't the issue. The issue is that the VM is powered off and then the transfer begins.
Thanks.
-
@farokh can you post a task log ( the json ) , even one of a running import, as long as it is after the power down ?
-
@florent Next time I attempt one, I can do that, but again, my question is why is the VM being powered down?
Thanks.
-
@farokh AFAIK it is powered off to transfer the data after the snapshot, since the active disk is locked ( unreadable) as long as the VM is running
To be able to do a better answer I will need to see what's happening, so the task log
-
@florent I guess I'm confused. What then does "Warm migration for all ESXi versions" mean exactly?
Powering off a running machine is really a problem since that can lead to all kinds of corruption/data loss issues.
-
@farokh said in Xen Orchestra 5.110 V2V not working:
Powering off a running machine is really a problem since that can lead to all kinds of corruption/data loss issues.
Not if you properly shutdown your VM, your applications should get to finalize all of their writes and gracefully close and if going "Start > Shutdown" causes data corruption you have some severe application issues that aren't related to the hypervisor.
-
@DustinB That's my point. The "Warm Migration" powers off the running machine.
-
@farokh said in Xen Orchestra 5.110 V2V not working:
@DustinB That's my point. The "Warm Migration" powers off the running machine.
Are you stating that it forcibly powers the VM off, or does it gracefully execute a shutdown, IE "Start > Shutdown"?
-
@DustinB It forcibly powers off the VM.
-
@farokh In case you need to ensure that the VM is powered off manually :
- do the first migration without "stop source"
- stop the VM properly
- launch the migration . It will only transfer the data from the snapshot
-
gracefully powering down a VM may need to go inside the VM ( through ssh/powershell) and that is something we try not to do, especially since we do not know anything on the os inside
It can be easily scripted if you know what is the type of VM running and how to authenticate inside them
-
@farokh said in Xen Orchestra 5.110 V2V not working:
@DustinB It forcibly powers off the VM.
You'd have to do what Florent is saying in this case. But I question why should it matter as long as the migration completes successfully and the VM boots on your new pool...
-
@DustinB Because I was led to believe that I could leave my VM running while the initial transfer is occurring and only have it shutdown for the final bit to be copied. I have VMs that I'd rather not shut down for some number of hours if I can avoid doing that.
-
@farokh said in Xen Orchestra 5.110 V2V not working:
@DustinB Because I was led to believe that I could leave my VM running while the initial transfer is occurring and only have it shutdown for the final bit to be copied. I have VMs that I'd rather not shut down for some number of hours if I can avoid doing that.
You would do what florent said, transfer the VM without shutting down the original VM on ESXi. Once the migration is completed you'd then power off the ESXi VM and power on the XCP-ng.
-
@DustinB When I tried to do that the first thing the migration process did was to power off the VM.
