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

    XCP-ng 8.3 public alpha 🚀

    Scheduled Pinned Locked Moved News
    264 Posts 43 Posters 176.5k Views 39 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.
    • stormiS Offline
      stormi Vates 🪐 XCP-ng Team @rRobbie
      last edited by

      @rRobbie Thanks. This look like the same crash as discussed just above, with a candidate for a fix provided, if you want to test it. It should be included in the next update of the Xen packages anyway.

      R R 2 Replies Last reply Reply Quote 1
      • R Offline
        ravenet @stormi
        last edited by

        @stormi Here's results from one of my lab servers. I'll run on some newer hardware next week.

        Asus KGPE-D16, Opteron 6328, 128GB ram.

        Combined test results:
test-hvm32-selftest                      SUCCESS
test-hvm32pae-selftest                   SUCCESS
test-hvm32pse-selftest                   SUCCESS
test-hvm64-selftest                      SUCCESS
test-pv64-selftest                       SUCCESS
Combined test results:
test-pv64-cpuid-faulting                 SKIP
test-pv64-pv-fsgsbase                    SKIP
test-hvm32-umip                          SKIP
test-hvm64-umip                          SKIP
test-pv64-xsa-167                        SKIP
test-pv64-xsa-182                        SKIP
3

        CPU Policy unit tests
Testing CPU vendor identification:
Testing CPUID serialise success:
Testing CPUID deserialise failure:
Testing CPUID out-of-range clearing:
Testing MSR serialise success:
Testing MSR deserialise failure:
Testing policy compatibility success:
Testing policy compatibility failure:
Done: all ok
0
        1 Reply Last reply Reply Quote 0
        • olivierlambertO Offline
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

          @ravenet said in XCP-ng 8.3 public alpha 🚀:

          Opteron 6328

          Wow! It's been a while I didn't heard about those ones 😄 11 years old CPU, and still usable, impressive 😄

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

            @stormi

            Here's two more old servers that I have still running:

            Supermicro H8DGU
AMD Opteron 6380

CPU Policy unit tests
Testing CPU vendor identification:
Testing CPUID serialise success:
Testing CPUID deserialise failure:
Testing CPUID out-of-range clearing:
Testing MSR serialise success:
Testing MSR deserialise failure:
Testing policy compatibility success:
Testing policy compatibility failure:
Done: all ok
Result 0

Combined test results:
test-hvm32-selftest                      SUCCESS
test-hvm32pae-selftest                   SUCCESS
test-hvm32pse-selftest                   SUCCESS
test-hvm64-selftest                      SUCCESS
test-pv64-selftest                       SUCCESS

Combined test results:
test-pv64-cpuid-faulting                 SKIP
test-pv64-pv-fsgsbase                    SKIP
test-hvm32-umip                          SKIP
test-hvm64-umip                          SKIP
test-pv64-xsa-167                        SKIP
test-pv64-xsa-182                        SKIP
Result 3

            HP DL360 G5
Intel E5450

CPU Policy unit tests
Testing CPU vendor identification:
Testing CPUID serialise success:
Testing CPUID deserialise failure:
Testing CPUID out-of-range clearing:
Testing MSR serialise success:
Testing MSR deserialise failure:
Testing policy compatibility success:
Testing policy compatibility failure:
Done: all ok
Result 0

Combined test results:
test-hvm32-selftest                      SUCCESS
test-hvm32pae-selftest                   SUCCESS
test-hvm32pse-selftest                   SUCCESS
test-hvm64-selftest                      SUCCESS
test-pv64-selftest                       SUCCESS

Executing 'xl create -p tests/invlpg/test-hvm32-invlpg~hap.cfg'
Parsing config from tests/invlpg/test-hvm32-invlpg~hap.cfg
libxl: error: libxl_create.c:604:libxl__domain_make: domain creation fail: Invalid argument
libxl: error: libxl_create.c:1102:initiate_domain_create: cannot make domain: -3

Error: Failed to create VM
Result 1

            I guess the old G5 is getting a little too old to keep running... but it does still work.

            A 1 Reply Last reply Reply Quote 1
            • R Offline
              ravenet
              last edited by ravenet

              @stormi
              Here's a Ryzen 1700 on Asus TUF B550

              Combined test results:
test-hvm32-selftest                      SUCCESS
test-hvm32pae-selftest                   SUCCESS
test-hvm32pse-selftest                   SUCCESS
test-hvm64-selftest                      SUCCESS
test-pv64-selftest                       SUCCESS
Combined test results:
test-pv64-cpuid-faulting                 SKIP
test-hvm32-umip                          SKIP
test-hvm64-umip                          SKIP
test-pv64-xsa-167                        SKIP
test-pv64-xsa-182                        SKIP
3

              CPU Policy unit tests
