@nikade No, but I've done a lot -- probably one or two dozen -- when doing updates to help speed up the evacuation of hosts. You can check the queue with
"xe task-list" to see what's being processed or queued.
Ambassadors
People talking about XCP-ng/XO around them
-
RE: Some HA Questions Memory Error, Parallel Migrate, HA for all VMs,
-
RE: Some HA Questions Memory Error, Parallel Migrate, HA for all VMs,
@nikade And if you queue up more than three migration instances, my experience has been that then they are processed such that no more than three run concurrently.
-
RE: Some HA Questions Memory Error, Parallel Migrate, HA for all VMs,
@nikade In XenServer at least, I thought the limit was three VMs being able to be migrated in parallel, according to this:
https://docs.xenserver.com/en-us/xencenter/current-release/vms-relocate.html -
RE: Some HA Questions Memory Error, Parallel Migrate, HA for all VMs,
@vahric-0 VM migration takes a lot of resources; be sure to give dom0 plenty of VCPUs and RAM. You can run top or xentop from the CLI to see the impact during migration and watch for CPU and memory saturation as a sign that dom0 does not have adequate resources.
-
RE: Same CPU XEON 4309Y but migration failed because some CPU features missing !
@olivierlambert said in Same CPU XEON 4309Y but migration failed because some CPU features missing !:
It could be microcode update and BIOS update making that change. Since they are not in the same pool, this can be expected. Indeed, migrate to the more recent, upgrade the old one/reboot and that should do the trick.
Yes, the BIOS/microcode differences do sometimes change the CPU mask. They need to be identical in many cases on all hosts within a pool.