We pushed the tested packages along a xen security update to the xcp-ng-updates repository, check blog post for summary and related advisories:
https://xcp-ng.org/blog/2026/07/28/july-2026-updates-1-for-xcp-ng-8-3-lts/
Team - OS Platform Release
Posts
-
RE: XCP-ng 8.3 updates announcements and testing
-
RE: XCP-ng 8.3 updates announcements and testing
@rzr Since the targeted test window is over by now, I wonder: what are your plans regarding this set of patches? Will it be released soon?
yes this is the plan, we're a bit slower this time because the iso publication is a longer process, but afaik no issue are spotted so far, thank you for your patience.
-
RE: XCP-ng 8.3 updates announcements and testing
XCP-ng 8.3 LTS Updated installer ISO
The installer ISO has been refreshed with up date packages already published.
The image can be downloaded from:
https://repo.vates.tech/tmp/xcp-ng-8.3.0-20260709.testing.iso
The procedure to install XCP-ng 8.3 remains the same.
The refreshed installer ships updated Xen, Linux kernel and some drivers/firmware, which help with deploying XCP-ng 8.3 on hardware that needs changes introduced by updates not present in previous ISO image releases.
This refreshed ISO has been validated on a subset of supported hardware. Additional testing on any hardware from the community would be greatly appreciated.
As with previous installer releases, it can be used to upgrade XCP-ng from a previous major release (8.0, 8.1 or 8.2). Refer to the Upgrade documentation. For existing XCP-ng 8.3 installations, there’s no need to use this ISO image. Regular yum updates achieve the same results as a fresh installation with that ISO image.
Installer improvements include minor enhancements related to software RAID1 support for the system disks, including support for more than 2 disks in the RAID1 array if anyone really wants that.
New maintenance update candidates for XCP-ng 8.3 LTS
This release batch includes a VBD leak regression fix in XAPI and minor changes needed to build the installer ISO.
A regression was introduced to the
VM.revertoperation inxapi-26.1.4-3.3, which left VBDs attached to the VM when they are not present in the reverted-to snapshot (instead of destroying such VBDs, as was done before).VMs that were reverted to their snapshots after
xapi-26.1.4-3.3may have such "leftover" VBDs. Advanced users can use the leaked_vbds script to detect possible cases in your pools. Sadly, there is no way to automatically distinguish a VBD that was created after a VM.revert from a VBD that survived the VM.revert, so this script relies on the user to determine if the suspicious VBDs are indeed affected or not.What changed
Control Plane
xapi: Fix non-snapshotted VBDs staying attached after VM.revert
Versions
xapi: 26.1.11-1.2.xcpng8.3 -> 26.1.11-1.3.xcpng8.3xcp-ng-release: 8.3.0-37 -> 8.3.0-38
Test on XCP-ng 8.3
yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates rebootThe usual update rules apply: pool coordinator first, etc.
What to test
As usual, normal use and anything else you want to test.
Test window before official release of the updates
~5 days
We would like to thank users who shared feedback since our last call for testing: @Andrew, @XCP-ng-JustGreat, @acebmxer, @bufanda, @flakpyro , @marcoi.
-
RE: XCP-ng 8.3 updates announcements and testing
Applied the latest pushed updated to production, no major issues.
Thank you for testing
The only thing to note is my backup XCP config failed Sunday, (...) This morning the backup ran without issues.
Glad it has finally to work, if problem occurs again feel free to ask about this feature in this subforum:
-
RE: XCP-ng 8.3 updates announcements and testing
We pushed the tested packages (of 3 batches) to the xcp-ng-updates repository, check blog post for summary and related advisories:
https://xcp-ng.org/blog/2026/06/23/june-2026-updates-2-for-xcp-ng-8-3-lts/
Thanks everyone for the tests!
-
RE: XCP-ng 8.3 updates announcements and testing
New maintenance update candidates for XCP-ng 8.3 LTS
This release batch contains fixes, and a security fix on an optional package,
Note: the two previous batches of updates has not been released yet, so if you haven't tested it, you will see more updates than described here when you'll install the update candidates. Refer to the previous announcements.
What changed
Virtualization & System
kexec-tools: Update to sync with Xen Server:- Add checks to reboot a crashed host if kernel crash handling doesn't complete.
Control Plane
xapi: Fix the VM revert regression introduced in earlier "testing" version.
Optional package
lldpd: Fix CVE-2026-46433, a buffer over-read when processing the "VLAN tags" from an Ethernet frame.
Versions
kexec-tools: 2.0.15-20.1.xcp-ng8.3 -> kexec-tools-2.0.15-21.1.xcpng8.3xapi: 26.1.11-1.1.xcpng8.3 -> xapi-26.1.11-1.2.xcpng8.3
Optional packages:
lldpd: 1.0.4-1.1.xcpng8.3 -> 1.0.4-1.2.xcpng8.3
Test on XCP-ng 8.3
Warning: XOSTOR users, refer to the instructions in the previous announcement, which apply here if you haven't installed the previous update candidates.
yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates rebootThe usual update rules apply: pool coordinator first, etc.
What to test
As usual, normal use and anything else you want to test.
Test window before official release of the updates
~2 days
We would like to thank users who reported feedback since our last call for testing:
@Andrew, @ScarfAntennae, @XCP-ng-JustGreat, @acebmxer, @bufanda, @flakpyro -
RE: XCP-ng 8.3 updates announcements and testing
As this is my first time installing these update candidates,
Actually we moved first batch of packages that landed in testing to candidates repo, to avoid mix up in the second batch that just landed in testing repo. Since nothing new appeared in candidate you should probably already had them before, home this is clarifying what is actually happening

Next yum update should just pull the latest stable versions?
Not if you already have installed then from testing (or candidate) repo, because versions are same, it's only the distribution channel that change, no impact for testers.
I'm not sure what you understood from @scarfantennae's question, but that we moved packages from xcp-ng-testing to xcp-ng-candidates doesn't seem on topic here.
The question is: "now that I've applied this update candidates from the testing repositories, am I definitively in testing mode?".
The answer is: no, because:
- The
--enable-reposwitch only applies to the two commands you ran: clearing the cache and applying updates. The repositories remain disabled by default, so yes, next time you update you'll only get stable updates if there are any. - Either the exact packages that you installed will be pushed as official updates (in which case there will be nothing for you to do), or we'll push newer updates that will supersede them automatically next time you update.
Hope it's clear.
- The