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.
    • A Offline
      Ajmind 0 @stormi
      last edited by

      @stormi
      https://xcp-ng.org/forum/post/72099

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

        I am also seeing lots of xcp-networkd errors in xensource.log

        Feb 23 11:41:17 xcpng-test-01 xcp-networkd: [error||3 ||network_utils] Error in read one line of file: /sys/class/net/bond0/device/vendor, exception Unix.Unix_error(Unix.ENOENT, "open", "/sys/class/net/bond0/device/vendor")\x0ARaised by primitive operation at Xapi_stdext_unix__Unixext.with_file in file "lib/xapi-stdext-unix/unixext.ml", line 90, characters 11-40\x0ACalled from Xapi_stdext_unix__Unixext.buffer_of_file in file "lib/xapi-stdext-unix/unixext.ml" (inlined), line 177, characters 31-83\x0ACalled from Xapi_stdext_unix__Unixext.string_of_file in file "lib/xapi-stdext-unix/unixext.ml", line 179, characters 47-73\x0ACalled from Network_utils.Sysfs.read_one_line in file "ocaml/networkd/lib/network_utils.ml", line 156, characters 6-33\x0A
        Feb 23 11:41:22 xcpng-test-01 xcp-networkd: [error||3 ||network_utils] Error in read one line of file: /sys/class/net/bond0/carrier, exception Unix.Unix_error(Unix.ENOENT, "open", "/sys/class/net/bond0/carrier")\x0ARaised by primitive operation at Xapi_stdext_unix__Unixext.with_file in file "lib/xapi-stdext-unix/unixext.ml", line 90, characters 11-40\x0ACalled from Xapi_stdext_unix__Unixext.buffer_of_file in file "lib/xapi-stdext-unix/unixext.ml" (inlined), line 177, characters 31-83\x0ACalled from Xapi_stdext_unix__Unixext.string_of_file in file "lib/xapi-stdext-unix/unixext.ml", line 179, characters 47-73\x0ACalled from Network_utils.Sysfs.read_one_line in file "ocaml/networkd/lib/network_utils.ml", line 156, characters 6-33\x0A
        Feb 23 11:41:22 xcpng-test-01 xcp-networkd: [error||3 ||network_utils] Error in read one line of file: /sys/class/net/bond0/device/device, exception Unix.Unix_error(Unix.ENOENT, "open", "/sys/class/net/bond0/device/device")\x0ARaised by primitive operation at Xapi_stdext_unix__Unixext.with_file in file "lib/xapi-stdext-unix/unixext.ml", line 90, characters 11-40\x0ACalled from Xapi_stdext_unix__Unixext.buffer_of_file in file "lib/xapi-stdext-unix/unixext.ml" (inlined), line 177, characters 31-83\x0ACalled from Xapi_stdext_unix__Unixext.string_of_file in file "lib/xapi-stdext-unix/unixext.ml", line 179, characters 47-73\x0ACalled from Network_utils.Sysfs.read_one_line in file "ocaml/networkd/lib/network_utils.ml", line 156, characters 6-33\x0A
        Feb 23 11:41:22 xcpng-test-01 xcp-networkd: [error||3 ||network_utils] Error in read one line of file: /sys/class/net/bond0/device/vendor, exception Unix.Unix_error(Unix.ENOENT, "open", "/sys/class/net/bond0/device/vendor")\x0ARaised by primitive operation at Xapi_stdext_unix__Unixext.with_file in file "lib/xapi-stdext-unix/unixext.ml", line 90, characters 11-40\x0ACalled from Xapi_stdext_unix__Unixext.buffer_of_file in file "lib/xapi-stdext-unix/unixext.ml" (inlined), line 177, characters 31-83\x0ACalled from Xapi_stdext_unix__Unixext.string_of_file in file "lib/xapi-stdext-unix/unixext.ml", line 179, characters 47-73\x0ACalled from Network_utils.Sysfs.read_one_line in file "ocaml/networkd/lib/network_utils.ml", line 156, characters 6-33\x0A
        
        

        My bond interfaces in XO report as running at 0 b/s as well.

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

          @stormi
          Stats seems to work now

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

            Stats are back after the latest batch of patches.

            1 Reply Last reply Reply Quote 1
            • X Offline
              XCP-ng-JustGreat
              last edited by

              Stats are back in XO after latest XCP-ng 8.3 updates and compiling XO from latest source. That was fast!

              1 Reply Last reply Reply Quote 1
              • olivierlambertO Offline
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by olivierlambert

                Great work from both XCP-ng and XO teams 👍

                1 Reply Last reply Reply Quote 2
                • T Offline
                  TheFrisianClause @jivanpal
                  last edited by

                  @jivanpal No IPv6 addresses are configured on the host, still getting this error when doing yum update

                  failure: repodata/repomd.xml from xcp-ng-base: [Errno 256] No more mirrors to try.
                  http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address"
                  http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address"
                  http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address"
                  http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address"
                  http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address"
                  http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address"
                  http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address"
                  http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address"
                  http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address"
                  http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address"
                  
                  stormiS 1 Reply Last reply Reply Quote 0
                  • A Offline
                    Andrew Top contributor @ravenet
                    last edited by

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

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

                      @TheFrisianClause Please open a separate thread for this, where we'll follow-up (was it you who already had one about this very problem?)

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

                        By the way, it is OK, and even good, to mention any issues you have with 8.3 here. It's what's this thread is for. However, if you don't see any answers because there are too many different discussions happening at the same time, I advise to open a separate thread and mention it here, so that people can jump there and help there.

                        1 Reply Last reply Reply Quote 3
                        • psafontP Offline
                          psafont @rmaclachlan
                          last edited by

                          @rmaclachlan This looks awfully similar to https://github.com/xapi-project/xen-api/pull/5451

                          freddy77 opened this pull request in xapi-project/xen-api

                          closed CP-47754: Do not report errors attempting to read PCI vendor:product #5451

                          1 Reply Last reply Reply Quote 1
                          • 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.0-1.xcpng8.3

                            You can update it like this:

                            yum update xo-lite
                            

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

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

                              @gduperrey should it be available by usual way at XO?

                              yum update xo-lite
                              Loaded plugins: fastestmirror
                              Loading mirror speeds from cached hostfile
                              No packages marked for update
                              
                              R 1 Reply Last reply Reply Quote 0
                              • 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
                                            • First post
                                              Last post