If you do the storage migration from XO, you shouldn't have to do anything. XAPI does refuse to move a disk while CBT is on, as @jr-m4 said, but reading XO's code it catches that refusal, turns CBT off on the VM's disks and retries. The price to pay is that the next backup of that VM is a full one, and the backup job switches CBT back on. The other trade-offs are in the docs (https://docs.xen-orchestra.com/backups-and-dr/backup-types/incremental_backups#purge-snapshot-data-cbt) : NBD has to be enabled, snapshot retention has to be 0, and since the purged snapshot only keeps metadata you can't roll back to it.

Just discussed this with @nathanael-h; I would strongly recommend using the load balancer plugin in XO and create some VM-to-host affinity rules, so that your CP VMs are running on different hosts ! So when the RPU comes you would have minimum impact.

@willamcorlin Hello, The fix for CVE-2026-46243 has gone through the entire standard release process, which includes: Review by at least 2 developers. Unit testing within the package (if available). End-to-end testing in the CI (xcp-ng-tests). Several days of user testing. And since the release, we have received no feedback suggesting any potential regression. (This does not mean that the risk of a regression is zero.) If any issue arises, please do not hesitate to get back to us. Respectfully,