XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XCP-ng 8.2 updates announcements and testing

    Scheduled Pinned Locked Moved News
    708 Posts 67 Posters 1.1m Views 86 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A Offline
      Andrew Top contributor @gduperrey
      last edited by

      @gduperrey Installed and working on a HA pool and other hosts, no XOSTOR.

      1 Reply Last reply Reply Quote 2
      • gduperreyG Offline
        gduperrey Vates 🪐 XCP-ng Team
        last edited by

        Update published: https://xcp-ng.org/blog/2025/01/23/january-2025-maintenance-update-for-xcp-ng-8-2-lts/

        Thank you for the tests!

        1 Reply Last reply Reply Quote 1
        • gduperreyG Offline
          gduperrey Vates 🪐 XCP-ng Team
          last edited by

          New update candidates for you to test!

          A new batch of non-urgent updates is ready for user tests before a future collective release. Below are the details about these.

          • intel-igc: Fix a possible update issue due to a recent package name change.
          • microcode_ctl:
            • Latest Intel release microcode-20250211:
              • Security updates for:
                • INTEL-SA-01166, INTEL-SA-01213, INTEL-SA-01139, INTEL-SA-01228
                • Updates for multiple functional issues
                • Upstream update drops files for older Sapphire Rapids steppings, we kept the previous versions
          • netdata:
            • Update to Netdata v1.44.3
              • Fix dmesg warnings due to setuid+capabilities on xenstat plugin
              • The freeipmi plugin now comes in a separate package
              • Improve systemd service restart with a custom script waiting for Netdata to be fully up-and-running before stopping it.
          • openvswitch:
            • Synchorized with XS82ECU1081. Alignement with the hotfix, no functional changes.
            • Fix CVE-2022-4337 & CVE-2022-4338 when parsing malformed AutoAttach
          • qemu: Fix CVE-2023-3354, which could cause QEMU to crash when handling multiple VNC connections. If an incorrect response is received while closing a connection—whether due to a bug or intentional manipulation—it could trigger this issue.
          • xapi:
            • Synchronized with XS82ECU1084: Fixes a behavior that could occur when changing masters in a pool with a large number of hosts. In this context, it was sometimes no longer possible to connect certain pool management software.
          • xcp-ng-xapi-plugins:
            • Add new service plugin to manage (start, stop, ...) XCP-ng services
            • Add a new ipmitool plugin to get information from ipmitool that:
              • Returns information about sensors
              • Returns IPMI LAN information
          • xen:
            • Synchronized with hotfix XS82ECU1082 from Citrix
              • Fix watchdog setup on Intel Sapphire Rapids and Emerald Rapids platforms.
              • Reduce PCI config reads
              • Prevent early exit from i8259 loop detection on systems with multiple IO-APICs
              • Fix incomplete reduction of PCI config reads
            • Fix XSA-467 / CVE-2025-1713

          XOSTOR:

          • sm (specific release for XOSTOR): Ensure that coalesces run correctly on LINSTOR volumes that have been previously resized.

          Test on XCP-ng 8.2

          From an up to date host:

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

          The usual update rules apply: pool coordinator first, etc.

          If you are using XOSTOR on your test servers, be sure to read our documentation on updating XOSTOR. You will need to enable an additional repo. Replace the yum update command above with this one:

          yum update --enablerepo=xcp-ng-testing,xcp-ng-linstor-testing
          

          Versions

          • intel-igc: 5.10.214-3.3.xcpng8.2
          • microcode_ctl: 2.1-26.xs29.7.xcpng8.2
          • netdata: 1.44.3-1.2.xcpng8.2
          • openvswitch: 2.5.3-2.3.14.2.xcpng8.2
          • qemu: 4.2.1-4.6.4.2.xcpng8.2
          • xapi: 1.249.41-1.1.xcpng8.2
          • xcp-ng-xapi-plugins: 1.12.0-2.xcpng8.2
          • xen: 4.13.5-9.48.2.xcpng8.2

          If you're using XOSTOR, there is also this version:

          • sm: 2.30.8-13.2.0.linstor.2.xcpng8.2

          What to test

          Normal use and anything else you want to test. The closer to your actual use of XCP-ng, the better. It would be nice if you could specify in your feedback if you are using Xostor or not.

          Test window before official release of the updates

          ~ 4/5 days

          1 Reply Last reply Reply Quote 0
          • bleaderB Offline
            bleader Vates 🪐 XCP-ng Team
            last edited by

            Home host, no XOSTOR, updated fine, no issue with my usual VMs.

            1 Reply Last reply Reply Quote 2
            • J Offline
              JeffBerntsen Top contributor
              last edited by JeffBerntsen

              Installed on my test server, not running XOSTOR, everything seems to be working fine so far.

              1 Reply Last reply Reply Quote 2
              • gduperreyG Offline
                gduperrey Vates 🪐 XCP-ng Team
                last edited by

                Update published: https://xcp-ng.org/blog/2025/03/12/march-2025-security-and-maintenance-update-for-xcp-ng-8-2-lts/

                Thank you for the tests!

                1 Reply Last reply Reply Quote 1
                • stormiS Offline
                  stormi Vates 🪐 XCP-ng Team
                  last edited by

                  New security update candidates for you to test!

                  Yet more vulnerabilities in Intel hardware, addressed in two complementary ways: patching Xen and updating Intel microcode.

                  Together with this security update, will also publish a patched XAPI to fix a minor issue with information reporting from VM to hypervisor.

                  Test on XCP-ng 8.2

                  From an up-to-date host:

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

                  The usual update rules apply: pool coordinator first, etc.

                  Versions

                  • microcode_ctl: 2.1-26.xs29.8.xcpng8.2 (weird identifier for historical reasons, but that's actually Intel microcode published by them yesterday)
                  • xen: 4.13.5-9.49.1.xcpng8.2
                  • xapi: 1.249.41-1.2.xcpng8.2

                  What to test

                  Normal use and anything else you want to test. The closer to your actual use of XCP-ng, the better.

                  Test window before official release of the updates

                  ~24h. That's an urgent one.

                  A 1 Reply Last reply Reply Quote 2
                  • J Offline
                    JeffBerntsen Top contributor
                    last edited by

                    Installed and seems to be running fine so far on my test systems.

                    1 Reply Last reply Reply Quote 3
                    • A Offline
                      Andrew Top contributor @stormi
                      last edited by

                      @stormi I needed an excuse to reboot all my hosts... Upgraded and running on stable pools. I see the Intel 11th gen new microcode. All working normally at this time.

                      1 Reply Last reply Reply Quote 1
                      • bleaderB Offline
                        bleader Vates 🪐 XCP-ng Team
                        last edited by

                        Update published: https://xcp-ng.org/blog/2025/05/14/may-2025-security-update-for-xcp-ng-8-2-8-3/

                        Thank your for the tests.

                        1 Reply Last reply Reply Quote 2
                        • olivierlambertO Offline
                          olivierlambert Vates 🪐 Co-Founder CEO
                          last edited by

                          Updated our own prod via XO RPU, everything is working fine 🙂

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post