XCP-ng 8.3 updates announcements and testing
-
New security update candidates for XCP-ng 8.3 LTS (kernel, xen, intel-microcode)
This release batch contains security fix on kernel, version updates, some bug fixes.
What changed
Virtualization & System
kernel: Update to 4.19.19-8.0.46.3- Fixes CVE-2026-43284 (used by the DirtyFrag and CopyFail2 exploits)
intel-microcode: Update to 20260416-1- Improve Intel support and security INTEL-SA-01420
xen: Update to 4.17.6-8.1- Minor bugfixes for x86 systems, including calibration of various timers and handling of PCI devices when disabling SR-IOV
Control plane
xapi: Update to 26.1.4- Minor NUMA fixes
UI
xo-lite: Update to 0.21.0- chore: upgrade dependencies with known security vulnerabilities (#9640)
- These vulnerabilities are not believed to affect XO Lite itself. They are fixed as defence-in-depth.
- Changelog
- chore: upgrade dependencies with known security vulnerabilities (#9640)
Versions:
gpumon: 24.1.0-83.2.xcpng8.3 -> 24.1.0-84.1.xcpng8.3intel-microcode: 20260115-1.xcpng8.3 -> 20260416-1.xcpng8.3kernel: 4.19.19-8.0.46.2.xcpng8.3 -> 4.19.19-8.0.46.3.xcpng8.3xapi: 26.1.3-1.10.xcpng8.3 -> 26.1.4-3.1.xcpng8.3xcp-featured: 1.1.8-6.xcpng8.3 -> 1.2.1-1.xcpng8.3xen: 4.17.6-6.2.xcpng8.3 -> 4.17.6-8.1.xcpng8.3xo-lite: 0.20.0-1.xcpng8.3 -> 0.21.0-1.xcpng8.3
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
~1 day
We would like to thank users who reported feedback since our last call for testing:
@Andrew, @FritzGerald, @IgorGlock, @bufanda, @flakpyro, @manilx, @marcoi, @ovicz, @ph7. -
@rzr There's other stuff in the updates too. Are these also expected?
forkexecd x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 2.5 M message-switch x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 4.6 M qcow-stream-tool x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 1.4 M rrdd-plugins x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 9.8 M sm-cli x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 4.8 M squeezed x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 1.9 M varstored-guard x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 4.9 M vhd-tool x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 4.9 M wsproxy x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 1.1 M xenopsd x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 1.4 M xenopsd-cli x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 2.0 M xenopsd-xc x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 5.3 M -
While updating my host i see 30 updates...
========================================================================================================================================= Package Arch Version Repository Size ========================================================================================================================================= Updating: forkexecd x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 2.5 M gpumon x86_64 24.1.0-84.1.xcpng8.3 xcp-ng-testing 1.6 M intel-microcode noarch 20260416-1.xcpng8.3 xcp-ng-testing 14 M kernel x86_64 4.19.19-8.0.46.3.xcpng8.3 xcp-ng-testing 29 M message-switch x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 4.6 M qcow-stream-tool x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 1.4 M rrdd-plugins x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 9.8 M sm-cli x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 4.8 M squeezed x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 1.9 M varstored-guard x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 4.9 M vhd-tool x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 4.9 M wsproxy x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 1.1 M xapi-core x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 30 M xapi-nbd x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 3.1 M xapi-rrd2csv x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 3.0 M xapi-storage-script x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 2.5 M xapi-tests x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 5.0 M xapi-xe x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 1.5 M xcp-featured x86_64 1.2.1-1.xcpng8.3 xcp-ng-testing 1.5 M xcp-networkd x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 4.8 M xcp-rrdd x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 3.6 M xen-dom0-libs x86_64 4.17.6-8.1.xcpng8.3 xcp-ng-testing 703 k xen-dom0-tools x86_64 4.17.6-8.1.xcpng8.3 xcp-ng-testing 2.0 M xen-hypervisor x86_64 4.17.6-8.1.xcpng8.3 xcp-ng-testing 2.4 M xen-libs x86_64 4.17.6-8.1.xcpng8.3 xcp-ng-testing 65 k xen-tools x86_64 4.17.6-8.1.xcpng8.3 xcp-ng-testing 46 k xenopsd x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 1.4 M xenopsd-cli x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 2.0 M xenopsd-xc x86_64 26.1.4-3.1.xcpng8.3 xcp-ng-testing 5.3 M xo-lite noarch 0.21.0-1.xcpng8.3 xcp-ng-testing 2.6 M Transaction Summary ========================================================================================================================================= Upgrade 30 Packages Total download size: 152 M -
I'm seeing 30 updates as well but they're installed and seem to be working fine on my test systems.
-
I'm seeing 30 updates as well but they're installed and seem to be working fine on my test systems.
I think I only listed sources packages (which contains several binaries sub-packages having the same versions), so that's expected
BTW thank you for reactivity on testing
-
Indeed we only list source packages.
xapi's source RPM alone creates a lot of RPMs each time, for example. In this case, all those with version 26.1.4-3.1.xcpng8.3. -
@rzr
Seems to be OK
ran a few backups and installed a new VM
XO-lite was already on 0.21.0 (13f98) after the update 2 weeks ago.. Don't know if it's the same. -
Installed on my usual batch of test hosts, so far so good.
-
XO-lite was already on 0.21.0 (13f98) after the update 2 weeks ago.. Don't know if it's the same.
yes it's same landed in testing before and not yet moved to updates, btw this version does not bring much change as it's a rebuild with dep update, see there is no full changelog :
https://github.com/vatesfr/xen-orchestra/releases/tag/xo-lite-v0.21.0
-
@rzr Updated and running on most systems now. Rolling pool reboot worked correctly (need to disable backups first). VMs and CR running normally.
After a large S3 backup session (that succeeded), GC on the master got stuck in a loop and failed (lock issue). A reboot of the pool master was required to resolve the problem then GC coalesced the VHDs without additional action. Other pools did not have the same problem. I have not seen that issue before, but everything seems fine now so I can't blame the update.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login