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

    XCP-ng 8.3 updates announcements and testing

    Scheduled Pinned Locked Moved News
    211 Posts 31 Posters 24.5k 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.
    • B Offline
      bufanda @andriy.sultanov
      last edited by

      @andriy.sultanov
      Same issue after another reboot. The stats on host just flatline. No CPU usage or anything.
      See screenshot
      f58c86b0-ac72-4a6c-a554-ecee918e4db7-image.png

      I attached log files
      daemon.log.txt xcp-rrdd-plugins.log.txt xensource.log.txt

      A 1 Reply Last reply Reply Quote 0
      • A Offline
        andriy.sultanov Vates 🪐 XAPI & Network Team @bufanda
        last edited by andriy.sultanov

        @bufanda Thanks!
        Hmm, can't see anything suspicious either in your logs or @abudef's

        Since you said it reproduces if you reboot the host again, I'd really appreciate if you could send the result of rrd2csv running for 30 seconds or so on a system that doesn't have the stats working - so before any toolstack restarts.

        B G 2 Replies Last reply Reply Quote 0
        • B Offline
          bufanda @andriy.sultanov
          last edited by

          @andriy.sultanov
          I ran it for a minute.

          rrd2csv.txt

          1 Reply Last reply Reply Quote 0
          • G Offline
            Greg_E @andriy.sultanov
            last edited by

            @andriy.sultanov

            If still needed, I can probably get you the rrd2csv next week, I need to unrack my system and move it to a new mobile rack. A large expense that I'm not happy to have to do, but now needed going forward (it's a work thing, where I prototype workflows for my production system) 😠 😡 😣

            A 1 Reply Last reply Reply Quote 0
            • A Offline
              andriy.sultanov Vates 🪐 XAPI & Network Team @Greg_E
              last edited by

              @Greg_E Thanks, but that will not be necessary - I think I've figured out where the problem lies now. Good luck with the move 🙂

              G 1 Reply Last reply Reply Quote 1
              • G Offline
                Greg_E @andriy.sultanov
                last edited by

                @andriy.sultanov

                The move is more about spending yet more personal money for something that is primarily used for learning what I need to know for work (a rack, UPS, and some odds and ends at $800). Or half of it is, half of it is a VMware system and that's to let me learn what I need to leave this job and find one that pays more. And then move that work to something easier to use that costs less. Still amazed at how many places just took the price increase and are still not making plans to move to something else, even if they are cutting core counts in half to save half of that new money. But I'm also seeing that the general trend in IT around where I live is to get into a Silo, and never ever take on another task to fill a need. This way you never want to move laterally to other products, just keep doing the same things the same ways until management gets tired of hearing "we can't do that" and fires everyone to replace them with an MSP (or other contractor).

                So for the off topic rant, feeling salty again today.

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

                  New security update candidates for you to test!

                  We're still working on the updates that you started testing (and a few more), but right now there's an emergency: a security update.

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

                  Test on XCP-ng 8.3

                  From an up-to-date host, or a host on which previous update candidates had been installed. Both fit.

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

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

                  Versions

                  • intel-microcode: 20250501-1.xcpng8.3
                  • xen: 4.17.5-13.1.xcpng8.3

                  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.

                  P G A 3 Replies Last reply Reply Quote 3
                  • P Offline
                    ph7 @stormi
                    last edited by

                    @stormi
                    Stats still not good
                    Only rebooted
                    a9e73f4f-5bde-4e1e-a82b-abc8ce2cb45b-image.png

                    After Restart tool stack
                    1990a307-c40c-440d-8b9b-d2171cc336a8-image.png

                    A 1 Reply Last reply Reply Quote 0
                    • A Offline
                      andriy.sultanov Vates 🪐 XAPI & Network Team @ph7
                      last edited by

                      @ph7 This update only covers the security issue described above. Fix for the stats issue will roll out later.

                      F P 2 Replies Last reply Reply Quote 3
                      • F Online
                        flakpyro @andriy.sultanov
                        last edited by

                        @stormi installed on the same test machines i have the other batch of updates installed on. No issues after a reboot.

                        1 Reply Last reply Reply Quote 2
                        • P Offline
                          ph7 @andriy.sultanov
                          last edited by

                          @andriy.sultanov
                          Sorry, if I only could read...
                          Anyhow, My updated host running on intel seems to work just fine.

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

                            @stormi

                            My lab is down for a few days, so no testing for me. And it is AMD so maybe not useful. I probably won't be back running until Friday.

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

                              @Greg_E Thanks for letting me know. It is useful to make sure that it's still working on any kind of hardware, but your lab won't participate this time 🙂

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

                                Installed the patches on my lab pool and both hosts are up and running and no issues so far.

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

                                  Latest urgent updates installed on 3-node Intel pool. Everything is working as before including the pre-production code "no stats" issue, but that still resolves following xe-toolstack-restart command. Since it is currently Microsoft patch Tuesday here, the latest Windows 11-24H2 2025-05 cumulative update was installed to VM along with various Linux VM updates and live VM host migrations. All working well including latest af03c Xen Orchestra from source (XOS).

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

                                    @stormi Upgraded my test 8.3 hosts, several Intel and AMD Zen 3. So far, so good.

                                    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.

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

                                        @bleader

                                        I see this for my 8.2 pool this morning, I'll kick it off when we all go into a meeting so it will be done when we finish.

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

                                          @Greg_E Updated 3 pools @business (3 Intel hosts, 2 EPYC hosts) all OK with stats. Also 1 pool @home (2 Intel Protectlis) all OK with stats.

                                          1 Reply Last reply Reply Quote 1
                                          • A Offline
                                            archw
                                            last edited by

                                            I updated the master pool...all went well. I updated one of the other hosts. After it rebooted, I got lots of messages about "Async.VM.clean_shutdown: 8%" on the various VMs.

                                            My bad....XO was a two builds behind and well as XO was not up to date.

                                            I updated to commit 95e72 and updated XOA version to 5.106.2 and all is well.

                                            User error on my part but I hope this helps someone.

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