Testing CPU vendor identification:
Testing CPUID serialise success:
Testing CPUID deserialise failure:
Testing CPUID out-of-range clearing:
Testing MSR serialise success:
Testing MSR deserialise failure:
Testing policy compatibility success:
Testing policy compatibility failure:
Done: all ok
0
              1 Reply Last reply Reply Quote 1
              • A Offline
                andyhhp Xen Guru @Andrew
                last edited by

                @Andrew Intel E5450, that's very retro.

                It's also first-gen VT-x and doesn't have HAP, which is why the test that is looking explicitly for HAP doesn't work.

                As a stopgap, remove hap from the VARY-CFG := hap shadow line in tests/invlpg/Makefile and rebuild. In the meantime I'll try to figure out a nice way to cope with this.

                A 1 Reply Last reply Reply Quote 1
                • A Offline
                  Andrew Top contributor @andyhhp
                  last edited by

                  @stormi @andyhhp Yes, it is very retro.... it was my first XCP-ng host (because it was free).

                  HP DL360 G5
Intel E5450

HAP test disabled

CPU Policy unit tests
Testing CPU vendor identification:
Testing CPUID serialise success:
Testing CPUID deserialise failure:
Testing CPUID out-of-range clearing:
Testing MSR serialise success:
Testing MSR deserialise failure:
Testing policy compatibility success:
Testing policy compatibility failure:
Done: all ok
Result 0

Combined test results:
test-hvm32-selftest                      SUCCESS
test-hvm32pae-selftest                   SUCCESS
test-hvm32pse-selftest                   SUCCESS
test-hvm64-selftest                      SUCCESS
test-pv64-selftest                       SUCCESS

Combined test results:
test-pv64-cpuid-faulting                 SKIP
test-pv64-pv-fsgsbase                    SKIP
test-hvm32-umip                          SKIP
test-hvm64-umip                          SKIP
test-pv64-xsa-167                        SKIP
test-pv64-xsa-182                        SKIP
Result 3
                  1 Reply Last reply Reply Quote 0
                  • R Offline
                    rRobbie @stormi
                    last edited by rRobbie

                    @stormi Hello.

                    Just installed the latest patches to the XCP-NG host and did the test again.

                    Not sure the fix was already included in the packages... So just for your info 😊

                    Intel NUC11ATKC4 with N5105 and 32GB of RAM

                    [21:55 xcp-ng-1 xtf]# yum upgrade
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-base: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-updates: mirrors.xcp-ng.org
No packages marked for update
[21:55 xcp-ng-1 xtf]# ./xtf-runner -aqq --host ; echo Result: $?
Combined test results:
test-hvm64-lbr-tsx-vmentry               CRASH
test-pv64-xsa-167                        SKIP
test-pv64-xsa-182                        SKIP
Result: 6
                    stormiS 1 Reply Last reply Reply Quote 0
                    • stormiS Offline
                      stormi Vates 🪐 XCP-ng Team @rRobbie
                      last edited by

                      @rRobbie It's not included yet.

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

                        So, a few days ago, we pushed the following updates to XCP-ng 8.3:

                        • guest-templates-json-*: adds Ubuntu Jammy template.
                        • XAPI updated to version 22.34. Among other things:
                          • the host's webpage, when accessed on port 80, now automatically redirects to HTTPS on port 443 rather than displaying a 403 Forbidden error. Note that in a future update, port 80 may be completely closed instead.
                          • I haven't checked yet, but I think this removes the immortal pending xapi events task that a previous update added, while keeping the perk of the previous change, which removed a lot of spurious "INVALID_SESSION" errors from xensource.log (almost anyone having had a look at the logs has seen them).
                        • xcp-featured: was simply rebuilt for the updated XAPI
                        • microsemi-smartpqi vendor driver updated to 2.1.20_035
                        • sudo patched for security issue

                        No need to re-run the Xen tests if you ran them previously, as Xen wasn't updated in this round of updates. If you haven't yet, then the "let's cover the largest range of hardware possible" action continues.

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

                          A test was recently pushed to XTF's repository which may crash a host whose hardware is vulnerable to XSA-304 (hardware vulnerability related to EPT superpages).

                          There are two modes in Xen regarding EPT superpages, fast vs secure, and XCP-ng defaults to fast due to the big performance hit secure would have by default on affected hardware. The vulnerability may allow an HVM guest to crash the host, and this is what the test demonstrates.

                          I've updated the small Xen testing guide above with instructions to switch to secure mode before running the tests, if you want to avoid the crash in case your host is vulnerable.

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

                            Here's the results on my new Intel NUC11 Pool (tested on one of the two identical NUCs)

                            Host: Intel Nuc11TNK
                            CPU: i5-1135G7
                            RAM: 64GB G.SKILL Ripjaws F4-3200C22D-64GRS
                            SSD: Samsung 980 1TB
                            NIC: Intel i225 running at 2500 mbit
                            UEFI BIOS: TNTGL357.0064.2022.0217.1550

                            [00:51 xcpng33 xtf]# ./xtf-runner -aqq --host ; echo Result: $?
