Just taking screenshots for others... @mathieura is looking into the issue... after update this how the proxies show. Along with the log posted in first post. [image: Screenshot_20261001_055108.png]

@lem2405 No problem. Let me know if you still encounter any issues.

@john.c Indeed, John, and I almost forgot that the backup network on each host was actually on a separate, isolated NIC, and not at all on the VLAN.

@poddingue Looks like it clears after 30 days... but not the XO Config Cloud backup... This is from XOA.. [image: Screenshot_20261001_054141.png] Just filtered for backup... Oldest is from 7-19-26 oldest backup job 8-31-26. [image: Screenshot_20261001_053839.png]

i forgot how i got VM_BAD_POWER_STATE. Probably need to choose multiple VMs from different pools and do a batch migration.

@trelane Hello, the bug affects Xen drivers of any 9.0 series (considering the upstream code, it goes back to circa September 2019). 9.2.385 contains the fix, which was merged upstream just this month. The bug also impacts network connections, however to a lesser extent due to its nature. I believe that the bug is also present in XenServer VM Tools 9.6.0 and by extension, older versions of it. We recommend that you switch to the XCP-ng tools whenever possible, also due to its other benefits (fully open source, validated for XCP-ng and optimized for Xen Orchestra).

@johnnezero It just came out with the release... now Just one thing, you may have empty directories even after the reclaimSpace task but they should be empty

Great, thanks for the feedback @yomeyo !

A short label on that step would've saved you the ghost hunt, yes. Since it's a UI change more than a bug, I think https://feedback.vates.tech is where it'd get picked up, ideally with your two screenshots showing "All (8)" against seven VMs.