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.
    • DanpD Online
      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
                              • stormiS Offline
                                stormi Vates πŸͺ XCP-ng Team @Andrew
                                last edited by

                                @Andrew I now pushed a rebased build of XAPI in the xcp-ng-lab repo.

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

                                  @Andrew said in XCP-ng 8.3 beta πŸš€:

                                  @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?

                                  I'm the one who can answer the second part of this question, actually. It's all built in the xcp-ng-ci repository. We are now testing them in CI, will fix issues if there's any, and then this will reach the xcp-ng-base repository and make the packages in xcp-ng-lab deprecated (and should update them smoothly).

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

                                    @stormi So, is it better/safer to now just use xcp-ng-ci for an actual representation of XCP 8.3/Xen 4.17 beta/RC release?

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

                                      @Andrew No, it's not safer, as it's not tested, and there are far more changes than just Xen.

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

                                        @stormi said in XCP-ng 8.3 beta πŸš€:

                                        yum update --enablerepo=xcp-ng-lab

                                        After the new updates came out yesterday, I did the update but, this time, I did what you said (" yum update --enablerepo=xcp-ng-lab") and it worked perfectly...thanks!

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

                                          New updates are propagating to the mirrors as I write this. Xen 4.17 for everyone, XAPI 24.11, and various other changes bringing us closer to a release candidate for XCP-ng 8.3.

                                          Users of Xen 4.17 from the xcp-ng-lab repository don't need to use this repository anymore, as the new update supersedes it.

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

                                            @stormi
                                            I tried it but....
                                            I will try to paste a pic here, don't laugh at me

                                            snap-2024-04-22.png

                                            I have a few weeks ago installed nut client:
                                            yum --enablerepo=* install nut-client.x86_64
                                            I hope that didnt break it

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