Combined test results:
test-hvm64-lbr-tsx-vmentry               CRASH
test-pv64-xsa-167                        SKIP
test-pv64-xsa-182                        SKIP
Result: 6

[00:53 xcpng33 xtf]# ./xtf-runner selftest -q --host
Combined test results:
test-hvm32-selftest                      SUCCESS
test-hvm32pae-selftest                   SUCCESS
test-hvm32pse-selftest                   SUCCESS
test-hvm64-selftest                      SUCCESS
test-pv64-selftest                       SUCCESS

[00:53 xcpng33 xtf]# ./xtf-runner -aq --host
Combined test results:
test-hvm32-cpuid-faulting                SUCCESS
test-hvm32pae-cpuid-faulting             SUCCESS
test-hvm32pse-cpuid-faulting             SUCCESS
test-hvm64-cpuid-faulting                SUCCESS
test-pv64-cpuid-faulting                 SUCCESS
test-hvm64-fpu-exception-emulation       SUCCESS
test-hvm32-invlpg~hap                    SUCCESS
test-hvm32-invlpg~shadow                 SUCCESS
test-hvm32pae-invlpg~hap                 SUCCESS
test-hvm32pae-invlpg~shadow              SUCCESS
test-hvm64-invlpg~hap                    SUCCESS
test-hvm64-invlpg~shadow                 SUCCESS
test-hvm64-lbr-tsx-vmentry               CRASH
test-hvm32-livepatch-priv-check          SUCCESS
test-hvm64-livepatch-priv-check          SUCCESS
test-pv64-livepatch-priv-check           SUCCESS
test-hvm32pae-memop-seg                  SUCCESS
test-hvm64-memop-seg                     SUCCESS
test-pv64-memop-seg                      SUCCESS
test-hvm32pae-nmi-taskswitch-priv        SUCCESS
test-pv64-pv-fsgsbase                    SUCCESS
test-pv64-pv-iopl~hypercall              SUCCESS
test-pv64-pv-iopl~vmassist               SUCCESS
test-hvm32-swint-emulation               SUCCESS
test-hvm32pae-swint-emulation            SUCCESS
test-hvm32pse-swint-emulation            SUCCESS
test-hvm64-swint-emulation               SUCCESS
test-hvm32-umip                          SUCCESS
test-hvm64-umip                          SUCCESS
test-hvm32-xsa-122                       SUCCESS
test-hvm32pae-xsa-122                    SUCCESS
test-hvm32pse-xsa-122                    SUCCESS
test-hvm64-xsa-122                       SUCCESS
test-pv64-xsa-122                        SUCCESS
test-hvm32-xsa-123                       SUCCESS
test-pv64-xsa-167                        SKIP
test-hvm64-xsa-168                       SUCCESS
test-hvm64-xsa-170                       SUCCESS
test-hvm64-xsa-173                       SUCCESS
test-pv64-xsa-182                        SKIP
test-hvm32-xsa-186                       SUCCESS
test-hvm64-xsa-186                       SUCCESS
test-hvm32-xsa-188                       SUCCESS
test-hvm32pae-xsa-188                    SUCCESS
test-hvm32pse-xsa-188                    SUCCESS
test-hvm64-xsa-188                       SUCCESS
test-pv64-xsa-188                        SUCCESS
test-hvm32-xsa-191                       SUCCESS
test-hvm32-xsa-192                       SUCCESS
test-pv64-xsa-193                        SUCCESS
test-hvm64-xsa-195                       SUCCESS
test-hvm64-xsa-196                       SUCCESS
test-hvm32-xsa-200                       SUCCESS
test-hvm32-xsa-203                       SUCCESS
test-hvm64-xsa-204                       SUCCESS
test-pv64-xsa-212                        SUCCESS
test-pv64-xsa-213                        SUCCESS
test-hvm64-xsa-221                       SUCCESS
test-pv64-xsa-221                        SUCCESS
test-pv64-xsa-224                        SUCCESS
test-pv64-xsa-227                        SUCCESS
test-hvm64-xsa-231                       SUCCESS
test-pv64-xsa-231                        SUCCESS
test-hvm64-xsa-232                       SUCCESS
test-pv64-xsa-232                        SUCCESS
test-pv64-xsa-234                        SUCCESS
test-hvm32-xsa-239                       SUCCESS
test-pv64-xsa-255                        SUCCESS
test-pv64-xsa-259                        SUCCESS
test-pv64-xsa-260                        SUCCESS
test-hvm64-xsa-261                       SUCCESS
test-pv64-xsa-265                        SUCCESS
test-hvm64-xsa-269                       SUCCESS
test-hvm64-xsa-277                       SUCCESS
test-hvm64-xsa-278                       SUCCESS
test-pv64-xsa-279                        SUCCESS
test-pv64-xsa-286                        SUCCESS
test-pv64-xsa-296                        SUCCESS
test-pv64-xsa-298                        SUCCESS
test-hvm64-xsa-304                       SUCCESS
test-hvm64-xsa-308                       SUCCESS
test-pv64-xsa-316                        SUCCESS
test-hvm32-xsa-317                       SUCCESS
test-hvm32pae-xsa-317                    SUCCESS
test-hvm32pse-xsa-317                    SUCCESS
test-hvm64-xsa-317                       SUCCESS
test-pv64-xsa-317                        SUCCESS
test-pv64-xsa-333                        SUCCESS
test-pv64-xsa-339                        SUCCESS
test-hvm32pae-xsa-consoleio-write        SUCCESS

