XOA migrate the XO itself
-
Hello.
I'm in process of migration of VM within the pools from old to new hosts with shared NFS. The old Hypervisors are Intel based and the new ones are AMD. So far I ended up by doing it with VDI migration at first and then power-cycle the VM and "Start on..." the new host. Doing it that way because the live VM migration won't work. It is failing with error related to CPU features incompatibility. (I'm sorry, this happened a week ago, so the log is not available.)
One machine is still refusing to start on the new hypervisor.
My questions are:- Is there anything I'm missing in the process?
- What is the correct way of migration for XOA's VM itself regarding my situation? My plan is to migrate the VDI on the NFS, shutdown the machine and power it on from the host's terminal. Would that work?
Thanks!
-
You can't, indeed, live migrate a VM from Intel to AMD (or vice-versa), for obvious reason (the VM will try to call Intel specific instructions after migrating on an AMD CPU, the result would be… a crash!)
We had a similar migration ourselves (in our own prod), from Intel to AMD. And we decided to use Continuous Replication to make a first "backup" on destination (the full) while the original VMs were running (no service interruption).
Then, we shut down the VMs, make another round of replication (delta, very fast) and then we booted on destination.