@john.c Yet another awesome idea - adding it to the "ToDo List", thanks!

Copy fail is already fixed: https://xcp-ng.org/blog/2026/05/05/april-2026-security-and-maintenance-updates-for-xcp-ng-8-3-lts-2/

That's weird. Adding @Team-XO-Backend in the loop including @julienxovates

@acomav it’s disappointing that there seems to be internal knowledge of: (A) the issue with xcp-ng that triggers this problem but no one has shared the workaround in development to help us to fix it in xcp-ng (B) the issue with XO failing to deal with this edge(?) case that was introduced in December still hasn’t been reverted. I would have thought that if we were given the instructions for (A), someone could help with a patch for (B) or we’d just do it manually and (B) wouldn’t be needed. If we have the information then we can help with the solution rather than feel like we’re living with a festering wound! Seems like a pretty important issue for enterprise software, and I haven’t heard that ‘if you pay money it will be quickly fixed’ - that’s both good and bad. I’d like to think it would be, but don’t want to feel like this community is a sales funnel either! Anyway, xcp-ng and xo are a gift that I am very thankful for in my small business. If the people on this thread can help in any way please let us know!

Thanks for the ping and for narrowing it down; that live-migration repro is a really useful signal. I don't know enough about how the guest tools report IPs back through XAPI to say where the canonicalisation should happen, but it sounds like something @Team-Hypervisor-Kernel might want to look at since the trigger is on the agent side after migration. If it turns out to be reproducible on another Windows guest version (2022, 2019), that might help narrow it further; no pressure though, you've already done the hard part.

Yes it's for this summer, can't tell more precisely (because I don't know ^^)