[00:54 xcpng33 xtf]# /usr/libexec/xen/bin/test-cpu-policy
CPU Policy unit tests
Testing CPU vendor identification:
Testing CPUID serialise success:
Testing CPUID deserialise failure:
Testing CPUID out-of-range clearing:
Testing MSR serialise success:
Testing MSR deserialise failure:
Testing policy compatibility success:
Testing policy compatibility failure:
Done: all ok
                            stormiS 1 Reply Last reply Reply Quote 2
                            • stormiS Offline
                              stormi Vates 🪐 XCP-ng Team @Strebor
                              last edited by

                              @Strebor Thanks! You likely have the same crash as what was discussed earlier in the thread (same test failing), with instructions to install a patched Xen to see if it fixes it for you.

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

                                @stormi You're all welcome! Thanks so much for making this possible!

                                I will install the patch next week when I'm back in the office and send the updated results.

                                1 Reply Last reply Reply Quote 0
                                • S Offline
                                  Strebor @stormi
                                  last edited by

                                  @stormi

                                  Yes, it seems the patches fix it:

                                  Host: Intel Nuc11TNK
                                  CPU: i5-1135G7
                                  RAM: 64GB G.SKILL Ripjaws F4-3200C22D-64GRS
                                  SSD: Samsung 980 1TB
                                  NIC: Intel i225 running at 2500 mbit
                                  UEFI BIOS: TNTGL357.0064.2022.0217.1550

                                  [16:51 xcpng33 xtf]# ./xtf-runner -aqq --host ; echo Result: $?
Combined test results:
test-pv64-xsa-167                        SKIP
test-pv64-xsa-182                        SKIP

                                  [16:52 xcpng33 xtf]# ./xtf-runner selftest -q --host
Combined test results:
test-hvm32-selftest                      SUCCESS
test-hvm32pae-selftest                   SUCCESS
test-hvm32pse-selftest                   SUCCESS
test-hvm64-selftest                      SUCCESS
test-pv64-selftest                       SUCCESS

                                  [16:52 xcpng33 xtf]# ./xtf-runner -aq --host
