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 2.1m 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.
    • R Offline
      rmaclachlan @Tristis Oris
      last edited by

      @Tristis-Oris Try a yum clean all and then redo your yum update

      XO Update seems to be working well for us on 3 hosts!

      Tristis OrisT 1 Reply Last reply Reply Quote 0
      • Tristis OrisT Offline
        Tristis Oris Top contributor @rmaclachlan
        last edited by

        @rmaclachlan nvm found it. Some long lived cache at repo proxy. Looks i need a wait about 1 extra hour.

        1 Reply Last reply Reply Quote 0
        • jivanpalJ Offline
          jivanpal @stormi
          last edited by

          @stormi I was able to get the new version of xo-lite via yum update (and it's looking good!), so I have everything up to date, though I'm still running Xen 4.13, not Xen 4.17. However, stats in XO (not XO Lite) still aren't working for me for some reason; I'm running XO v5.92.0 (commit 25982ca, from today), built from source. All VMs are running xe-guest-utilities / management agent 7.30.0-2, as that is the version provided by my installation of XCP-ng.

          stormiS 1 Reply Last reply Reply Quote 0
          • T Offline
            ThierryC01 @stormi
            last edited by

            @stormi said in XCP-ng 8.3 beta 🚀:

            @ThierryC01 said in XCP-ng 8.3 beta 🚀:

            For your information, the connection error icon in "Settings"-->"Remotes" that appears when entering a wrong password once, then connecting anyway afterwards with the correct password is still present after all the 8.3 updates.

            Is this an XCP-ng issue?

            After the latest XOA update, the annoying error icon is gone! So it was an XOA issue 🙂

            1 Reply Last reply Reply Quote 1
            • R Offline
              rmaclachlan
              last edited by

              Not sure if this is a known issue, I couldn't find it on Github but maybe I was looking in the wrong spot. Is anyone else's network Bond speeds 0? I thought I had seen a fix a month ago for this in a release but now I can't find that changelog

              3cff6b94-8603-41b1-a962-e0087baf5dfb-image.png

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

                @jivanpal If it persists, please open a new thread in the Xen Orchestra section of the forum.

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

                  I just pushed a few updates to the xcp-ng-base repository for XCP-ng 8.3. Nothing really worth mentioning from the user point of view, so what matters is as usual to ensure no regressions are seen.

                  F P 2 Replies Last reply Reply Quote 0
                  • F Offline
                    flakpyro @stormi
                    last edited by

                    After installing all the latest patches from this week my XOA and xe pif-param-list are both still showing network bonds linking at 0 b/s just like @rmaclachlan pointed out above.

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

                      @stormi
                      In XO updated yesterday, it says: 6 missing patches. but in the patches tab i got no missing pathes ???

                      stormiS 1 Reply Last reply Reply Quote 0
                      • 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
                                • lethedataL 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

                                            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                            With your input, this post could be even better 💗

                                            Register Login
                                            • First post
                                              Last post