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

    VMware migration tool: we need your feedback!

    Scheduled Pinned Locked Moved Migrate to XCP-ng
    318 Posts 37 Posters 174.3k Views 30 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.
    • olivierlambertO Offline
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by olivierlambert

      Hello!

      Do you have the same issue with XOA on latest? Is your XO from sources is fully up to date on latest master commit?

      D 1 Reply Last reply Reply Quote 0
      • D Offline
        DangerKlaus @olivierlambert
        last edited by DangerKlaus

        Hey @olivierlambert

        I'm using Jarli's install/update script and I ran an update and test before I posted so believe the answer is yes.

        This stack (XCP) was only built in the last 24hr so everything is pretty much up to date.

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

          Okay I would also try with a fully updated XOA on latest channel to compare with your source install. If the result is the same, then @florent will take a look 🙂

          1 Reply Last reply Reply Quote 1
          • florentF Offline
            florent Vates 🪐 XO Team @DangerKlaus
            last edited by

            @DangerKlaus can you try importing only one VM , to see if we have another error message ?

            D 1 Reply Last reply Reply Quote 0
            • D Offline
              DangerKlaus @florent
              last edited by

              @florent It's the same error regardless. Currently testing official XO and will report back asap.

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

                Don't forget to register/update and select "latest" on the release channel. Thanks for your feedback!

                D 1 Reply Last reply Reply Quote 1
                • D Offline
                  DangerKlaus @olivierlambert
                  last edited by DangerKlaus

                  @olivierlambert Okay, there is definitely a difference. I've kicked off a migration and I'm getting a spinning wheel on the import button rather than a flat out error.

                  So I guess is the issue is with source??

                  d4c50771-d8f6-488c-b6b2-8d61d35f7b9a-image.png

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

                    Well, that's a possibility yes. And that's the point of XOA: we test it and we control the environment, so it's a LOT easier to provide pro support for it. Many things can be different on the sources (node version, libs or deps version breaking stuff and such).

                    At least, that's an interesting feedback that either something new since latest XOA broke on master, or the installation is broken.

                    Please let the migration happens and let us know 🙂

                    D 1 Reply Last reply Reply Quote 1
                    • D Offline
                      DangerKlaus @olivierlambert
                      last edited by

                      @olivierlambert
                      Quick update. Import via XOA finished overnight with no error.

                      I can keep both XOA and source running in parallel for now if you need me to do any more testing

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

                        Great news then! The tool will stay free in XOA Free anyway, but as soon as we can, we'll see if we can reproduce the issue on master on our side. If not, maybe you need to wipe/re-clone/rebuild the XO source folder in case. Double check your node version too.

                        1 Reply Last reply Reply Quote 0
                        • F Offline
                          Flying9167
                          last edited by

                          I'm getting the same error from sources and from a fresh XOA fully updated on Latest channel even started a trial of premium. Any ideas?

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

                            @Flying9167 without providing more info on the error nor the VMware version you use, or if your VM is running or not, it's hard to help 😞

                            F 1 Reply Last reply Reply Quote 0
                            • F Offline
                              Flying9167 @olivierlambert
                              last edited by Flying9167

                              @olivierlambert

                              I'm running ESXi 6.7 update 3, trying to transfer a Windows 2019 Server, running or halted I get the same error, I have tried several other vms with the same result. Tried different storage and network options too, all same result.

                              Import
                              Property description must be an object: undefined
                              

                              Running XOA on latest with trial enabled fully up to date, two hosts in pool fully up to date.

                              vm.importMultipleFromEsxi
                              {
                                "concurrency": 2,
                                "host": "192.168.150.39",
                                "network": "d41468b9-53d8-63af-b474-d3062625ce10",
                                "password": "* obfuscated *",
                                "sr": "1477ad1f-0d29-ec1f-fa8e-7b8d3bb04ae4",
                                "sslVerify": false,
                                "stopOnError": true,
                                "stopSource": false,
                                "thin": false,
                                "user": "root",
                                "vms": [
                                  "21",
                                  "20"
                                ]
                              }
                              {
                                "succeeded": {},
                                "message": "Property description must be an object: undefined",
                                "name": "TypeError",
                                "stack": "TypeError: Property description must be an object: undefined
                                  at Function.defineProperty (<anonymous>)
                                  at Task.onProgress (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/combineEvents.js:51:16)
                                  at Task.#emit (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:130:21)
                                  at Task.#emit (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:124:17)
                                  at Function.set (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:47:17)
                                  at file:///usr/local/lib/node_modules/xo-server/src/api/vm.mjs:1388:20
                                  at Task.runInside (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:149:22)
                                  at Task.run (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:134:20)
                                  at asyncEach.concurrency.concurrency (file:///usr/local/lib/node_modules/xo-server/src/api/vm.mjs:1372:11)"
                              }
                              
                              

                              Even selecting just 1 vm at a time produces the same error

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

                                Are you sure the halted VM doesn't have any snapshot?

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

                                  New user to XCP-NG.
                                  Testing the migration from ESXi and i am getting the following message in log.
                                  Property description must be an object: undefined

                                  ESXi client is version 8.0.0

                                  I am able to connect from XCP-NG and see my VMs but cant import any of them. Is there another workaround than using XOA?

                                  edit: I have tried suspending and shutdown my VM on ESXi and still get the same error.

                                  vm.importMultipleFromEsxi
                                  {
                                    "concurrency": 2,
                                    "host": "192.168.50.20",
                                    "network": "61289739-1df5-c88d-770c-78287d9d72a5",
                                    "password": "* obfuscated *",
                                    "sr": "0b002e97-e812-8626-f4e0-2c6267c62296",
                                    "sslVerify": false,
                                    "stopOnError": true,
                                    "stopSource": false,
                                    "thin": false,
                                    "user": "admin",
                                    "vms": [
                                      "1"
                                    ]
                                  }
                                  {
                                    "succeeded": {},
                                    "message": "Property description must be an object: undefined",
                                    "name": "TypeError",
                                    "stack": "TypeError: Property description must be an object: undefined
                                      at Function.defineProperty (<anonymous>)
                                      at Task.onProgress (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/combineEvents.js:51:16)
                                      at Task.#emit (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:130:21)
                                      at Task.#emit (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:124:17)
                                      at Function.set (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:47:17)
                                      at file:///usr/local/lib/node_modules/xo-server/src/api/vm.mjs:1388:20
                                      at Task.runInside (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:149:22)
                                      at Task.run (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:134:20)
                                      at asyncEach.concurrency.concurrency (file:///usr/local/lib/node_modules/xo-server/src/api/vm.mjs:1372:11)"
                                  }
                                  
                                  1 Reply Last reply Reply Quote 0
                                  • olivierlambertO Offline
                                    olivierlambert Vates 🪐 Co-Founder CEO
                                    last edited by

                                    You need to be sure the VM is halted and doesn't have any snapshot 🙂

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

                                      @olivierlambert to be clear as i mentioned in my post, the VMs are shut down.

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

                                        Are you using XOA on latest channel? My question holds regarding the presence of a snapshot for this VM 🙂

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

                                          @olivierlambert just about to edit my comment 🙂
                                          There are no snapshots. I shutdown the VM at the time.

                                          bc1c3b03-51b5-4f98-9751-56fd04dded51-image.png

                                          a8dd09ae-1b3a-4b15-8927-e0ae490a3e48-image.png

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

                                            @florent will take a look tomorrow (it's V-day here)

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