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

      This is an error another user reported through a support ticket. Do others confirm?

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

        I confirm the issue here 🙂

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

          same issue.

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

            Same here (ticket is in).

            Anyone having issues with NFS SR performance too? Since the update my VMs are transferring about 140MB/s vs before the update we were seeing speeds around 440MB/s.

            I'm using "dd if=/dev/zero of=tmp bs=1G oflag=dsync count=1" to test, if I SSH onto the host I can get full speed to the NFS mount but from within a VM it is much slower, this means backups are also crawling since XOA can't read the VHD very quickly.

            iSCSI performance seems unaffected.

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

              Same issue on latest 8.3 release, no stats.

              1 Reply Last reply Reply Quote 1
              • BobTB12B Offline
                BobTB12 @stormi
                last edited by

                @stormi
                OmniOS guest fails to boot in xcp-ng on version 8.3.

                Installation is fine: create a new vm, set viridian=false and installation progress smoothly. I've noticed that installation seem to lack PV-drivers.

                When booting from freshly installed disk it panics with:
                panic[cpu0]/thread=ffffffffffbc490c0: unable to configure /xpvd nexus

                I've tried several version of OmniOS (and latest OpenIndiana), I also tried Solaris 11.4, tried disabling apix with apix_enable=0 in /etc/system and all without success.
                The same setup in xcp-ng 8.0 works like a charm with working PV-drivers (but no tools).

                Anyone with an idea of a workaround or even better, a resolution to this.

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

                  If you have the same problem in 8.2, then it's not 8.3 related.

                  BobTB12B 1 Reply Last reply Reply Quote 0
                  • BobTB12B Offline
                    BobTB12 @olivierlambert
                    last edited by

                    @olivierlambert oh, sorry, got too carried away and did not notice this is 8.3 beta.

                    1 Reply Last reply Reply Quote 1
                    • K Offline
                      kait
                      last edited by

                      can confirm the stats/true granulrity issue as well

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

                        No stats :o(
                        but netdata seems to work

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

                          So we are working on this issue. The format of the JSON output changed, which explains why it doesn't work in XO anymore. We'll fix it either in XCP-ng or in XO, depending on what is the best thing to do.

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

                            @stormi
                            No stats in XO-lite v0.1.7 (0d127) , as you probably already know

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

                              @ph7 Indeed, we know about XO lite too. Thanks 🙂

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

                                And XCP-ng 8.3 Beta 2 finally released!

                                https://xcp-ng.org/blog/2024/02/15/xcp-ng-8-3-beta-2/

                                Fixes are on the way for the stats issue. It involves both XCP-ng and Xen-Orchestra, so this will take a few more days.

                                W 1 Reply Last reply Reply Quote 4
                                • Tristis OrisT Offline
                                  Tristis Oris Top contributor
                                  last edited by

                                  Good news. Release at this year possible?
                                  What xapi version now at 8.2.1? dunno how to check it.

                                  1 Reply Last reply Reply Quote 0
                                  • W Offline
                                    wilsonqanda @stormi
                                    last edited by

                                    @stormi I assume you had issue so took file down as link is giving a 404 page not found? lol

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

                                      8.3 will be obviously released this year @Tristis-Oris 😉

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

                                        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.

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

                                          Has the emergency network reset and xe been updated to handle IPv6 only configurations with patches after Beta2 ISO or is there something special that needs to be done?

                                          I'm not able to pull patches atm and after running the resets it didn't seem to like the v6 addressing and xe refused to set the management interface without v4 set. Couldn't drop the temporary v4 address either.


                                          Looks like the answer is yes but only at boot? "The only way to enable IPv6 for the management interface is at boot time. It's something that can't be modified afterwards in XAPI."

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

                                            This update broke my mellanox network drivers for connectx-4 / 4 LX
                                            Seems this latest patches included update from mennalox-mlnxen 5.4 to 5.9

                                            I have no networking, and after an emergency network reset, eth0 and eth1 disappeared.

                                            update1: used yum downgrade mellanox-mlnxen-5.4_1.0.3.0-4.xcpng8.3.x86_64
                                            this didn't fix until I did another emergency network reset.

                                            Looks like I'm back up and running.
                                            Anyone else able to confirm this bug or am I alone in this hiccup?

                                            A 2 Replies Last reply Reply Quote 0
                                            • First post
                                              Last post