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

    XCP-ng 8.3 updates announcements and testing

    Scheduled Pinned Locked Moved News
    231 Posts 31 Posters 60.0k Views 45 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.
    • olivierlambertO Online
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by

      Updated and enabled (but on an Intel machine so far). I think I will enable it on our prod with the new config, this won't hurt 🙂 (full EPYC)

      1 Reply Last reply Reply Quote 1
      • B Offline
        bufanda @gduperrey
        last edited by

        Installed on a 2 Node pool consisting of 2
        HP EliteDesk 300 G3 Mini with

        • 1x i7 6700T & 1x i5 6500T
        • 32GB RAM each
        • NFS VM SR
        • iSCSI VM SR
        • various SMB ISO SR

        VMs migrated during reboot withput issues, also no issues with migration after updates completed with all nodes rebooted. Alos no issues found with VMs. Primarily AlmaLinux 9 and FreeBSD 13.

        1 Reply Last reply Reply Quote 1
        • G Offline
          gb.123 @gduperrey
          last edited by gb.123

          @gduperrey
          @olivierlambert

          First of all ...... a BIG THANK YOU for this patch !

          Tested on Minisforum AMD 7945HX based pc; and I can confirm that XCP-ng boots with ACPI PSS & C Cores as mentioned in this post and it works with both options enabled.

          So excited that I have tested this only and replied before testing other things.. 😃

          UPDATE :
          While updating this, I actually had to do 2 updates (last stable update patch of 7 files + this one)

          After this installation, GPU (Nvidia) passthrough completely seems to be broken. Before the update(s) the host had to be turnoff completely, power cable had to be removed and then replugged to reset the graphics card (which used to work as I was able to run the card); but now attaching the graphics card to VM makes the VM hang on VM boot and at times, the host is also abruptly restarted (as if someone as pressed the HW reset button).

          I am not sure whether the problem is in this update or the last stable one; but graphics card reset for Nvidia ( I think it has to do with ACPI reset ) still remains a problem.

          Would be great if you guys can look into this.

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

            Updated on our prod cluster, works very well (full EPYC)

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

              @gduperrey I updated my little AMD Ryzen 5 5600U (Zen3) and it's running great!

              As for the important VM to VM network performance, using Debian 13 and iperf3 single thread, before (update not enabled) is about 7.2-8Gb/sec. After the update (xen-platform-pci-bar-uc=false) I get about 10.1-13Gb/sec. So that's about a 40-60% improvement. This brings it in line with similar small Intel systems.

              I did not see any change (or problem) setting it on my small test Intel system (getting about 10.1-10.8Gb/sec).

              FYI: Remember, after the config change and xe-toolstack-restart, restart the VMs!

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

                Yeah I had to stop then start the VM to enjoy the new performance. On my end, iperf (not iperf3) bring even more perf on my setup, especially with multiple threads (-P4 and -P8 gave more than 100% boost)

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

                  New update candidate for you to test!

                  A new non-urgent update is ready for user testing before a future collective release. Below are the details.

                  A bug was found in the Emergency Network Reset due to desynchronisation between xsconsole and XAPI. This issue prevented the Emergency Network Reset from working at all. This update includes the fixes from the upstream xsconsole project to fix it.


                  Maintenance updates

                  • xsconsole
                    • Backport sync of network reset trigger file path with XAPI to fix emergency network reset
                    • Backport fix for pool.conf IPv6 to avoid IPv6 truncation

                  Test on XCP-ng 8.3

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

                  Reboot is not strictly necessary, but the xsconsole instance running on the first virtual terminal of your host won't be restarted otherwise. If you do not reboot, make sure to start xsconsole from another terminal after the update.

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

                  Versions:

                  • xsconsole: 11.0.8-1.2.xcpng8.3

                  What to test

                  Normal xsconsole usage, is still useful feedback. However, if possible, the most helpful test would be performing an Emergency Network Reset through xsconsole, making actual configuration changes and verifying that they are correctly applied after reboot.

                  Test window before official release of the updates

                  None defined, but early feedback is always better than late feedback, which is in turn better than no feedback 🙂

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

                    New update candidate for you to test!

                    A new non-urgent update is ready for user testing before a future collective release. Below are the details.


                    Maintenance updates

                    • broadcom-bnxt-en: Update driver to version 1.10.3_232.0.155.5

                    Test on XCP-ng 8.3

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

                    A reboot is preferable to load the new version of the driver.

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

                    Versions:

                    • broadcom-bnxt-en: 1.10.3_232.0.155.5-1.xcpng8.3

                    What to test

                    Normal use and anything else you want to test.

                    Test window before official release of the updates

                    None defined, but early feedback is always better than late feedback, which is in turn better than no feedback 🙂

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

                      Updates published: https://xcp-ng.org/blog/2025/09/01/september-2025-maintenance-update-for-xcp-ng-8-3/

                      Thank you for the tests!

                      M F 2 Replies Last reply Reply Quote 1
                      • M Offline
                        manilx @gduperrey
                        last edited by

                        @gduperrey Installed at HomeLab. No issues.
                        Running via
                        yum clean metadata ; yum update

                        J 1 Reply Last reply Reply Quote 1
                        • J Offline
                          john.c @manilx
                          last edited by

                          @manilx said in XCP-ng 8.3 updates announcements and testing:

                          @gduperrey Installed at HomeLab. No issues.
                          Running via
                          yum clean metadata ; yum update

                          You must have been looking forward to this improvement for quite a while. Once it reaches the point where it can be rolled into production, your AMD Epyc servers will get to see a boost, the Linux guests any way.

                          M 2 Replies Last reply Reply Quote 0
                          • M Offline
                            manilx @john.c
                            last edited by

                            @john.c Will apply to business EPYC servers right away 😊

                            1 Reply Last reply Reply Quote 2
                            • M Offline
                              manilx @john.c
                              last edited by

                              @john.c Updated our 2 production pools, with RPU.

                              RPU emptied the master, rebooted BUT then nothing else.
                              It should have moved all VM's to the other host, patched/rebooted and then migrating the VM's where they were.
                              This did not happen. I had to manually empty the other hosts, patch, reboot and migrate the VM's.

                              G 1 Reply Last reply Reply Quote 0
                              • F Offline
                                flakpyro @gduperrey
                                last edited by

                                @gduperrey Installed on about 50 servers across various pools and remote sites. No issues. Ran a couple backup jobs as well which completed without issue.

                                1 Reply Last reply Reply Quote 2
                                • G Offline
                                  Greg_E @manilx
                                  last edited by

                                  @manilx

                                  Once in a while my rpu will do this, then I handle it manually. Been happening more often since the 8.3 upgrade, but not enough to post about it yet since we are only a couple of updates into the LTS. Still watching though and will probably do this patch on wednesday.

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