XCP-ng 8.3 updates announcements and testing

acebmxer

Installed updates on home lab. No issues to report initially other then nslookup still an issue.

[10:54 xcp-ng-haznrrtw ~]# nslookup vates.com 8.8.8.8
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   vates.com
Address: 104.21.52.238
Name:   vates.com
Address: 172.67.205.118

openssl_link.c:132: INSIST(dst__memory_pool != ((void *)0)) failed, back trace
#0 0x7f163cd960e7 in ??
#1 0x7f163cd9603a in ??
#2 0x7f163d9a3780 in ??
#3 0x7f163c1aedf6 in ??
#4 0x7f163c1f5464 in ??
#5 0x7f163c1f5732 in ??
#6 0x7f163c1f4b8d in ??
#7 0x7f163a95fbd9 in ??
#8 0x7f163a95fc27 in ??
#9 0x7f163a94844c in ??
#10 0x405818 in ??
Aborted (core dumped)
[12:50 xcp-ng-haznrrtw ~]#

flakpyro

Installed on my usual hosts, one of which has an E810 and used the ICE driver, no issues so far however i am not using LACP bonding on that host.

rzr

@acebmxer said:

@rzr
No issues to report initially other then nslookup still an issue.

openssl_link.c:132: INSIST(dst__memory_pool != ((void *)0)) failed, back trace

Yes I looked at it, it looks like it's a design isssue that was fixed in later version of bind.

In details If I understand correctly this patched version of nslookup is facing a SIGARBT caused by an assert on previously cleanup resources (dst__memory_pool) which is unexpected in finishing part of the openssl thread (dst__openssl_destroy).

This bind patched version (where ssl support is in progress) is also known to have memory leaks, but those are resolved in later version, so until we catch up you'll probably have to live with this little annoyance on process exit unless we find (and validate) a better fix.

Andrew

@rzr Installed and running. Not expecting any issues because I'm not using SMB/CIFS, ice card, or CPU with affected microcode.

Rolling pool reboot failed me again... This time it got stuck evacuating a host with no VMs.

bufanda

@rzr Installed on my usual lab pool. No immediate issues seen.

ph7

@rzr

manilx

@Andrew I have the RPU failing most of the time now also. I have reported and opened a ticket. No solution so far. It's a hit and miss and beginning to be a PITA.

Pilow

@manilx yup, same here
we evacuate & roll patch manually because RPU is inconsistent in achieving a full pool update nowadays

maximum hosts in pools are 3, so it is still easy to process manually
thoses with 5-6+ hosts must be more painful

olivierlambert

That would be interesting to group your findings/issues on RPU in a dedicated topic, because I don't think the logic changed recently So it's an interesting investigation to make.

JeffBerntsen

@rzr
Seems to be working well on my test systems as well.

marcoi

update to latest test patches on 2nd pool. no issue. LACP worked, started UB26 VM on host 4 and live migrated to host 3.

MajorP93

@rzr Installed those security update candidates in my XCP-ng test environment.
So far no issues whatsoever. Basic operations all work. VMs running etc.

rzr

rzr said:

New security update candidates for XCP-ng 8.3 LTS (kernel)

Test window before official release of the updates

~3 days

The testing window is extended a bit, expect also a next batch (to be tested later this month).

It has been planned to group updates for the convenience of administrators (stay tuned in blog).

Meanwhile If you didn't notice yet, an updated xen-4.17.6-9.2.xcpng8.3 package landed in testing repo, it addresses some low risk vulnerabilities as reported at:

VSA-2026-017 (XSA-491, CVE-2026-42487)
VSA-2026-018 (XSA-492, CVE-2026-42489 - CVE-2026-42490),
VSA-2026-019 (CVE-2025-10263, XSA-493)
VSA-2026-020 (CVE-2026-42488, XSA-494)

More to come soon

bufanda

@rzr Installed all currently available patches on my lab pool. No issue so far in normal use.

JeffBerntsen

@rzr

Installed on my test systems and all seems well so far.

acebmxer

@rzr

I also installed updates this morning no new issues to report.

Andrew

@rzr Updates installed everywhere (on top of the previous updates). Rolling pool reboot worked this time (with correct prep).

