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

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

    Scheduled Pinned Locked Moved Xen Orchestra
    206 Posts 46 Posters 24.6k Views 37 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.
    • G Online
      Greg_E @MajorP93
      last edited by

      @MajorP93

      Before the LTS release UEFI worked extremely well, something kind of went sideways when it hit release. I only have a single UEFI VM, it was created under version 8.2 and does not give me trouble.

      I guess I need to get my lab back up, had a UPS fail and shut everything off a few days ago. Then I need to test UEFI VMs and see what I can see. But back when it went LTS I reinstalled from scratch and tried to do everything through XO-lite to get the first VM running and found that Debian 13 or Windows Server 2022 would not boot if I created them with UEFI. Since then I haven't tested this again.

      I'm also tempted to just move my whole lab to version 9, waiting for the next ISO to land and I may do this. I can run real testing workloads on Harvester for the time being and maybe play around migrating back and forth between both systems.

      1 Reply Last reply Reply Quote 0
      • P Online
        probain @probain
        last edited by

        probain said:

        Unfortunately, commit https://github.com/vatesfr/xen-orchestra/pull/9727 doesn't fix this issue of the VM-console reloading constantly. With loss of focus as a result. At least not on XO6..

        pierre-briffaux opened this pull request in vatesfr/xen-orchestra

        closed fix(vm/console): fix VNC reconnection causing focus loss #9727

        1 Reply Last reply Reply Quote 0
        • B Online
          Baronvaile
          last edited by

          After upgrading from 6.3.3 to the new 6.4.0 release, the dashboard page for xoa 6 is just spinning. v5 seem unaffected after the update. I have restarted the xoa vm. The xoa-updated show all up to date and xoa check shows healthy.
          040b86f5-9129-4f4c-9af9-7af3184936b7-image.jpeg

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

            @Baronvaile
            Have You tested wit CTRL-F5 to update Your browser

            B 1 Reply Last reply Reply Quote 0
            • B Online
              Baronvaile @ph7
              last edited by

              @ph7 I have. Also same condition in Chrome and Edge.

              acebmxerA P 2 Replies Last reply Reply Quote 0
              • acebmxerA Online
                acebmxer @Baronvaile
                last edited by acebmxer

                @Baronvaile

                Just to confirm this is with actual XOA and not XO from sources? Have you rebooted XO? Check logs? sudo journalctl -u xo-server -n 50

                Edit - Just updated my home lab XOA

                Screenshot 2026-04-30 103224.png

                Screenshot 2026-04-30 103426.png

                I see same thing... XO from sources no issues. Work XOA no issues...
                Screenshot 2026-04-30 103451.png

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

                  @Baronvaile
                  Started my 6.4.0 test VM and got the same
                  Screenshot 2026-04-30 at 16-27-51 Xen Orchestra.png

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

                    My is XOA

                    acebmxerA 1 Reply Last reply Reply Quote 0
                    • acebmxerA Online
                      acebmxer @ph7
                      last edited by acebmxer

                      I am seeing these errors....

                      [09:45 30] xoa@xoa:~$ sudo journalctl -u xo-server -p warning --no-pager
                      Mar 13 13:13:52 xoa systemd[1]: xo-server.service: State 'stop-sigterm' timed out. Killing.
                      Mar 13 13:13:52 xoa systemd[1]: xo-server.service: Main process exited, code=killed, status=9/KILL
                      Mar 13 13:13:52 xoa systemd[1]: xo-server.service: Failed with result 'timeout'.
                      -- Boot 8398ef48e4e94d27b11bfc3300a68727 --
                      Apr 25 11:37:14 xoa systemd[1]: xo-server.service: State 'stop-sigterm' timed out. Killing.
                      Apr 25 11:37:14 xoa systemd[1]: xo-server.service: Main process exited, code=killed, status=9/KILL
                      Apr 25 11:37:14 xoa systemd[1]: xo-server.service: Failed with result 'timeout'.
                      -- Boot 9a9a6f09bdea43729cbe3aa74acc7a3b --
                      Apr 30 09:36:06 xoa systemd[1]: xo-server.service: State 'stop-sigterm' timed out. Killing.
                      Apr 30 09:36:06 xoa systemd[1]: xo-server.service: Main process exited, code=killed, status=9/KILL
                      Apr 30 09:36:06 xoa systemd[1]: xo-server.service: Failed with result 'timeout'.
                      [09:45 30] xoa@xoa:~$ sudo journalctl -u xo-server -f
                      Apr 30 09:43:14 xoa xo-server[594]:       at Function.emit (node:events:519:28)
                      Apr 30 09:43:14 xoa xo-server[594]:       at Function.emit (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17)
                      Apr 30 09:43:14 xoa xo-server[594]:       at Server.<anonymous> (file:///usr/local/lib/node_modules/xo-server/src/index.mjs:977:13)
                      Apr 30 09:43:14 xoa xo-server[594]:       at Server.emit (node:events:531:35)
                      Apr 30 09:43:14 xoa xo-server[594]:       at Server.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17)
                      Apr 30 09:43:14 xoa xo-server[594]:       at onParserExecuteCommon (node:_http_server:977:14)
                      Apr 30 09:43:14 xoa xo-server[594]:       at onParserExecute (node:_http_server:881:3) {
                      Apr 30 09:43:14 xoa xo-server[594]:     code: 'DEP0060'
                      Apr 30 09:43:14 xoa xo-server[594]:   }
                      Apr 30 09:43:14 xoa xo-server[594]: }
                      
                      1 Reply Last reply Reply Quote 0
                      • B Online
                        Baronvaile @acebmxer
                        last edited by Baronvaile

                        @acebmxer Correct, this is with XOA. While watching the journalctl and launching XOA in chrome, I get this output. 43a82668-4f1d-480c-bc0a-ce19ab7043cb-image.jpeg

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

                          [17:00 30] xoa@xoa:~$ sudo journalctl -u xo-server -f
                          Apr 30 16:23:13 xoa xo-server[569]: 2026-04-30T14:23:13.264Z xo:main INFO Setting up / → /usr/local/lib/node_modules/@xen-orchestra/web/dist
                          Apr 30 16:26:27 xoa xo-server[569]: 2026-04-30T14:26:27.942Z xo:rest-api:error-handler INFO [GET] /users/370331c9-fe77-49db-b2a0-e38f776607bd (403)
                          Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.549Z xo:rest-api:error-handler INFO [GET] /pools (403)
                          Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.555Z xo:rest-api:error-handler INFO [GET] /hosts (403)
                          Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.563Z xo:rest-api:error-handler INFO [GET] /vms (403)
                          Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.627Z xo:rest-api:error-handler INFO [GET] /tasks (403)
                          Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.812Z xo:rest-api:error-handler INFO [GET] /alarms (403)
                          Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.812Z xo:rest-api:error-handler INFO [GET] /vm-controllers (403)
                          Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.813Z xo:rest-api:error-handler INFO [GET] /vdis (403)
                          Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.813Z xo:rest-api:error-handler INFO [GET] /srs (403)
                          
                          1 Reply Last reply Reply Quote 0
                          • acebmxerA Online
                            acebmxer
                            last edited by

                            I didnt refresh the page when i ran the blow command before.

                            xoa@xoa:~$ sudo journalctl -u xo-server -f
                            Apr 30 10:28:02 xoa xo-server[568]:     at new Promise (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:103:10)
                            Apr 30 10:28:02 xoa xo-server[568]:     at Peer.request (/usr/local/lib/node_modules/xo-server-xoa/node_modules/json-rpc-peer/src/index.js:139:12)
                            Apr 30 10:28:02 xoa xo-server[568]:     at JsonRpcWebSocketClient.call (/usr/local/lib/node_modules/xo-server-xoa/node_modules/jsonrpc-websocket-client/src/index.js:63:23)
                            Apr 30 10:28:02 xoa xo-server[568]:     at Xoa.apply [as _getCurrentChannel] (/usr/local/lib/node_modules/xo-server-xoa/src/index.js:704:45)
                            Apr 30 10:28:02 xoa xo-server[568]:     at Xo.<anonymous> (file:///usr/local/lib/node_modules/xo-server/src/xo.mjs:256:24)
                            Apr 30 10:28:02 xoa xo-server[568]:     at Config.getGuiRoutes (file:///usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/mixins/Config.mjs:102:52)
                            Apr 30 10:28:02 xoa xo-server[568]:     at main (file:///usr/local/lib/node_modules/xo-server/src/index.mjs:1037:56)
                            Apr 30 10:28:02 xoa xo-server[568]: 2026-04-30T15:28:02.981Z xo:main INFO Setting up /v5 → /usr/local/lib/node_modules/xo-web/dist
                            Apr 30 10:28:02 xoa xo-server[568]: 2026-04-30T15:28:02.981Z xo:main INFO Setting up /v6 → /usr/local/lib/node_modules/@xen-orchestra/web/dist
                            Apr 30 10:28:02 xoa xo-server[568]: 2026-04-30T15:28:02.981Z xo:main INFO Setting up / → /usr/local/lib/node_modules/@xen-orchestra/web/dist
                            Apr 30 10:29:00 xoa xo-server[568]: 2026-04-30T15:29:00.487Z xo:rest-api:error-handler INFO [GET] /users/f1397281-6d64-442b-a78c-e53fea09aa76 (403)
                            Apr 30 10:29:01 xoa xo-server[568]: 2026-04-30T15:29:01.014Z xo:rest-api:error-handler INFO [GET] /pools (403)
                            Apr 30 10:29:01 xoa xo-server[568]: 2026-04-30T15:29:01.020Z xo:rest-api:error-handler INFO [GET] /hosts (403)
                            Apr 30 10:29:01 xoa xo-server[568]: 2026-04-30T15:29:01.027Z xo:rest-api:error-handler INFO [GET] /vms (403)
                            Apr 30 10:29:01 xoa xo-server[568]: 2026-04-30T15:29:01.044Z xo:rest-api:error-handler INFO [GET] /tasks (403)
                            Apr 30 10:29:01 xoa xo-server[568]: 2026-04-30T15:29:01.077Z xo:rest-api:error-handler INFO [GET] /alarms (403)
                            Apr 30 10:29:01 xoa xo-server[568]: 2026-04-30T15:29:01.079Z xo:rest-api:error-handler INFO [GET] /vm-controllers (403)
                            Apr 30 10:29:01 xoa xo-server[568]: 2026-04-30T15:29:01.082Z xo:rest-api:error-handler INFO [GET] /vdis (403)
                            Apr 30 10:29:01 xoa xo-server[568]: 2026-04-30T15:29:01.088Z xo:rest-api:error-handler INFO [GET] /srs (403)
                            Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.204Z xo:rest-api:error-handler INFO [GET] /users/f1397281-6d64-442b-a78c-e53fea09aa76 (403)
                            Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.748Z xo:rest-api:error-handler INFO [GET] /alarms (403)
                            Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.751Z xo:rest-api:error-handler INFO [GET] /vm-controllers (403)
                            Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.751Z xo:rest-api:error-handler INFO [GET] /srs (403)
                            Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.751Z xo:rest-api:error-handler INFO [GET] /vdis (403)
                            Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.753Z xo:rest-api:error-handler INFO [GET] /pools (403)
                            Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.778Z xo:rest-api:error-handler INFO [GET] /hosts (403)
                            Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.778Z xo:rest-api:error-handler INFO [GET] /vms (403)
                            Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.784Z xo:rest-api:error-handler INFO [GET] /tasks (403)
                            
                            MathieuRAM 1 Reply Last reply Reply Quote 0
                            • MathieuRAM Online
                              MathieuRA Vates 🪐 XO Team @acebmxer
                              last edited by

                              Hello, I'm investigating the problem.

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

                                Can someone open a support tunnel, so that i can test a fix?

                                PR: https://github.com/vatesfr/xen-orchestra/pull/9798

                                MathieuRA opened this pull request in vatesfr/xen-orchestra

                                open fix(rest-api): early return for admin user in acl check #9798

                                B 1 Reply Last reply Reply Quote 0
                                • B Online
                                  Baronvaile @MathieuRA
                                  last edited by

                                  @MathieuRA
                                  5d11339a-b442-4f0f-835c-d382b6d4f954-image.jpeg

                                  MathieuRAM B 2 Replies Last reply Reply Quote 0
                                  • MathieuRAM Online
                                    MathieuRA Vates 🪐 XO Team @Baronvaile
                                    last edited by

                                    Thanks @Baronvaile. Can i restart xo-server?

                                    acebmxerA 1 Reply Last reply Reply Quote 0
                                    • B Online
                                      Baronvaile @Baronvaile
                                      last edited by

                                      Sorry, I was out for a bit. Yes, you can restart my xoa.

                                      MathieuRAM 1 Reply Last reply Reply Quote 0
                                      • acebmxerA Online
                                        acebmxer @MathieuRA
                                        last edited by

                                        @MathieuRA

                                        If you still are waiting i have opened a support tunnel - 35965 this is for my home lab. You may reboot XOA if needed.

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

                                          Thanks @Baronvaile, the fix seems to work.

                                          @acebmxer i will also patch your XOA, It's better to have several confirmations

                                          1 Reply Last reply Reply Quote 0
                                          • B Online
                                            Baronvaile
                                            last edited by

                                            Can confirm that XOA v6 looks good now. 048ca0ab-1b29-49b6-aa5c-ee0744e6d391-image.jpeg

                                            MathieuRAM 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