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

    XCP-ng 8.3 updates announcements and testing

    Scheduled Pinned Locked Moved News
    669 Posts 56 Posters 571.1k Views 75 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.
    • marcoiM Offline
      marcoi
      last edited by

      for the latest updates. the test pool didnt move the vms when i went to reboot. so i moved them manually. rebooted master, move vms back patched and reboot 2nd test server in the pool.
      Skipped trying rolling reboot in prod and followed the same process. both pools went well without other issues.

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

        New maintenance update candidates for XCP-ng 8.3 LTS

        This batch of updates focuses on storage bug fixes and performance improvements.

        What changed

        Storage

        • blktap:
          When CBT is enabled, an issue occurred where tapdisk opened cbtlog instead of the primary QCOW2 image. This previously caused commit operations (ENOTSUPP) and leaf-coalesce routines to fail, resulting in excessive storage consumption on the SR. Tapdisk now correctly bypasses the cbtlog image to allow proper coalescing.

        • sm: Fix a bug where the coalesce on a secondary host of a QCOW2 VDI on LVMSR could corrupt LVM metadata and would need manual intervention to restore them.

        • xapi:
          - Migration speeds are now improved for sparse QCOW2-backed VDIs, as empty sectors are no longer transferred.
          - Preserve VDI tags on migration. This is a foundational fix for kubernetes integration.

        Versions

        • blktap: 3.55.5-9.3.xcpng8.3 -> 3.55.5-9.4.xcpng8.3
        • sm: 3.2.12-23.4.xcpng8.3 -> 3.2.12-23.5.xcpng8.3
        • xapi: 26.1.16-1.1.xcpng8.3 -> 26.1.16-1.2.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
        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

        ~24 hrs

        We would like to thank users who shared feedback since our last call for testing: @Andrew, @JeffBerntsen, @MajorP93, @XCP-ng-JustGreat, @acebmxer, @bufanda, @flakpyro

        B acebmxerA M 3 Replies Last reply Reply Quote 4
        • B Offline
          bufanda @gleh
          last edited by

          @gleh installed on my lab pool. Haven’t seen any issues so far.

          1 Reply Last reply Reply Quote 4
          • acebmxerA Offline
            acebmxer @gleh
            last edited by

            @gleh

            Installed...

            Updated:
              blktap.x86_64 0:3.55.5-9.4.xcpng8.3                forkexecd.x86_64 0:26.1.16-1.2.xcpng8.3                
              message-switch.x86_64 0:26.1.16-1.2.xcpng8.3       qcow-stream-tool.x86_64 0:26.1.16-1.2.xcpng8.3         
              rrdd-plugins.x86_64 0:26.1.16-1.2.xcpng8.3         sm.x86_64 0:3.2.12-23.5.xcpng8.3                       
              sm-cli.x86_64 0:26.1.16-1.2.xcpng8.3               sm-fairlock.x86_64 0:3.2.12-23.5.xcpng8.3              
              squeezed.x86_64 0:26.1.16-1.2.xcpng8.3             varstored-guard.x86_64 0:26.1.16-1.2.xcpng8.3          
              vhd-tool.x86_64 0:26.1.16-1.2.xcpng8.3             wsproxy.x86_64 0:26.1.16-1.2.xcpng8.3                  
              xapi-core.x86_64 0:26.1.16-1.2.xcpng8.3            xapi-nbd.x86_64 0:26.1.16-1.2.xcpng8.3                 
              xapi-rrd2csv.x86_64 0:26.1.16-1.2.xcpng8.3         xapi-storage-script.x86_64 0:26.1.16-1.2.xcpng8.3      
              xapi-tests.x86_64 0:26.1.16-1.2.xcpng8.3           xapi-xe.x86_64 0:26.1.16-1.2.xcpng8.3                  
              xcp-networkd.x86_64 0:26.1.16-1.2.xcpng8.3         xcp-rrdd.x86_64 0:26.1.16-1.2.xcpng8.3                 
              xenopsd.x86_64 0:26.1.16-1.2.xcpng8.3              xenopsd-cli.x86_64 0:26.1.16-1.2.xcpng8.3              
              xenopsd-xc.x86_64 0:26.1.16-1.2.xcpng8.3
            
            1 Reply Last reply Reply Quote 3
            • M Offline
              MajorP93 @gleh
              last edited by

              @gleh Installed those RC packages in my test environment.
              Tested basic operation. Looks good so far.
              (Booted, all 3 SR connected, VMs able to start, both VHD and QCOW2)
              Best regards

              F 1 Reply Last reply Reply Quote 3
              • F Offline
                flakpyro @MajorP93
                last edited by

                Installed on my usual hosts without issues. I am only making limited use of QCOW2 however.

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

                  Thank you everyone for your tests and your feedback!

                  The updates are live now: https://xcp-ng.org/blog/2026/08/27/august-2026-updates-2-for-xcp-ng-8-3-lts/

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

                    @gduperrey Installed and running. Rolling pool update worked.

                    M 1 Reply Last reply Reply Quote 1
                    • M Offline
                      mthird @Andrew
                      last edited by

                      First time rolling update worked for my pool. Woot!

                      M 1 Reply Last reply Reply Quote 0
                      • M Offline
                        mthird @mthird
                        last edited by

                        Spoke to soon. While the updates succeeded, one of the nodes is rebooting every few minutes due to an HA self-fence.

                        1 Reply Last reply Reply Quote 0

                        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
                        • First post
                          Last post