I'm not aware of any issue to live migrate XOA VM 
We do that very often, as per many many customers and users all around the world. If you are using XO from the sources, I would suggest to try instead with XOA (even Free version is enough)
Vates
People working at Vates
Posts
-
RE: Best Way to Live Migrate XO VM
-
RE: Created a new bond interface and lost management connectivity to hosts
The original problem could be a known issue when creating bond including the management interface that we have to investigate. Although the emergency network reset should have fixed that, so maybe it is a mix of the bond creation issue and MTU issue.
In the reinstalled pool, did you create the bonds already? If so I would think changing the MTU should be fine, especially as it worked on other PIF, but with MTU issue it is often quite sneaky, so I would not make any promises either.
-
RE: Our future backup code: test it!
@Tristis-Oris I still don't have the solution I am working on it .
-
RE: Xcp-ng 8.2 no more recognized with Cloudstack since last update
Indeed, and also you need to ask CloudStack people, because that's very likely related to CS and not XCP-ng
-
RE: Best Way to Live Migrate XO VM
As for many (all?) virtualization platform, you need to get the tools installed on your VMs to get an optimal usage of it.
-
RE: Live migration from VMware not working, only when I power off the VM
Please review our Vmware migration checklist -- https://help.vates.tech/kb/en-us/37/133
Depending on your type of datastore, it is possible that you need to perform a cold migration where the VM is shutdown prior to attempting the V2V process. Also, the creation of a snapshot is a requirement unless you are migrating from a VSAN.
-
RE: Best Way to Live Migrate XO VM
Hi,
If the migration doesn't work, it means there's something wrong happening in your VM (it doesn't cooperate). Check your memory settings to be sure dynamic min = dynamic max = static max.
Then, check from the OS perspective if there's enough free RAM and if the OS isn't frozen or something that could cause the migration to fail.
Live migration should work at 100% of the time when the guest cooperate, so there's clearly a problem.
