@acebmxer
Can you suspend the vm ?
If its not possible its most likely a kernel thing inside the vm.
If you can suspend the vm however, it points more to a timing/timeout issue with the migration.
Thanks both, very useful. One constraint on our side: this VM runs SQL Server 2014, and per Microsoft it’s supported only up to Windows Server 2019 (not 2022/2025). So our realistic target is 2012 R2 → 2019 in-place (after updating SQL to SP3), with the old Citrix tools removed beforehand and the new XCP-ng tools installed afterwards. We’ll rehearse the whole thing on a clone first, and note down the static IP config before removing the tools.
@poddingue Turns out it is all secondary-to-secondary out of sync. So that makes it less intense, though if primary dies I wonder how it will resolve this, or if it will become split brained. Still unsure of how it happened, but the ones I manually cleaned up have not come back. Going to continue to manually clear them up. If it happens again I will have an alert setup to notify me, and I have all the xcp-ng logs and everything to be able to see what happened.
If that happens I will post here with details and logs for the resource so we can see how it occurs.
[image: image.jpeg]
@AtaxyaNetwork Merci pour tes recherches !
Oui "cd_label" serait cool comme ajout au plugin ce qui permet sur les distro type Fedora/Redhat de ne pas avoir de boot_command à gérer