Combined test results:
test-hvm32-cpuid-faulting                SUCCESS
test-hvm32pae-cpuid-faulting             SUCCESS
test-hvm32pse-cpuid-faulting             SUCCESS
test-hvm64-cpuid-faulting                SUCCESS
test-pv64-cpuid-faulting                 SUCCESS
test-hvm64-fpu-exception-emulation       SUCCESS
test-hvm32-invlpg~hap                    SUCCESS
test-hvm32-invlpg~shadow                 SUCCESS
test-hvm32pae-invlpg~hap                 SUCCESS
test-hvm32pae-invlpg~shadow              SUCCESS
test-hvm64-invlpg~hap                    SUCCESS
test-hvm64-invlpg~shadow                 SUCCESS
test-hvm64-lbr-tsx-vmentry               SUCCESS
test-hvm32-livepatch-priv-check          SUCCESS
test-hvm64-livepatch-priv-check          SUCCESS
test-pv64-livepatch-priv-check           SUCCESS
test-hvm32pae-memop-seg                  SUCCESS
test-hvm64-memop-seg                     SUCCESS
test-pv64-memop-seg                      SUCCESS
test-hvm32pae-nmi-taskswitch-priv        SUCCESS
test-pv64-pv-fsgsbase                    SUCCESS
test-pv64-pv-iopl~hypercall              SUCCESS
test-pv64-pv-iopl~vmassist               SUCCESS
test-hvm32-swint-emulation               SUCCESS
test-hvm32pae-swint-emulation            SUCCESS
test-hvm32pse-swint-emulation            SUCCESS
test-hvm64-swint-emulation               SUCCESS
test-hvm32-umip                          SUCCESS
test-hvm64-umip                          SUCCESS
test-hvm32-xsa-122                       SUCCESS
test-hvm32pae-xsa-122                    SUCCESS
test-hvm32pse-xsa-122                    SUCCESS
test-hvm64-xsa-122                       SUCCESS
test-pv64-xsa-122                        SUCCESS
test-hvm32-xsa-123                       SUCCESS
test-pv64-xsa-167                        SKIP
test-hvm64-xsa-168                       SUCCESS
test-hvm64-xsa-170                       SUCCESS
test-hvm64-xsa-173                       SUCCESS
test-pv64-xsa-182                        SKIP
test-hvm32-xsa-186                       SUCCESS
test-hvm64-xsa-186                       SUCCESS
test-hvm32-xsa-188                       SUCCESS
test-hvm32pae-xsa-188                    SUCCESS
test-hvm32pse-xsa-188                    SUCCESS
test-hvm64-xsa-188                       SUCCESS
test-pv64-xsa-188                        SUCCESS
test-hvm32-xsa-191                       SUCCESS
test-hvm32-xsa-192                       SUCCESS
test-pv64-xsa-193                        SUCCESS
test-hvm64-xsa-195                       SUCCESS
test-hvm64-xsa-196                       SUCCESS
test-hvm32-xsa-200                       SUCCESS
test-hvm32-xsa-203                       SUCCESS
test-hvm64-xsa-204                       SUCCESS
test-pv64-xsa-212                        SUCCESS
test-pv64-xsa-213                        SUCCESS
test-hvm64-xsa-221                       SUCCESS
test-pv64-xsa-221                        SUCCESS
test-pv64-xsa-224                        SUCCESS
test-pv64-xsa-227                        SUCCESS
test-hvm64-xsa-231                       SUCCESS
test-pv64-xsa-231                        SUCCESS
test-hvm64-xsa-232                       SUCCESS
test-pv64-xsa-232                        SUCCESS
test-pv64-xsa-234                        SUCCESS
test-hvm32-xsa-239                       SUCCESS
test-pv64-xsa-255                        SUCCESS
test-pv64-xsa-259                        SUCCESS
test-pv64-xsa-260                        SUCCESS
test-hvm64-xsa-261                       SUCCESS
test-pv64-xsa-265                        SUCCESS
test-hvm64-xsa-269                       SUCCESS
test-hvm64-xsa-277                       SUCCESS
test-hvm64-xsa-278                       SUCCESS
test-pv64-xsa-279                        SUCCESS
test-pv64-xsa-286                        SUCCESS
test-pv64-xsa-296                        SUCCESS
test-pv64-xsa-298                        SUCCESS
test-hvm64-xsa-304                       SUCCESS
test-hvm64-xsa-308                       SUCCESS
test-pv64-xsa-316                        SUCCESS
test-hvm32-xsa-317                       SUCCESS
test-hvm32pae-xsa-317                    SUCCESS
test-hvm32pse-xsa-317                    SUCCESS
test-hvm64-xsa-317                       SUCCESS
test-pv64-xsa-317                        SUCCESS
test-pv64-xsa-333                        SUCCESS
test-pv64-xsa-339                        SUCCESS
test-hvm32pae-xsa-consoleio-write        SUCCESS

                                  [16:53 xcpng33 xtf]# /usr/libexec/xen/bin/test-cpu-policy
CPU Policy unit tests
Testing CPU vendor identification:
Testing CPUID serialise success:
Testing CPUID deserialise failure:
Testing CPUID out-of-range clearing:
Testing MSR serialise success:
Testing MSR deserialise failure:
Testing policy compatibility success:
Testing policy compatibility failure:
Done: all ok
                                  1 Reply Last reply Reply Quote 2
                                  • jchuaJ Offline
                                    jchua
                                    last edited by jchua

                                    Hi all, i'm new to XCP-NG. 🙂

                                    Here are the test results for:
                                    Host: Intel NUC11PAHi7

                                    [04:08 xcp-1 xtf]# ./xtf-runner selftest -q --host
Combined test results:
test-hvm32-selftest                      SUCCESS
test-hvm32pae-selftest                   SUCCESS
test-hvm32pse-selftest                   SUCCESS
test-hvm64-selftest                      SUCCESS
test-pv64-selftest                       SUCCESS

                                    [04:08 xcp-1 xtf]# ./xtf-runner -aq --host
