@olivierlambert -

Hi,First off, I want to acknowledge the team's commitment and hard work. It's clear that a lot of effort has gone into testing across many different environments, and I truly appreciate the energy and dedication that everyone puts into this project.

I certainly didn't mean to dismiss the significant work that's already been done. At the same time, I think it's important for us all to be open to constructive criticism. Sometimes, even with the most thorough testing, unique configurations slip through the cracks, and that's nobody's fault—it's just the nature of complex IT systems.

My intention was not to diminish the team's work, but to highlight a potential gap that might help improve things further.

Don't intend to bump in but the new migration tool isn't working as per the release notes.

I had similar issues, there is no warm migration. My testing against esxi v7, resulted in:

.Abrupt power off of source VM on esxi.
.VM disks start copying. I can see disk copy progress in tasks.
.Migration tasks fails but multiple disks of the source VM keeps on copying.
.when all the disks are copied, there is no VM with the name available in xcp.
.All disks are labeled orphaned under health in xo.

.Where is the pause/resume function as stated in the release notes.

I don't think the tool has been tested properly. The only difference from older migration tool to this one is progress of disk copying. Otherwise nothing new. The old tool could only do cold migrations and had issues with vms with multiple disks. The new can also only do cold migrations and still has issues with multiple disks migrations.

@olivierlambert - With the host not able to evacuate, i will have to manually move VMs around to other hosts in the pool and then perform maintenance on the host. Imagine you have to do this for few hundred VMs and multiple physical hosts.

Also, the issue is not just the evacuate, if the pool ha is enabled and you disable all the ha property for all VMs, it allows to put the host in maint fine. But when i tried to disable the maint mode, i got this:
"code": "HA_OPERATION_WOULD_BREAK_FAILOVER_PLAN"

So, i disabled ha on the pool, then the disable maint on the host worked fine.

I think whole HA needs to be fully validated and every aspect needs to cross checked, otherwise i dont think its production ready.

For smaller environments, it might not be too much of a pain but even a medium environment this needs to be fixed.

Apologies for jumping in, but what are the plans to resolve this issue. Any update will be appreciated.