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

    XCP-ng 8.3 betas and RCs feedback πŸš€

    Scheduled Pinned Locked Moved News
    792 Posts 89 Posters 1.4m Views 69 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 Offline
      olivierlambert Vates πŸͺ Co-Founder CEO
      last edited by

      XOSTOR isn't entirely ready on 8.3 yet (at least it's not on the latest bug fixes level)

      1 Reply Last reply Reply Quote 0
      • AnonabharA Offline
        Anonabhar
        last edited by

        So I got a weird one. I have installed the latest XCP 8.3 updates and rebooted my server. All the VM's I had on my test server worked perfectly fine except for a single Debian 9 VM that would start booting and then "power off" just as the kernel started to spit stuff on the display.

        I banged around with it for a while and what I found is its a kernel crash somewhere when SMP is initialized. If I only give a single vProc to the VM, it boots normally and all works fine.

        At this point, its not causing me any more problems because I jsut rebuilt the VM on something more modern (Rocky 9)

        I have perserved this VM if the dev's would like to get more debugging information or wish to try anything. I can also capture the logs if its of interest.

        stormiS 1 Reply Last reply Reply Quote 0
        • stormiS Offline
          stormi Vates πŸͺ XCP-ng Team @flakpyro
          last edited by

          @flakpyro If the pull request mentioned by @psafont earlier does fix it, we'll know next time we rebase on the fixed code.

          1 Reply Last reply Reply Quote 0
          • stormiS Offline
            stormi Vates πŸͺ XCP-ng Team @Anonabhar
            last edited by

            @Anonabhar I don't think we have enough work bandwidth to investigate this, but it could be good, if you have enough space, to keep it for some time. If someone has a similar issue in the future, maybe this will prove useful.

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

              I noteced new updates for 8.3 this morning. Oen of teh machines will not update. When you try to run it from XOA you get this error:

              pool.installPatches
              {
                "hosts": [
                  "7ce4f772-4391-4982-a1f9-d1de86be92cb"
                ]
              }
              {
                "code": "-1",
                "params": [
                  "Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1",
                  "",
                  "Traceback (most recent call last):
                File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 119, in wrapper
                  return func(*args, **kwds)
                File \"/etc/xapi.d/plugins/updater.py\", line 96, in decorator
                  return func(*args, **kwargs)
                File \"/etc/xapi.d/plugins/updater.py\", line 182, in update
                  return install_helper(session, args, 'update')
                File \"/etc/xapi.d/plugins/updater.py\", line 153, in install_helper
                  raise error
              CalledProcessError: Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1
              "
                ],
                "call": {
                  "method": "host.call_plugin",
                  "params": [
                    "OpaqueRef:fab0b7b0-de37-a996-1760-92a38cf136c2",
                    "updater.py",
                    "update",
                    {}
                  ]
                },
                "message": "-1(Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1, , Traceback (most recent call last):
                File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 119, in wrapper
                  return func(*args, **kwds)
                File \"/etc/xapi.d/plugins/updater.py\", line 96, in decorator
                  return func(*args, **kwargs)
                File \"/etc/xapi.d/plugins/updater.py\", line 182, in update
                  return install_helper(session, args, 'update')
                File \"/etc/xapi.d/plugins/updater.py\", line 153, in install_helper
                  raise error
              CalledProcessError: Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1
              )",
                "name": "XapiError",
                "stack": "XapiError: -1(Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1, , Traceback (most recent call last):
                File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 119, in wrapper
                  return func(*args, **kwds)
                File \"/etc/xapi.d/plugins/updater.py\", line 96, in decorator
                  return func(*args, **kwargs)
                File \"/etc/xapi.d/plugins/updater.py\", line 182, in update
                  return install_helper(session, args, 'update')
                File \"/etc/xapi.d/plugins/updater.py\", line 153, in install_helper
                  raise error
              CalledProcessError: Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1
              )
                  at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202403291838/packages/xen-api/_XapiError.mjs:16:12)
                  at file:///opt/xo/xo-builds/xen-orchestra-202403291838/packages/xen-api/transports/json-rpc.mjs:38:21"
              
              
              If you go to the command line and do a "yum update" you get this:
              
              
              Transaction Summary
              ===================================================================================================================================================================================
              Install              ( 1 Dependent package)
              Upgrade  21 Packages
              
              Total size: 84 M
              Is this ok [y/d/N]: y
              Downloading packages:
              Running transaction check
              Running transaction test
              
              
              Transaction check error:
                file /usr/lib64/python2.7/site-packages/xen/__init__.py from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64
                file /usr/lib64/python2.7/site-packages/xen/lowlevel/__init__.py from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64
                file /usr/lib64/python3.6/site-packages/xen/__init__.py from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64
                file /usr/lib64/python3.6/site-packages/xen/lowlevel/__init__.py from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64
                file /usr/lib64/python2.7/site-packages/xen/__init__.pyc from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64
                file /usr/lib64/python2.7/site-packages/xen/lowlevel/__init__.pyc from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64
                file /usr/lib64/python2.7/site-packages/xen/__init__.pyo from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64
                file /usr/lib64/python2.7/site-packages/xen/lowlevel/__init__.pyo from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64
                file /usr/lib64/python2.7/site-packages/xen/lowlevel/xc.so from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64
                file /usr/lib64/python3.6/site-packages/xen/__pycache__/__init__.cpython-36.opt-1.pyc from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64
                file /usr/lib64/python3.6/site-packages/xen/lowlevel/__pycache__/__init__.cpython-36.opt-1.pyc from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64
                file /usr/lib64/python3.6/site-packages/xen/__pycache__/__init__.cpython-36.pyc from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64
                file /usr/lib64/python3.6/site-packages/xen/lowlevel/__pycache__/__init__.cpython-36.pyc from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64
                file /usr/lib64/python3.6/site-packages/xen/lowlevel/xc.cpython-36m-x86_64-linux-gnu.so from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64
              

              Any ideas?

              F stormiS 2 Replies Last reply Reply Quote 0
              • olivierlambertO Offline
                olivierlambert Vates πŸͺ Co-Founder CEO
                last edited by

                Have you, at any time, installed something outside the XCP-ng repos?

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

                  @olivierlambert

                  Hmmmm...while I'm gonna say a guarded "I don't think so", that is a junk machine that I use to test things so that may be a possibility.

                  How do I tell?

                  DanpD 1 Reply Last reply Reply Quote 0
                  • DanpD Offline
                    Danp Pro Support Team @archw
                    last edited by

                    @archw Post the output of yum repolist --verbose

                    FWIW, read here for the proper way to install additional packages.

                    A 1 Reply Last reply Reply Quote 0
                    • F Offline
                      flakpyro @archw
                      last edited by

                      @archw I see references to xen 4.17 in your logs. Are you currently using the 4.17 test repos or was 4.17 pushed out to the main 8.3 repos?

                      R 1 Reply Last reply Reply Quote 0
                      • R Offline
                        redakula @flakpyro
                        last edited by

                        @flakpyro

                        Probably - i get the same error and i am on the 4.17 testing version

                        1 Reply Last reply Reply Quote 0
                        • stormiS Offline
                          stormi Vates πŸͺ XCP-ng Team @archw
                          last edited by stormi

                          @archw I think you need to enable the xcp-ng-lab repo for updating because you installed the test packages with Xen 4.17.

                          yum update --enablerepo=xcp-ng-lab
                          
                          1 Reply Last reply Reply Quote 0
                          • stormiS Offline
                            stormi Vates πŸͺ XCP-ng Team
                            last edited by

                            Note: as soon as possible, we'll switch to Xen 4.17 for everyone so you won't have to think about the fact you were using packages from xcp-ng-lab.

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

                              @Danp

                              I think all of this is my fault and I wouldn't worry about it. After I left the last post, I went in and saw a but of stuff from the @xcp-ng-lab repo. I quasi fixed it doing a bunch of yum downgrades until I no longer got an error and and I think I fixed it. I had to remove a few things but I took a "yum list installed" from a good system and made everything the same. Again, its a dummy system that I don't really use except to test things.

                              Here is the output from "yum repolist --verbose"

                              Loading "fastestmirror" plugin
                              Config time: 0.010
                              Yum version: 3.4.3
                              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
                              Setting up Package Sacks
                              pkgsack time: 0.004
                              Repo-id      : xcp-ng-base
                              Repo-name    : XCP-ng Base Repository
                              Repo-revision: 1711706182
                              Repo-updated : Fri Mar 29 05:56:22 2024
                              Repo-pkgs    : 3,599
                              Repo-size    : 12 G
                              Repo-baseurl : http://mirrors.xcp-ng.org/8/8.3/base/x86_64/,
                                           : http://updates.xcp-ng.org/8/8.3/base/x86_64/
                              Repo-expire  : 21,600 second(s) (last: Sat Mar 30 15:37:49 2024)
                                Filter     : read-only:present
                              Repo-filename: /etc/yum.repos.d/xcp-ng.repo
                              
                              Repo-id      : xcp-ng-updates
                              Repo-name    : XCP-ng Updates Repository
                              Repo-revision: 1693236966
                              Repo-updated : Mon Aug 28 11:36:06 2023
                              Repo-pkgs    : 2
                              Repo-size    : 4.6 k
                              Repo-baseurl : http://mirrors.xcp-ng.org/8/8.3/updates/x86_64/,
                                           : http://updates.xcp-ng.org/8/8.3/updates/x86_64/
                              Repo-expire  : 21,600 second(s) (last: Sat Mar 30 15:37:50 2024)
                                Filter     : read-only:present
                              Repo-filename: /etc/yum.repos.d/xcp-ng.repo
                              
                              repolist: 3,601
                              
                              stormiS 1 Reply Last reply Reply Quote 0
                              • stormiS Offline
                                stormi Vates πŸͺ XCP-ng Team @archw
                                last edited by

                                @archw yum update --enablerepo=xcp-ng-lab didn't work for you?

                                A 2 Replies Last reply Reply Quote 0
                                • gduperreyG Offline
                                  gduperrey Vates πŸͺ XCP-ng Team
                                  last edited by

                                  A new version of xo-lite for XCP-ng 8.3 has been released:

                                  Version: xo-lite-0.2.1-1.xcpng8.3

                                  You can update it like this:

                                  yum update xo-lite
                                  

                                  For more information about the changes between version 0.1.3 or 0.2.0 and 0.2.1, you can consult this link: https://github.com/vatesfr/xen-orchestra/blob/master/%40xen-orchestra/lite/CHANGELOG.md

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

                                    @stormi I didn't even think to try that 😞 I just did it and its rebooting.

                                    1 Reply Last reply Reply Quote 0
                                    • 0nelight0 Offline
                                      0nelight @stormi
                                      last edited by 0nelight

                                      Tried to Boot the Installer for XCP-ng 8.3 beta 2 ISO (07-Feb-2024 19:21) on my Testmachine today:

                                      Gigabyte B550 AORUS PRO AC
                                      AMD Ryzen 7 3700X 8-Core Processor
                                      Adaptec 6405E (Hardware-RAID PCIe 2.0-Card)
                                      

                                      But the (discontinued by Adaptec but flawlessly working) RAID 6405E creates the following Errors (as in 8.2) on Boot:

                                      aacraid 0000:03:00.0: AAC0: aac_eh_abort: Host adapter abort request.
                                      aacraid 0000:03:00.0: AAC0: aac_eh_abort: Timed out Command
                                      

                                      In case anyone wants to fix this, this is my other forum posts regarding this:
                                      https://xcp-ng.org/forum/post/47040 (RAID 6405E)

                                      Adaptec RAID 8405E (also discontinued by Adaptec but newer) is on my productive System and I cannot test 8.3 at the moment there, but as I am aware of it should be better supported with 8.3. In case I manage to test it there, I will update you in this thread.
                                      https://xcp-ng.org/forum/post/47048 (RAID 8405E)

                                      https://github.com/xcp-ng/xcp/issues/472

                                      stormi created this issue in xcp-ng/xcp

                                      open Adaptec Series 6 Raid Cards not working because of kernel bug #472

                                      1 Reply Last reply Reply Quote 0
                                      • stormiS Offline
                                        stormi Vates πŸͺ XCP-ng Team
                                        last edited by

                                        A new update is available. It's a small one (though, as it touches XAPI, it causes many packages to be updated): the webserver will now report the correct mimetype for SVG files, which is needed by XO Lite.

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

                                          @stormi The base update conflicts with the 4.17 lab update...

                                          @olivierlambert Will XCP-ng 8.3 be using Xen 4.17 for the release (like XenServer)? If so, when will Xen 4.17 be part of the base install?

                                          R stormiS 3 Replies Last reply Reply Quote 1
                                          • R Offline
                                            ravenet @Andrew
                                            last edited by

                                            @Andrew Yes 8.3 will be xen 4.17. They've stated that this will be moved out of lab into the 8.3 official branch once they are happy with their and our feedback.

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