Combined test results:
test-hvm32-cpuid-faulting                SUCCESS
test-hvm32pae-cpuid-faulting             SUCCESS
test-hvm32pse-cpuid-faulting             SUCCESS
test-hvm64-cpuid-faulting                SUCCESS
test-pv64-cpuid-faulting                 SUCCESS
test-hvm64-fpu-exception-emulation       SUCCESS
test-hvm32-invlpg~hap                    SUCCESS
test-hvm32-invlpg~shadow                 SUCCESS
test-hvm32pae-invlpg~hap                 SUCCESS
test-hvm32pae-invlpg~shadow              SUCCESS
test-hvm64-invlpg~hap                    SUCCESS
test-hvm64-invlpg~shadow                 SUCCESS
test-hvm64-lbr-tsx-vmentry               SUCCESS
test-hvm32-livepatch-priv-check          SUCCESS
test-hvm64-livepatch-priv-check          SUCCESS
test-pv64-livepatch-priv-check           SUCCESS
test-hvm32pae-memop-seg                  SUCCESS
test-hvm64-memop-seg                     SUCCESS
test-pv64-memop-seg                      SUCCESS
test-hvm32pae-nmi-taskswitch-priv        SUCCESS
test-pv64-pv-fsgsbase                    SUCCESS
test-pv64-pv-iopl~hypercall              SUCCESS
test-pv64-pv-iopl~vmassist               SUCCESS
test-hvm32-swint-emulation               SUCCESS
test-hvm32pae-swint-emulation            SUCCESS
test-hvm32pse-swint-emulation            SUCCESS
test-hvm64-swint-emulation               SUCCESS
test-hvm32-umip                          SUCCESS
test-hvm64-umip                          SUCCESS
test-hvm32-xsa-122                       SUCCESS
test-hvm32pae-xsa-122                    SUCCESS
test-hvm32pse-xsa-122                    SUCCESS
test-hvm64-xsa-122                       SUCCESS
test-pv64-xsa-122                        SUCCESS
test-hvm32-xsa-123                       SUCCESS
test-pv64-xsa-167                        SKIP
test-hvm64-xsa-168                       SUCCESS
test-hvm64-xsa-170                       SUCCESS
test-hvm64-xsa-173                       SUCCESS
test-pv64-xsa-182                        SKIP
test-hvm32-xsa-186                       SUCCESS
test-hvm64-xsa-186                       SUCCESS
test-hvm32-xsa-188                       SUCCESS
test-hvm32pae-xsa-188                    SUCCESS
test-hvm32pse-xsa-188                    SUCCESS
test-hvm64-xsa-188                       SUCCESS
test-pv64-xsa-188                        SUCCESS
test-hvm32-xsa-191                       SUCCESS
test-hvm32-xsa-192                       SUCCESS
test-pv64-xsa-193                        SUCCESS
test-hvm64-xsa-195                       SUCCESS
test-hvm64-xsa-196                       SUCCESS
test-hvm32-xsa-200                       SUCCESS
test-hvm32-xsa-203                       SUCCESS
test-hvm64-xsa-204                       SUCCESS
test-pv64-xsa-212                        SUCCESS
test-pv64-xsa-213                        SUCCESS
test-hvm64-xsa-221                       SUCCESS
test-pv64-xsa-221                        SUCCESS
test-pv64-xsa-224                        SUCCESS
test-pv64-xsa-227                        SUCCESS
test-hvm64-xsa-231                       SUCCESS
test-pv64-xsa-231                        SUCCESS
test-hvm64-xsa-232                       SUCCESS
test-pv64-xsa-232                        SUCCESS
test-pv64-xsa-234                        SUCCESS
test-hvm32-xsa-239                       SUCCESS
test-pv64-xsa-255                        SUCCESS
test-pv64-xsa-259                        SUCCESS
test-pv64-xsa-260                        SUCCESS
test-hvm64-xsa-261                       SUCCESS
test-pv64-xsa-265                        SUCCESS
test-hvm64-xsa-269                       SUCCESS
test-hvm64-xsa-277                       SUCCESS
test-hvm64-xsa-278                       SUCCESS
test-pv64-xsa-279                        SUCCESS
test-pv64-xsa-286                        SUCCESS
test-pv64-xsa-296                        SUCCESS
test-pv64-xsa-298                        SUCCESS
test-hvm64-xsa-304                       SUCCESS
test-hvm64-xsa-308                       SUCCESS
test-pv64-xsa-316                        SUCCESS
test-hvm32-xsa-317                       SUCCESS
test-hvm32pae-xsa-317                    SUCCESS
test-hvm32pse-xsa-317                    SUCCESS
test-hvm64-xsa-317                       SUCCESS
test-pv64-xsa-317                        SUCCESS
test-pv64-xsa-333                        SUCCESS
test-pv64-xsa-339                        SUCCESS
test-hvm32pae-xsa-consoleio-write        SUCCESS

                                    [04:09 xcp-1 xtf]# /usr/libexec/xen/bin/test-cpu-policy
