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

    XCP-ng 8.3 updates announcements and testing

    Scheduled Pinned Locked Moved News
    599 Posts 53 Posters 303.7k Views 74 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.
    • B Offline
      bufanda @rzr
      last edited by

      @rzr Installed on my 2 node lab pool, so far no issues.

      1 Reply Last reply Reply Quote 2
      • TeddyAstieT Online
        TeddyAstie Vates 🪐 XCP-ng Team Xen Guru @Andrew
        last edited by TeddyAstie

        @Andrew said:
        HP DL G8 Intel E5-2673 v2 shows 64 CPUs. The actual CPUs show correctly, the higher ones (that don't exist) show [CPUxx] Unable to fetch temperature (19 - No such device)

        Machines with hotpluggable CPUs are a pretty tricky case, the logic tries up to "maximum possible CPU" and fails here because the CPU is not online (No such device error). That doesn't prevent the temperature from getting fetched for CPU that exists.
        I can try to add a check to hide this specific error, so it's doesn't create noise for offline CPUs on such machines.

        1 Reply Last reply Reply Quote 1
        • S Offline
          ScarfAntennae
          last edited by ScarfAntennae

          Temps seem to be working on i5-10500T:

          [11:46 delta-2 ~]# xenpm get-core-temp
          Package0: 57°C
          CPU0: 56°C
          CPU2: 57°C
          CPU4: 56°C
          CPU6: 56°C
          CPU8: 55°C
          CPU10: 57°C
          

          As this is my first time installing these update candidates, is there no other action required after doing:

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

          Meaning I am not permanently in testing mode now? Next yum update should just pull the latest stable versions?

          rzrR 1 Reply Last reply Reply Quote 2
          • rzrR Offline
            rzr Vates 🪐 XCP-ng Team @ScarfAntennae
            last edited by rzr

            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.

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

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

              S 1 Reply Last reply Reply Quote 3
              • X Offline
                XCP-ng-JustGreat
                last edited by

                Updated my four host home lab pool with latest batch of updates with no observed issues.

                1 Reply Last reply Reply Quote 2
                • psafontP Offline
                  psafont Vates 🪐 XAPI & Network Team @rzr
                  last edited by stormi

                  @rzr We've found a regression in the VM revert with the new version of xapi (26.1.11)

                  The CD VBDs of the pre-revert are not removed when reverting, this means that the reverted VM usually ends up with duplicated VBDs for CDs.

                  We've verified a fix for it and we're integrating it as soon as possible. This means that this test cycle will take longer.

                  1 Reply Last reply Reply Quote 2
                  • S Offline
                    ScarfAntennae @stormi
                    last edited by

                    @rzr @stormi Perfect, thanks for clarifying!

                    rzrR 1 Reply Last reply Reply Quote 0
                    • rzrR Offline
                      rzr Vates 🪐 XCP-ng Team @ScarfAntennae
                      last edited by stormi

                      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

                      acebmxerA 1 Reply Last reply Reply Quote 2
                      • acebmxerA Offline
                        acebmxer @rzr
                        last edited by

                        @rzr

                        Updates applied...

                        Updated:
                          forkexecd.x86_64 0:26.1.11-1.2.xcpng8.3                         kexec-tools.x86_64 1:2.0.15-21.1.xcpng8.3                           
                          message-switch.x86_64 0:26.1.11-1.2.xcpng8.3                    qcow-stream-tool.x86_64 0:26.1.11-1.2.xcpng8.3                      
                          rrdd-plugins.x86_64 0:26.1.11-1.2.xcpng8.3                      sm-cli.x86_64 0:26.1.11-1.2.xcpng8.3                                
                          squeezed.x86_64 0:26.1.11-1.2.xcpng8.3                          varstored-guard.x86_64 0:26.1.11-1.2.xcpng8.3                       
                          vhd-tool.x86_64 0:26.1.11-1.2.xcpng8.3                          wsproxy.x86_64 0:26.1.11-1.2.xcpng8.3                               
                          xapi-core.x86_64 0:26.1.11-1.2.xcpng8.3                         xapi-nbd.x86_64 0:26.1.11-1.2.xcpng8.3                              
                          xapi-rrd2csv.x86_64 0:26.1.11-1.2.xcpng8.3                      xapi-storage-script.x86_64 0:26.1.11-1.2.xcpng8.3                   
                          xapi-tests.x86_64 0:26.1.11-1.2.xcpng8.3                        xapi-xe.x86_64 0:26.1.11-1.2.xcpng8.3                               
                          xcp-networkd.x86_64 0:26.1.11-1.2.xcpng8.3                      xcp-rrdd.x86_64 0:26.1.11-1.2.xcpng8.3                              
                          xenopsd.x86_64 0:26.1.11-1.2.xcpng8.3                           xenopsd-cli.x86_64 0:26.1.11-1.2.xcpng8.3                           
                          xenopsd-xc.x86_64 0:26.1.11-1.2.xcpng8.3                       
                        
                        Complete!
                        

                        Will continue to test.

                        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