Team - OS Platform Release

Private

Posts

  • 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.3
    • xapi: 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
    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, @ScarfAntennae, @XCP-ng-JustGreat, @acebmxer, @bufanda, @flakpyro

  • RE: XCP-ng 8.3 updates announcements and testing

    @rzr said:

    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-repo switch 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.

  • 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.

  • RE: XCP-ng 8.3 updates announcements and testing

    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.

  • RE: The Lowest Priority Bug Ever? (/etc/udev/rules.d/z10-xen-vcpu-hotplug.rules)

    rzr said:
    Since it's a lowest priority you can take all the time you need, and If too busy, no problem we can do it for you and then backport the change to XCP-ng.

    Or Is there any volunteer interested to learn about how to contribute to xcp-ng ? I can mentor you, pm me.

  • RE: XCP-ng 8.3 updates announcements and testing

    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:

    More to come soon