Oh sorry, I thought you were on the sources In that case, you just have to provide the XOA channel you are on, that's enough

Regarding your issue, it's hard to tell, it seems you have a problem at the host level. Have you enabled IOMMU in the bios?

You probably need to raise the max upload size or something.

Hi,

Yes, by default, adding a new host to a pool, it will be lowered on CPU features to the common denominator, in other word, cutting that's not common between all pool members.

So:

1. If you add a more recent CPU to an existing pool, the CPU won't use new CPU features
2. If you add an older host to a pool, it will lower down all features from existing CPUs

Hi,

You might have a discrepancy between the IP you use to connect and the internal IP reported by XCP-ng, so likely your XO is trying to connect the console via a different IP (the old ones?)

Hi,

As stated in https://docs.xen-orchestra.com/community, you should provide the commit number and double check you are on the latest version available on master

Hi,

It was never meant to be a 2 ways synchronization plugin. Making it 2 ways considerably raise the complexity of such plugin (because we would need to make configuration for decision on when to take it one way and the other, and each use case is different).

I would say: you shouldn't have any IP that's already in Netbox from other source in the IP range that's used for your VMs.

Hi,

Let me ask the XO team via @lsouai-vates

Ping @Team-Hypervisor-Kernel

I'm not aware of that issue still being… an issue.

Ping @lsouai-vates

Another one @lsouai-vates

1. About the xsconsole: sometimes it's not refreshing. You can try to get access to the console, then type "xsconsole" it will start it and you should see it works
2. You must have the master up to date if you want your slave to connect again. I never tried to elect a new master in the middle of the upgrade, I would discourage it. Better shutdown some VMs on the master, upgrade it and you are automatically back on track.

Pinging the @Team-DevOps

Ping @lsouai-vates

@Gheppy It's not clear to me. Is it fixed on latest commit on master as of now?

Hi,

The idea behind XO from the sources is to give home users, enthusiasts, and lab setups full access to the XO features, completely free and open source. On the other hand, XOA is our commercial offering, built specifically for production and business environments, with official support, automatic updates, and extra services.

So while XOA isn’t intended for home use, XO from sources is exactly made for that, and we’re happy to see so many people using it in their labs!

Then try to find anything happening around that time on other hosts, equipment, storage and so on.

Sorry I forgot to publish in here the news: https://xcp-ng.org/blog/2025/06/16/xcp-ng-8-3-is-now-lts/

Indeed, since June the 16th, XOSTOR is available on 8.3

Well dmesg is fine, I would also check the switch logs if you have anything happening on the ports where you host are connected. Since you can find when it's happening with dmesg, I would use that to correlate with anything else happening few minutes before.

Sure, but it's nice to have your feedback because if we improve that page, we are saving hours for others after you, which is exactly the point of having a great community!

Thanks for sharing it with us!