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.3m 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.
    • stormiS Offline
      stormi Vates 🪐 XCP-ng Team @ph7
      last edited by

      @ph7 This happens when not all hosts in the pool are up to date. Could it be the case?

      P 1 Reply Last reply Reply Quote 0
      • P Offline
        ph7 @stormi
        last edited by

        @stormi No, they are on the same patchlevel. Exept these released just resently.

        P 1 Reply Last reply Reply Quote 0
        • P Offline
          ph7 @ph7
          last edited by

          @ph7
          Eureka. I can see them now !!!

          P 1 Reply Last reply Reply Quote 0
          • P Offline
            ph7 @ph7
            last edited by

            @ph7 Running rolling pool update.
            This is really fun.
            Love this project

            1 Reply Last reply Reply Quote 0
            • L Offline
              laurentm
              last edited by laurentm

              XenOrchestra (from source) update failed with the latest updates of XCP-NG 8.3.
              I opened a topic in XOA forum, but I succeeded to update in XCP-NG 8.2, so the
              error is coming from 8.3.

              fatal: unable to access 'https://github.com/vatesfr/xen-orchestra/': server certificate verification failed. CAfile: none CRLfile: none

              Finally, I have bypassed the PFBlocker module during the update and no more error happened.

              stormiS 1 Reply Last reply Reply Quote 0
              • L Offline
                lethedata
                last edited by

                ISO NFS can't seem to mount with an IPv6 address as it leads to a "DNS Error."

                Error code: SR_BACKEND_FAILURE_140
                Error parameters: , Incorrect DNS name, unable to resolve.,
                

                sr-probe is able to find the target/paths and VDI SR NFS is able to mount using the same path. Tried with and without brackets but no success on the NFS ISO side

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

                  @laurentm What's the dedicated topic? We can discuss there.

                  L 1 Reply Last reply Reply Quote 0
                  • BenjiReisB Offline
                    BenjiReis Vates 🪐 XCP-ng Team @lethedata
                    last edited by BenjiReis

                    @lethedata Can you share the command you're running and the corresponding SMlog?

                    Thanks

                    1 Reply Last reply Reply Quote 0
                    • L Offline
                      laurentm @stormi
                      last edited by

                      @stormi

                      https://xcp-ng.org/forum/topic/8527/fatal-error-while-updating-xoa-installed-from-source/7

                      1 Reply Last reply Reply Quote 0
                      • C Offline
                        cunrun
                        last edited by

                        Just providing feedback:

                        Love the XO interface at the start, very helpful. Also, I do like the colour scheme. It turned a few heads in the datacentre the other day.

                        Using a Dell R740xd with 2 GPU's to pass through - Works fine and given the GPU's to a VM each (for 3D mapping).

                        After watching Lawrence Systems device passthrough vid, I managed to view a PUSB in the XOA via the host. I managed to pass it through to a Windows 10 VM but cannot see if in the device manager. Assuming that this still in beta stages so will try a different set of USB devices for testing but so far the Seagate RSS LLC_00000000NAB7AQ06 doesn't show in Windows.

                        d1968cbe-61a8-49a5-8efb-8555882cd738-image.png

                        65a2d246-e99c-4fa1-8d21-1173186052e2-image.png

                        752f246b-0c73-4c99-9f93-3729005f3d82-image.png

                        Happy to test further

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

                          @cunrun said in XCP-ng 8.3 beta 🚀:

                          Just providing feedback:

                          Love the XO interface at the start, very helpful. Also, I do like the colour scheme. It turned a few heads in the datacentre the other day.

                          Using a Dell R740xd with 2 GPU's to pass through - Works fine and given the GPU's to a VM each (for 3D mapping).

                          After watching Lawrence Systems device passthrough vid, I managed to view a PUSB in the XOA via the host. I managed to pass it through to a Windows 10 VM but cannot see if in the device manager. Assuming that this still in beta stages so will try a different set of USB devices for testing but so far the Seagate RSS LLC_00000000NAB7AQ06 doesn't show in Windows.

                          d1968cbe-61a8-49a5-8efb-8555882cd738-image.png

                          65a2d246-e99c-4fa1-8d21-1173186052e2-image.png

                          752f246b-0c73-4c99-9f93-3729005f3d82-image.png

                          Happy to test further

                          Did you run a scan for changes (the icon of a monitor with a magnifying glass) in that Device Manager window? It will then check for new drivers to install and prepare for use. Prompting for device driver installation if required.

                          C 1 Reply Last reply Reply Quote 0
                          • R Offline
                            ravenet @Andrew
                            last edited by

                            @Andrew said in XCP-ng 8.3 beta 🚀:

                            @ravenet I did not have any problems with my Mellanox Connect-4 Lx card during upgrades from 8.2.1 (5.0 driver), to 8.3 (5.4 driver), then update to current 8.3 (5.9 driver), and then update to Xen 4.17.3. My card has the 14.32.1010 firmware. It is not used for the management interface. It is used by VMs and continued to keep the same ethernet name and function for the VMs.

                            Thanks for testing

                            I finally got around to updating the firmware on this Mellanox connectx-4 LX adapter. Bit of jumping through hoops to install tools, find proper firmware, but went from FW version14.18.1000 to New FW version: 14.32.1010. Had to do an emergency network reset again, but it's back.

                            Obviously an incompatibility with the new 5.9 driver with much older mellanox firmware.

                            AnonabharA 1 Reply Last reply Reply Quote 2
                            • AnonabharA Offline
                              Anonabhar @ravenet
                              last edited by

                              @ravenet This worries me because I use the Connectx-3 cards in my setup. I wonder if I am going to run into the same problem or is it only a Connectx-4 problem.

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

                                @Anonabhar I don't think so as the ConnectX-3 is supported only in the older 4.9 drivers and not the newer versions (5.0 or 5.9 or newer). As all of these cards are old and EOL, it would be good to have the latest/last firmware installed anyway.

                                stormiS 1 Reply Last reply Reply Quote 0
                                • X Offline
                                  xerxist
                                  last edited by

                                  Any reason why xcp-ng is focussing on back porting kernel drivers and fixes to an old kernel instead of using a newer kernel and porting back in what is needed for xcp-ng?

                                  stormiS 1 Reply Last reply Reply Quote 0
                                  • C Offline
                                    cunrun @john.c
                                    last edited by

                                    @john-c Yeah, tried all of that. I get the same issue with older GPU's when vGPU'ing them. So I'm wondering if it's a setting on the Dell Server BIOS.

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

                                      @xerxist Who says we're not doing both?

                                      X 2 Replies Last reply Reply Quote 0
                                      • stormiS Offline
                                        stormi Vates 🪐 XCP-ng Team @Andrew
                                        last edited by

                                        @Andrew @Anonabhar Indeed, it's not the same driver so the old card will keep using the old driver.

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

                                          @cunrun said in XCP-ng 8.3 beta 🚀:

                                          @john-c Yeah, tried all of that. I get the same issue with older GPU's when vGPU'ing them. So I'm wondering if it's a setting on the Dell Server BIOS.

                                          Have you enabled SR-IOV in Integrated Devices on the Dell Server's BIOS?

                                          1 Reply Last reply Reply Quote 0
                                          • X Offline
                                            xerxist @stormi
                                            last edited by xerxist

                                            @stormi

                                            👌🏼😃🚀

                                            It seems it would fix my iGPU passthrough issue with the NUC13 🙂

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