@poddingue
Thanks for taking a look.
Yes it is this part that tells me that it should start the VM automatically once the import has completed.
"After the transfer, the VM on XCP-ng side is started:"
Followed by, "This process is fully automated, without any human intervention after it starts on step 1."
[image: image.jpeg]
https://docs.xcp-ng.org/installation/migrate-to-xcp-ng/
But my findings/experience is that the VM does not start once the import/transfer has completed.
So either the docs are wrong. Or the function is not behaving as intended. I'm acctually fine either way. As long as I know what to expect. However, I would like to have it auto-start the VMs after transfer completion. Which would make the procedure "Fully automated".
Update:
Am I assuming correctly that "the XO V2V guide says to start the VM yourself once the migration is complete " you're reffering to, is part of the "test migration"-procedure? Not the acctual production mgiration?
Because:
"Final migration
Run the production migration
When you're ready for the final migration:
Shut down the source VM completely.
Start the V2V migration in Xen Orchestra with the Stop source option enabled.
This ensures the final sync happens while the VM is powered off, and prevents any inconsistencies."
In my mind doesn't state that the VM should be started manually post-transfer.
Great thanks in advance for discussing!
Cheers!
