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

    Error importing vhd or VM

    Xen Orchestra
    5
    47
    842
    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
      Gheppy
      last edited by

      import is ok
      9db9f4be-a970-4e89-b800-8ff6353c534b-image.png

      1 Reply Last reply Reply Quote 1
      • olivierlambertO
        olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼
        last edited by

        Good, then it's maybe your XO build. Could you try on a fresh XOA fully up to date on latest?

        G 1 Reply Last reply Reply Quote 0
        • G
          Gheppy @olivierlambert
          last edited by

          @olivierlambert
          XOA or XO form source ?

          1 Reply Last reply Reply Quote 0
          • olivierlambertO
            olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼
            last edited by olivierlambert

            I specifically said "XOA", so it's XOA 😉 There's no "latest" on XO from the sources.

            G 1 Reply Last reply Reply Quote 0
            • G
              Gheppy @olivierlambert
              last edited by

              @olivierlambert
              For this I need to do a little more work, it gives the same error on import for xoa_unified.xva.
              I'm going to bring the XOCE to a working version so I can import the xva

              1 Reply Last reply Reply Quote 0
              • olivierlambertO
                olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼
                last edited by

                You can deploy XOA without XO. See https://xen-orchestra.com/#!/xoa for example.

                G 1 Reply Last reply Reply Quote 0
                • G
                  Gheppy @olivierlambert
                  last edited by

                  @olivierlambert
                  I have no internet for this network

                  1 Reply Last reply Reply Quote 0
                  • olivierlambertO
                    olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼
                    last edited by

                    Then use xe CLI to import manually the XVA. But you'll need to update XOA with an internet access, in order to be on latest version.

                    G 1 Reply Last reply Reply Quote 0
                    • G
                      Gheppy @olivierlambert
                      last edited by Gheppy

                      @olivierlambert

                      I managed to import it with XCP-ng Center (it was easier that way). After the update to latest, the same problem.
                      xo-server 5.109.0 xo-web 5.111.0

                      Edit:
                      Downgrade to stable the same problem, but after 2 minutes of transfer
                      xo-server 5.107.5 xo-web 5.109.0

                      1 Reply Last reply Reply Quote 0
                      • olivierlambertO
                        olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼
                        last edited by

                        Is it possible to have access to this VHD file?

                        G 1 Reply Last reply Reply Quote 0
                        • G
                          Gheppy @olivierlambert
                          last edited by Gheppy

                          @olivierlambert
                          Ill share this vhd

                          On XOA stable I exported the VM and imported and all is ok, but on XOA I cant export VHD file ( no options)

                          Edit:
                          On XOA latest, I exported the VM (xva) and imported with no success

                          1 Reply Last reply Reply Quote 0
                          • olivierlambertO
                            olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼
                            last edited by

                            You can export a VHD in XO. On the SR/disk tab, you should have an "export" icon to get the VHD.

                            G 1 Reply Last reply Reply Quote 0
                            • G
                              Gheppy @olivierlambert
                              last edited by

                              @olivierlambert
                              This is what I have on XO on SR/disk tab
                              cd3e0171-f3c7-422f-a609-d3908000b4bf-image.png

                              And this on XOCE
                              7c855b2f-ca13-4b2c-b4a3-5ac8941a9ae2-image.png

                              1 Reply Last reply Reply Quote 0
                              • olivierlambertO
                                olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼
                                last edited by

                                Yes, that's the export button. Are you on XOA Free for the first screenshot?

                                G 1 Reply Last reply Reply Quote 0
                                • G
                                  Gheppy @olivierlambert
                                  last edited by

                                  @olivierlambert
                                  yes, I use XOA Free

                                  1 Reply Last reply Reply Quote 0
                                  • olivierlambertO
                                    olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼
                                    last edited by

                                    Can you try on XOA in trial? (if you trial expired, PM me your registered email so I can extend it)

                                    1 Reply Last reply Reply Quote 0
                                    • G
                                      Gheppy
                                      last edited by Gheppy

                                      I don't know how, but:

                                      • XOA trial export can be imported with XOCE commit cf4a1d7d40a16f08122ce7487dce7c8ab9d73513
                                      • XOCE export can not be imported with XOA trial
                                      • XOA trial export can not be imported with the same XOA trial

                                      I tested this 3 times with the same result

                                      Edit:
                                      I update XOCE in this morning and:

                                      • XOCE commit cf4a1d7d40a16f08122ce7487dce7c8ab9d73513 export, now can be imported with XOCE same commit, but not with XOA trial
                                      • XOCE commit 675405f7ace55411b1ca0bbed8b9e31504fcc387 export can be imported with XOCE commit cf4a1d7d40a16f08122ce7487dce7c8ab9d73513, but not with XOA trial

                                      I'll downgrade to XOCE commit 675405f7ace55411b1ca0bbed8b9e31504fcc387 to see what happens when I import XOCE commit cf4a1d7d40a16f08122ce7487dce7c8ab9d73513 export

                                      Edit2:
                                      It seems that the problem no longer appears after the commit cf4a1d7d40a16f08122ce7487dce7c8ab9d73513, for now
                                      I still can't import with XOA trial, both VMs (XOA and XOCE) are on the same server.

                                      1 Reply Last reply Reply Quote 0
                                      • G
                                        Gheppy
                                        last edited by Gheppy

                                        With commit 9ff305d5db2028c989df4b362db828f5bbb5b1b3, I get this error and can't export VM or VHD

                                        HTTP handler of vm.import
                                        undefined
                                        {
                                          "message": "Xapi#watchTask() requires events watching",
                                          "name": "Error",
                                          "stack": "Error: Xapi#watchTask() requires events watching
                                            at Xapi.watchTask (/opt/xen-orchestra/packages/xen-api/src/index.js:691:13)
                                            at Xapi.createTask (/opt/xen-orchestra/packages/xen-api/src/index.js:636:10)
                                            at runNextTicks (node:internal/process/task_queues:60:5)
                                            at processImmediate (node:internal/timers:447:9)
                                            at process.callbackTrampoline (node:internal/async_hooks:130:17)
                                            at Xapi._importVm (file:///opt/xen-orchestra/packages/xo-server/src/xapi/index.mjs:662:21)
                                            at Xapi.importVm (file:///opt/xen-orchestra/packages/xo-server/src/xapi/index.mjs:795:48)"
                                        } 
                                        

                                        And I get this on tasks
                                        a30a0971-5a0f-4272-8375-72604b598a2d-image.png

                                        julien-fJ 1 Reply Last reply Reply Quote 0
                                        • julien-fJ
                                          julien-f Vates 🪐 Co-Founder🦸 XO Team 🔭 @Gheppy
                                          last edited by

                                          @Gheppy I've just pushed a fix for this, I'm still investigating some issues regarding VDI upload, I'll let you know.

                                          https://github.com/vatesfr/xen-orchestra/commit/9f4fce9daa75b418d099928d1ab37a0b2cdd3078

                                          0 julien-f committed to vatesfr/xen-orchestra
                                          fix(xen-api): fix task watchers when initially not watching events
                                          
                                          Introduced by bc61dd85c
                                          julien-fJ 1 Reply Last reply Reply Quote 0
                                          • julien-fJ
                                            julien-f Vates 🪐 Co-Founder🦸 XO Team 🔭 @julien-f
                                            last edited by julien-f

                                            @Gheppy I've identified the root cause, I'm waiting for Node.js' devs feedback before pushing a fix.

                                            In the meantime you can work-around it by setting this in your xo-server's config:

                                            [http.listenOptions]
                                            requestTimeout = 0
                                            

                                            Edit: This work-around is broken (c.f. this GitHub issue) and should not be used. Also, it's no longer necessary, XO integrates the necessary work-around.

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