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

    XCP-ng 8.3 updates announcements and testing

    Scheduled Pinned Locked Moved News
    178 Posts 31 Posters 16.0k Views 44 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 Online
      Andrew Top contributor @stormi
      last edited by

      @stormi Upgrade problem... I upgraded a good working busy 8.2.1 server to 8.3 (using the new ISO). The upgrade went well without error. No guest VMs were changed.

      Same issue in XO (Master 7be70) and XOA (5.107.2), so it must be an XCP issue. There are three new problems (all was working before);

      1. XCP coretemp no longer loads/works. Error: coretemp coretemp.0: Adding Core 0 failed
      2. XO Host CPU stats and Load are now reported as zero (It's a busy machine, they are not zero)
      3. XO All guest VMs report zero CPU usage. Some just report No stats. for CPU. They do have current recognized guest tools (Linux and Windows). They do report other stats (memory, network, disk).

      Other older XCP 8.3 hosts/guests are working.

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

        @Andrew Does restarting the toolstack bring the stats back?

        CC @Team-XAPI-Network

        Regarding coretemp, @r1's module doesn't work anymore with Xen 4.17. See https://github.com/xcp-ng/xcp/issues/669. A possible workaround is using IPMI readings, when available. For a better solution, there's work needed in Xen.

        (CC @Team-Hypervisor-Kernel, FYI)

        mikhail-shevtsov-wiregate created this issue in xcp-ng/xcp

        open XCP 8.3 coretemp module doesn't detect any sensors #669

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

          @stormi Got it... I missed that one for coretemp. Vates ticket opened for the XOA stats problem after 8.3 upgrade.

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

            The above issue is solved in packages that we haven't released as an update yet, that @Andrew tested.

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

              You probably saw it, but just in case: https://xcp-ng.org/blog/2025/06/16/xcp-ng-8-3-is-now-lts/

              Today marks several important updates for XCP-ng 8.3. In a nutshell:

              • It officially becomes a Long-Term Support (LTS) release, as previously announced when it was first released on October 7th, 2024.
              • We are releasing updated installation images ("ISOs") that include installer improvements and all updates published since the original release.
              • XOSTOR, our hyperconverged storage solution powered by LINSTOR, is now officially supported on XCP-ng 8.3.
              • A new, dedicated upgrade ISO is available to support upgrading from an 8.2 pool that includes a XOSTOR storage repository.
              J G 2 Replies Last reply Reply Quote 2
              • J Offline
                JeffBerntsen Top contributor @stormi
                last edited by

                @stormi @olivierlambert I did see it! Contratulations and a huge thank you for the new LTS release!

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

                  @stormi
                  Just for clarification sake (I know this might have been said before), installing patches is the same as upgrading from iso in this case ?
                  (Unlike with previous update where it was mandatory to upgrade using iso)

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

                    @gb.123 Yes. If you think it's not clear in the blog post, I'll think how I can word it.

                    Current wording:

                    This announcement does not represent a new release. It applies to the existing XCP-ng 8.3.

                    If you're already running XCP-ng 8.3, you're on the LTS version. There's no need for a full upgrade. Standard package updates will keep your system current.

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

                      Congratulations to all the staff at Vates at getting XCP-ng version 8.3 to the LTS stage.

                      1 Reply Last reply Reply Quote 1
                      • T Offline
                        TrapoSAMA
                        last edited by

                        Hi!!

                        Then 8.3 dont show LTS flag in the console?

                        Thx

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

                          @TrapoSAMA No, as with 8.2, this isn't something displayed in the console.
                          Since it doesn't indicate that an updated 8.2 is actually 8.2.1, only the major version is displayed. We have the same behavior here.

                          However, as with many other products, this is clearly displayed on the XCP-ng homepage, in addition to the announcement on the blog.

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

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

                            Since it doesn't indicate that an updated 8.2 is actually 8.2.1, only the major version is displayed.

                            Not a very good example actually 😄 (but what's true is that for 8.2 we didn't add a "LTS" mention next to the version number in the system either).

                            37210535-b72a-49e3-aeb0-ad59cbbdd82e-image.png

                            But yes, we decided not to increment the version number for XCP-ng 8.3.0. That breaks compatibility with some third party software because they wouldn't recognize a "8.3.1".

                            However we're working on a secondary version identifier that would allow you to know your precise patch level.

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