The original problem could be a known issue when creating bond including the management interface that we have to investigate. Although the emergency network reset should have fixed that, so maybe it is a mix of the bond creation issue and MTU issue.
In the reinstalled pool, did you create the bonds already? If so I would think changing the MTU should be fine, especially as it worked on other PIF, but with MTU issue it is often quite sneaky, so I would not make any promises either.
Update published: https://xcp-ng.org/blog/2025/05/14/may-2025-security-update-for-xcp-ng-8-2-8-3/
Thank your for the tests.
Update published: https://xcp-ng.org/blog/2025/05/14/may-2025-security-update-for-xcp-ng-8-2-8-3/
Thank your for the tests.
Sorry for the delay, I'm a bit swamped. That does not ring a bell to me right now.
What is you setup like? How many pools, how many host per pool, is there bond on some of them?
Then, more to debug what was actually created as you stated there network does exist but there is no traffic:
On your hosts:
xe network-list to get the uuid of one of these private networks you createdxe network-param-list uuid=<netwok-uuid> should tell you in which bridge they areovs-vsctl show shows all bridges and their ports, in there you should be seeing the bridge you found in previous step. This bridge should have:
On your VM:
ip link or similar when you attached the network?We'll see from there if we can get an idea of what is happening.