flakpyro

Installed on my usual test hosts. No issues so far.

XCP-ng-JustGreat

Installed latest updates on my four host home lab pool and a fifth standalone host with no apparent issues.

rzr

New maintenance update candidates for XCP-ng 8.3 LTS

This release batch contains mostly fixes, tools version update, a some improvements.

Note: the previous batch 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

xen: Add support for xenpm get-core-temp to query CPU temperature on Intel platforms.
- Use xenpm get-core-temp to get the temperature on Intel's CPU, to fallback unsupported coretemp. Doc update being reviewed.
grub: Sync with XenServer 8.4: Fix a rare out-of-memory error.
dracut: Fixes
- Fix to force reboot/shutdown/halt.
- Fix issue where the omission of 'override' kernel modules from the initrd image could, in rare instances, prevent a freshly installed XCP-ng host from booting.

Control Plane

xapi: Update to 26.1.11, add fixes and improvements.
- Fixed an issue where a newly installed host wouldn't be able to join a pool due to incompatible features exposed by storage.
- Fix shutdown VMs not being migratable due to errors generated when the VM was running.
- Allow moving VMs back to DHCP from static IP with configure_ipv4/6.

Network

stunnel: Fixed stunnel only considering one of the self-signed certificates with the same DN.

Tools

xcp-ng-pv-tools: Update to XCP-ng Windows Guest Tools 9.1.200 (full changelog).

Drivers

mpi3mr-module: Update to version 8.17.1, adding newly supported SAS5116 devices.

Optional:

mellanox-mlnxen-alt: Fix build error with kernel 4.19.19-8.0.42.1+.

Storage

kmod-drbd: Update to 9.2.18 (full changelog)
- Improve XOSTOR stability when evacuating/evicting an host.
xcp-ng-release-linstor: Relocate config file to v8.3-linstor repository.

Versions

dracut: 033-538.xcpng8.3 -> 033-539.1.xcpng8.3
gpumon: 24.1.0-84.1.xcpng8.3 -> 24.1.0-91.1.xcpng8.3
grub: 1:2.06-4.0.2.1.xcpng8.3 -> 1:2.06-4.0.5.1.xcpng8.3
mpi3mr-module: 8.6.1.0.0-1.xcpng8.3 -> 8.17.1.0.0-1.xcpng8.3
stunnel: 5.60-5.xcpng8.3 -> 5.60-6.1.xcpng8.3
xapi: 26.1.4-3.2.xcpng8.3 -> 26.1.11-1.1.xcpng8.3
xcp-featured: 1.2.1-1.xcpng8.3 -> 1.2.1-2.xcpng8.3
xcp-ng-pv-tools: 8.3-17.xcpng8.3 -> 8.3-18.xcpng8.3
xen: 4.17.6-9.1.xcpng8.3 -> 4.17.6-9.3.xcpng8.3

Optional packages:

mellanox-mlnxen-alt: 5.4_1.0.3.0-2.xcpng8.3 -> 5.4_1.0.3.0-3.xcpng8.3

XOSTOR users: specific update procedure

Some XOSTOR packages are provided in separate repository, and should be installed along xcp-ng regular packages, using the following commands:

yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates,xcp-ng-linstor-testing
yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates,xcp-ng-linstor-testing
reboot

Note: linstor packages themselves have not been updated, only kmod-drbd and xcp-ng-release-linstor. Thus, this time it's not necessary to restart the satellites before rebooting.

The following XOSTOR-specific package received updates (and must be updated in the same transaction, which the above update commands will do):

xcp-ng-release-linstor: 1.4-2.xcpng8.3 -> 1.5-1.xcpng8.3 (from xcp-ng-testing repo)
kmod-drbd: 9.2.16-1.0.xcpng8.3 -> 9.2.18-2.0.xcpng8.3 (from xcp-ng-linstor-testing repo)

Test on XCP-ng 8.3

Warning: XOSTOR users should skip this part and follow the instructions of the previous section.

yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates
yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates
reboot

The 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, @XCP-ng-JustGreat, @acebmxer, @bufanda, @flakpyro, @jeffberntsen, @majorp93, @manilx, @marcoi, @ph7.