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

    XCP-ng 8.3 updates announcements and testing

    Scheduled Pinned Locked Moved News
    197 Posts 31 Posters 20.6k 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.
    • B Offline
      bufanda @dthenot
      last edited by

      @dthenot No worries, just wanted to make sure I understand the expected behavior when I had the qcow2 patches installed.

      dthenotD 1 Reply Last reply Reply Quote 0
      • dthenotD Offline
        dthenot Vates 🪐 XCP-ng Team @bufanda
        last edited by dthenot

        @bufanda You just need to make sure to have a sm and blktap qcow2 version.
        Otherwise, having a normal sm version would drop the QCOW2 VDI from the XAPI database and you would lose VBD to VM aswell as name of VDI.
        So it could be painful depending on how much you have 😬
        But in the case, you would install a non QCOW2 sm version, you would only lose the QCOW2 from DB, those would not be deleted or anything. Reinstalling a QCOW2 version then rescanning the SR would make them re-appear. But then you would have to identify them again (lost name-label) and relink them to VM.
        We try to keep our QCOW2 version on top of the testing branch of XCP-ng but we could miss it 🙂

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

          @dthenot Only have 2 Test VMs currently not running with qcow2. Nothing production and nothing crucial. It's a lab pool. As I said just to understand the behavior when I test the new updates. But thanks for the details. Really appreciated

          1 Reply Last reply Reply Quote 2
          • J Offline
            JeffBerntsen Top contributor
            last edited by

            Installed and working on my lab test machine, HP ProLiant DL165 G7 with AMD Opteron 6136 CPU and 32 GB of RAM.

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

              @gduperrey Installed and running on a few hosts. Good so far.

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

                Updates published: https://xcp-ng.org/blog/2025/07/03/july-2025-security-and-maintenance-update-for-xcp-ng-8-3-lts/

                Thank you for the tests!

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

                  Sorry to join the bandwagon late this time, but i got these errors while booting:

                  [    0.826901] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.GPP2.WWAN], AE_NOT_FOUND (20180810/dswload2-160)
                  [    0.826908] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20180810/psobject-221)
                  [    0.826910] ACPI Error: Ignore error and continue table load (20180810/psobject-604)
                  [    0.826912] ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-543)
                  [    0.827236] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.GPP2.WWAN], AE_NOT_FOUND (20180810/dswload2-160)
                  [    0.827239] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20180810/psobject-221)
                  [    0.827241] ACPI Error: Ignore error and continue table load (20180810/psobject-604)
                  [    0.827242] ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-543)
                  [    0.827245] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.GPP5.EWPM], AE_ALREADY_EXISTS (20180810/dswload2-316)
                  [    0.827248] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221)
                  [    0.827250] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.GPP5._PRW], AE_ALREADY_EXISTS (20180810/dswload2-316)
                  [    0.827252] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221)
                  [    0.827254] ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-543)
                  [    0.827257] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.GPP5.RTL8._S0W], AE_ALREADY_EXISTS (20180810/dswload2-316)
                  [    0.827259] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221)
                  

                  I think this is after the new update

                  Processor : AMD Ryzen 7 7840HS

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

                    Hi,

                    It's just an ACPI error, it shouldn't be a problem.

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

                      @olivierlambert

                      I agree. But just thought I should report nevertheless.

                      Update: This seems to be related to 7840HS motherboard. I tried it on another AMD Ryzen 7945HX but did not get this error.

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

                        It's clearly due to the motherboard, yes. Mostly buggy BIOS/UEFI and ACPI tables. This world is like the far west.

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

                          New security and maintenance update candidate

                          A new XSA (Xen Security Advisory) was published on the 8th of July, related to hardware vulnerabilities in several AMD CPUS. Updated microcode mitigate it, and Xen is updated to adapt to the changes in the CPU features. We also publish other non-urgent updates which we had in the pipe for the next update release.


                          Security updates

                          • amd-microcode:
                            • Update to 20250626-1 as redistributed by XenServer.
                          • xen-*:
                            • Fix XSA-471 - New speculative side-channel attacks have been discovered, affecting systems running all versions of Xen and AMD Fam19h CPUs (Zen3/4 microarchitectures). An attacker could infer data from other contexts. There are no current mitigations, but AMD is producing microcode to address the issue, and patches for Xen are available. These attacks, named Transitive Scheduler Attacks (TSA) by AMD, include CVE-2024-36350 (TSA-SQ) and CVE-2024-36357 (TSA-L1).

                          Maintenance updates

                          • http-nbd-transfer:
                            • Fix missing import exceptions in log files.
                            • Fix a potential HA startup failure with LINSTOR.
                          • xo-lite: update to 0.12.1
                            • [Charts] Fix tooltip overflow when too close to the edge
                            • [Host/VM/Dashboard] Fix timestamp on some charts

                          Test on XCP-ng 8.3

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

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

                          Versions:

                          • amd-microcode: 20250626-1.1.xcpng8.3
                          • http-nbd-transfer: 1.7.0-1.xcpng8.3
                          • xen: 4.17.5-15.1.xcpng8.3
                          • xo-lite: 0.12.1-1.xcpng8.3

                          What to test

                          Normal use and anything else you want to test.

                          Test window before official release of the updates

                          ~2 days.

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

                            And fixes for XCP-ng 8.2 are coming but they require more work to backport the patches.

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

                              @stormi

                              Tested on my usual Intel test servers you've seen me post in this thread in the past as well as a 2 host AMD Epyc pool,(HP DL325 Gen10) rolling pool reboot worked as expected, hosts rebooted without issue, backups and replication appear to function as usual.

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

                                @gduperrey Installed and running on Intel systems, and Zen3 system that sees the microcode update.

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