XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    🛰️ XO 6: dedicated thread for all your feedback!

    Scheduled Pinned Locked Moved Xen Orchestra
    69 Posts 22 Posters 2.9k Views 22 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.
    • pdoniasP Offline
      pdonias Vates 🪐 XO Team @ph7
      last edited by

      @ph7 said in 🛰️ XO 6: dedicated thread for all your feedback!:

      I'm not sure if it's a good idea to show a Backup issue every time a Cont.rep. job is run

      Thanks for the feedback, we'll fix that!

      @XCP-ng-JustGreat said in 🛰️ XO 6: dedicated thread for all your feedback!:

      However, the periodic console refresh interrupts the performing of actual work

      We'll investigate that issue, thanks for the report.

      @ph7 said in 🛰️ XO 6: dedicated thread for all your feedback!:

      In ContRep, Conf/meta and in one of the Full Backup jobs I get Report when Never. But they are enabled in XO5 with mail address and Report when Skipped and failure

      This definitely looks like a bug, we'll check that, thanks again!

      @cmoriarty said in 🛰️ XO 6: dedicated thread for all your feedback!:

      It seems now these VM Notes are stuffed into a small "Description" field inside the "Quick Info" panel for a VM.

      Notes and descriptions are 2 separate things. We haven't added notes in XO 6 yet, but don't worry, we will! And XO 5 and XO 6 will be available side by side until XO 6 is fully usable, so you're not going to lose your notes, no need to back them up 🙂

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

        FYI, we are adding a more structured way to get your feedback on missing features that you consider the most important: https://feedback.vates.tech

        You can sign in with your email or via your Github or Discord account.

        P 1 Reply Last reply Reply Quote 2
        • P Offline
          Pilow @olivierlambert
          last edited by

          @olivierlambert nice, better than megathreads ! 😃 added my first TAG demand on it

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

            Hi,

            Just pulled the last commit and see that v6 become the "default" endpoint.

            Unfortunatly, I have to rollback, any user can connect, SSO (oidc) is broken, I think it's not fully implemented yet ?

            callback URL give a "Internal Server Error"; adding "/v5" make a loop with login screen...

            There is any trick to diable v6 by default ? Or make OIDC works ?

            Thank you and have a good day

            MathieuRAM 1 Reply Last reply Reply Quote 0
            • MathieuRAM Offline
              MathieuRA Vates 🪐 XO Team @Kptainflintt
              last edited by

              @Kptainflintt Please provide us the XO-server log that concerns the connection error, authentication is supposed to work as before.

              K 1 Reply Last reply Reply Quote 0
              • K Offline
                Kptainflintt @MathieuRA
                last edited by

                @MathieuRA

                Hi,

                That's the wired thing, no error in logs...

                But I found why : I have "profile" scope in my OIDC configuration for a while, it seems to broke SSO in last version. Without it, it works.

                Thank you

                1 Reply Last reply Reply Quote 1
                • S Offline
                  skipthompson81
                  last edited by

                  Subject: XO 6 is unusable without Migration tools

                  I just updated and was presented with the XO 6 interface. I am shocked to find that the "Migrate" functionality is missing from the UI.

                  Moving a VM is the most fundamental feature of a hypervisor management tool. Making an interface the default—or even presenting it as a viable preview—without this feature is a major workflow breaker. I shouldn't have to revert to the CLI or hunt for a "legacy view" toggle just to perform basic maintenance.

                  Please prioritize porting the migration/lifecycle actions before pushing users toward this interface. It makes the product feel broken.

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

                    Hi @skipthompson81

                    Have you read the release announcement? You can upvote your most important features at https://feedback.vates.tech

                    S 1 Reply Last reply Reply Quote 1
                    • S Offline
                      skipthompson81 @olivierlambert
                      last edited by

                      @olivierlambert i voted. thanks

                      M 1 Reply Last reply Reply Quote 1
                      • M Offline
                        manilx @skipthompson81
                        last edited by manilx

                        Just did my RPU and checked on the new v6 interface.
                        The old one has task details that are missing on the new one (or I didn't find them:

                        ScreenShot 2025-12-19 at 09.36.54.png
                        ScreenShot 2025-12-19 at 09.37.00.png

                        I like to see the evacuation tasks happening (in the past I could identify hangs etc)

                        Here instead of the ID of the VM host the real names should be shown:
                        ScreenShot 2025-12-19 at 09.55.11.png

                        M 1 Reply Last reply Reply Quote 0
                        • M Offline
                          manilx @manilx
                          last edited by

                          As shown above the evacuation tasks are not shown.
                          The last steps migrating thre VM's to the original place are shown:
                          ScreenShot 2025-12-19 at 09.56.44.png

                          M 1 Reply Last reply Reply Quote 0
                          • M Offline
                            manilx @manilx
                            last edited by

                            Also here the task progression can't be followed (stays at 0% until completed):
                            ScreenShot 2025-12-19 at 10.01.37.png
                            instead of
                            ScreenShot 2025-12-19 at 10.01.28.png

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