Hi @odmsys
It's on the roadmap and it won't wait for SMAPIv3. I truly hope we can bring something in a matter of few months, at least to have it to test 
Developers of XCP-ng
Hi @odmsys
It's on the roadmap and it won't wait for SMAPIv3. I truly hope we can bring something in a matter of few months, at least to have it to test 
Looks like an XCP-ng update may have slipped an unwanted site back into our /etc/yum.repos.d/xcp-ng.repo.
Are you sure that this is what happened? XCP-ng updates do not overwrite this file if it has local modifications. It's defined as %config(noreplace) in the RPM spec file for package xcp-ng-release. And no update scriptlets edit it either.
Plus, config files are only updated by rpm when they change, and the file hasn't changed since May 2023.
A few other hypotheses towards the cause:
The RPU evacuated all the VMs from the master successfully but the RPU is stuck at 0% (as seen in Pool Tasks).
Thanks for the report, we have an item in our issue tracker that matches your description. It should be fixed in the upcoming 26.1.23-2.1 xapi version that will be part of the next maintenance update. Please let us know if it keeps happening after the next maintenance update.
Waiting before re-enabling the load balancer task is stuck waiting...
Was it stuck for longer than 30 minutes? If it simply appeared in the task list with a pending status for less than 30 minutes that's actually expected. I ran an RPU on some hosts of my own and made a screenshot for comparison, you can see how the task should look when it's pending and when it's completed.

This task has been introduced in XO 6.7.0 (2026-07-30) by the way, so it's fairly new:
[RPU] Re-enable the load balancer after a configurable safe delay (30 minutes by default) when a rolling pool update ends (PR #10111)
Please let us know if you notice something wrong with it.
Thank you everyone for your tests and your feedback!
This includes updates that you have tested, as well as security updates that were under embargo.
Check out the blog post for the full list of fixes and any post-update steps: https://xcp-ng.org/blog/2026/11/10/november-2026-security-updates-3-for-xcp-ng-8-3-lts/
If you installed the kernel from our last call for testing, please read on. You can check with rpm -q kernel.
The released kernel is not the 4.19.19-8.0.49.3 you tested, but 4.19.19-8.0.46.16. Its release number is lower, so a regular update will leave your hosts on 4.19.19-8.0.49.3. We identified some issues in 4.19.19-8.0.49.3.
To downgrade and install kernel-4.19.19-8.0.46.16, run the following commands:
yum clean metadata
yum downgrade --setopt=protected_packages= kernel-4.19.19-8.0.46.16.xcpng8.3
yum update
reboot
The usual update rules apply: pool coordinator first, etc.
We expect to release a new kernel in a few days, and it will install as a normal update from either version.
@Maelstrom96 Not yet, but you could revert https://github.com/xcp-ng/sm/pull/121 while adding the host and then go back to the current version. It's in progress on our side.
Hello,
The hang bug will be fixed in a future release of Xen, but Windows requires enabling all Viridian extensions (currently 6) to ensure optimal performance and reliability. Enabling Viridian extensions also fixes the hang bug via a different way.
On Windows guests, please reenable all Viridian extensions using these instructions: https://docs.xcp-ng.org/vms/#enabling-viridian-extensions
|
22,520
Posts
3,412
Reputation
|
|
11
Posts
12
Reputation
|
|
0
Posts
0
Reputation
|
|
0
Posts
0
Reputation
|