CPU Policy unit tests
Testing CPU vendor identification:
Testing CPUID serialise success:
Testing CPUID deserialise failure:
Testing CPUID out-of-range clearing:
Testing MSR serialise success:
Testing MSR deserialise failure:
Testing policy compatibility success:
Testing policy compatibility failure:
Done: all ok
                                    1 Reply Last reply Reply Quote 1
                                    • N Offline
                                      Niko1
                                      last edited by

                                      Hello, I decided to give the alpha a go, butI must have screwed something up. I upgraded one of my servers from 8.2. Upgrade seemed to go well. But now the console is very laggy and locks up for periods of time. I keep getting errors to the terminal

                                      Broadcast message from systemd-journald@xen-rack (Wed 2023-02-15 20:37:34 EST):

xapi-nbd[2128]: main:   "Failed to log in via xapi's Unix domain socket in 300.000000 seconds")

                                      in /var/log/xensource.log

                                      Feb 15 20:37:13 xen-rack xapi: [debug||0 |bringing up management interface D:45c71627e307|xapi_mgmt_iface] Shutting down the old management interface (if any)
Feb 15 20:37:13 xen-rack xapi: [ info||0 |bringing up management interface D:45c71627e307|xapi_mgmt_iface] Starting new server (listening on all IP addresses)
Feb 15 20:37:13 xen-rack xapi: [ info||0 |bringing up management interface D:45c71627e307|xapi_http] Successfully bound socket to: :::80
Feb 15 20:37:13 xen-rack xapi: [error||0 |bringing up management interface D:45c71627e307|master_connection] Caught Master_connection.Goto_handler
Feb 15 20:37:13 xen-rack xapi: [debug||0 |bringing up management interface D:45c71627e307|master_connection] Connection to master died. I will continue to retry indefinitely (supressing future logging of this message).
Feb 15 20:37:13 xen-rack xapi: [error||0 |bringing up management interface D:45c71627e307|master_connection] Connection to master died. I will continue to retry indefinitely (supressing future logging of this message).
Feb 15 20:37:13 xen-rack xapi: [debug||0 |bringing up management interface D:45c71627e307|master_connection] Sleeping 2.000000 seconds before retrying master connection...
Feb 15 20:37:15 xen-rack xapi: [debug||0 |bringing up management interface D:45c71627e307|stunnel] client cert verification 192.168.1.15:443: None
Feb 15 20:37:15 xen-rack xapi: [debug||0 |bringing up management interface D:45c71627e307|master_connection] stunnel: stunnel start\x0A
Feb 15 20:37:15 xen-rack xapi: [debug||0 |bringing up management interface D:45c71627e307|stunnel] Started a client (pid:7816): -> 192.168.1.15:443

                                      Is there something I can do to fix the upgrade?

                                      stormiS 1 Reply Last reply Reply Quote 0
                                      • R Offline
                                        rRobbie
                                        last edited by rRobbie

                                        @stormi, hello.

                                        Not sure it is related, but after the last XCP-NG update the windows driver are no longer recognized.

                                        Screenshot from 2023-02-16 07-20-49.png

                                        I tried to repair / remove / re-install. I also tried to manually update them pointing to the Driverw folder in XCP-ng/XenTools without success.

                                        Citrix guest tools are disabled.

                                        Screenshot from 2023-02-16 07-14-56.png

                                        Thanks for any insights.

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

                                          @Niko1 @rRobbie could you both open separate topics so that we can discuss your issues separately?

                                          1 Reply Last reply Reply Quote 1
                                          • gskgerG Offline
                                            gskger Top contributor @stormi
                                            last edited by

                                            @stormi
                                            From my homelab:

                                            Dell PowerEdge R720, BIOS 2.9.0
                                            2x Intel Xeon E5-2640 v2
                                            128GB RAM

                                            ./xtf-runner selftest -q --host
Combined test results:
test-hvm32-selftest                      SUCCESS
test-hvm32pae-selftest                   SUCCESS
test-hvm32pse-selftest                   SUCCESS
test-hvm64-selftest                      SUCCESS
test-pv64-selftest                       SUCCESS

                                            [18:31 xcp83 xtf]# ./xtf-runner -aq --host
Combined test results:
test-hvm32-cpuid-faulting                SUCCESS
test-hvm32pae-cpuid-faulting             SUCCESS
test-hvm32pse-cpuid-faulting             SUCCESS
test-hvm64-cpuid-faulting                SUCCESS
test-pv64-cpuid-faulting                 SUCCESS
test-hvm64-fpu-exception-emulation       SUCCESS
test-hvm32-invlpg~hap                    SUCCESS
test-hvm32-invlpg~shadow                 SUCCESS
test-hvm32pae-invlpg~hap                 SUCCESS
test-hvm32pae-invlpg~shadow              SUCCESS
test-hvm64-invlpg~hap                    SUCCESS
test-hvm64-invlpg~shadow                 SUCCESS
test-hvm64-lbr-tsx-vmentry               SUCCESS
test-hvm32-livepatch-priv-check          SUCCESS
test-hvm64-livepatch-priv-check          SUCCESS
test-pv64-livepatch-priv-check           SUCCESS
test-hvm32pae-memop-seg                  SUCCESS
test-hvm64-memop-seg                     SUCCESS
test-pv64-memop-seg                      SUCCESS
test-hvm32pae-nmi-taskswitch-priv        SUCCESS
test-pv64-pv-fsgsbase                    SUCCESS
test-pv64-pv-iopl~hypercall              SUCCESS
test-pv64-pv-iopl~vmassist               SUCCESS
test-hvm32-swint-emulation               SUCCESS
test-hvm32pae-swint-emulation            SUCCESS
test-hvm32pse-swint-emulation            SUCCESS
test-hvm64-swint-emulation               SUCCESS
test-hvm32-umip                          SKIP
test-hvm64-umip                          SKIP
test-hvm32-xsa-122                       SUCCESS
test-hvm32pae-xsa-122                    SUCCESS
test-hvm32pse-xsa-122                    SUCCESS
test-hvm64-xsa-122                       SUCCESS
test-pv64-xsa-122                        SUCCESS
test-hvm32-xsa-123                       SUCCESS
test-pv64-xsa-167                        SKIP
test-hvm64-xsa-168                       SUCCESS
test-hvm64-xsa-170                       SUCCESS
test-hvm64-xsa-173                       SUCCESS
test-pv64-xsa-182                        SKIP
test-hvm32-xsa-186                       SUCCESS
test-hvm64-xsa-186                       SUCCESS
test-hvm32-xsa-188                       SUCCESS
test-hvm32pae-xsa-188                    SUCCESS
test-hvm32pse-xsa-188                    SUCCESS
test-hvm64-xsa-188                       SUCCESS
test-pv64-xsa-188                        SUCCESS
test-hvm32-xsa-191                       SUCCESS
test-hvm32-xsa-192                       SUCCESS
test-pv64-xsa-193                        SUCCESS
test-hvm64-xsa-195                       SUCCESS
test-hvm64-xsa-196                       SUCCESS
test-hvm32-xsa-200                       SUCCESS
test-hvm32-xsa-203                       SUCCESS
test-hvm64-xsa-204                       SUCCESS
test-pv64-xsa-212                        SUCCESS
test-pv64-xsa-213                        SUCCESS
test-hvm64-xsa-221                       SUCCESS
test-pv64-xsa-221                        SUCCESS
test-pv64-xsa-224                        SUCCESS
test-pv64-xsa-227                        SUCCESS
test-hvm64-xsa-231                       SUCCESS
test-pv64-xsa-231                        SUCCESS
test-hvm64-xsa-232                       SUCCESS
test-pv64-xsa-232                        SUCCESS
test-pv64-xsa-234                        SUCCESS
test-hvm32-xsa-239                       SUCCESS
test-pv64-xsa-255                        SUCCESS
test-pv64-xsa-259                        SUCCESS
test-pv64-xsa-260                        SUCCESS
test-hvm64-xsa-261                       SUCCESS
test-pv64-xsa-265                        SUCCESS
test-hvm64-xsa-269                       SUCCESS
test-hvm64-xsa-277                       SUCCESS
test-hvm64-xsa-278                       SUCCESS
test-pv64-xsa-279                        SUCCESS
test-pv64-xsa-286                        SUCCESS
test-pv64-xsa-296                        SUCCESS
test-pv64-xsa-298                        SUCCESS
test-hvm64-xsa-304                       SUCCESS
test-hvm64-xsa-308                       SUCCESS
test-pv64-xsa-316                        SUCCESS
test-hvm32-xsa-317                       SUCCESS
test-hvm32pae-xsa-317                    SUCCESS
test-hvm32pse-xsa-317                    SUCCESS
test-hvm64-xsa-317                       SUCCESS
test-pv64-xsa-317                        SUCCESS
test-pv64-xsa-333                        SUCCESS
test-pv64-xsa-339                        SUCCESS
test-hvm32pae-xsa-consoleio-write        SUCCESS

[18:32 xcp83 xtf]# echo $?
3

                                            [18:34 xcp83 xtf]# /usr/libexec/xen/bin/test-cpu-policy
CPU Policy unit tests
Testing CPU vendor identification:
Testing CPUID serialise success:
Testing CPUID deserialise failure:
Testing CPUID out-of-range clearing:
Testing MSR serialise success:
Testing MSR deserialise failure:
Testing policy compatibility success:
Testing policy compatibility failure:
Done: all ok

[18:35 xcp83 xtf]# echo $?
0
                                            1 Reply Last reply Reply Quote 1
                                            • First post
                                              Last post