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.
    • brezlordB Offline
      brezlord @florent
      last edited by

      @florent https

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

        If you don't have valid certificates, you need to add --allowUnauthorized in the registration command.

        brezlordB 1 Reply Last reply Reply Quote 1
        • brezlordB Offline
          brezlord @olivierlambert
          last edited by

          @olivierlambert said in VMware migration tool: we need your feedback!:

          --allowUnauthorized

          thanks that did it.

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

            Okay, keep us posted on the VMware migration tool then šŸ™‚

            brezlordB 1 Reply Last reply Reply Quote 0
            • brezlordB Offline
              brezlord @olivierlambert
              last edited by

              @olivierlambert what i the esxi vm ID that xo is looking for. I get the below error now.

              root@xoa:~# xo-cli vm.importFromEsxi host=192.168.40.203 user='root' password='password' sslVerify=false vm=11 sr=648548b5-a789-6c72-2518-407a12717fad network=b71bcce1-0d59-0c13-7ca9-f28e24982355
              āœ– method not found: vm.importFromEsxi
              JsonRpcError: method not found: vm.importFromEsxi
                  at Peer._callee$ (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/json-rpc-peer/dist/index.js:139:44)
                  at tryCatch (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:44:17)
                  at Generator.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:125:22)
                  at Generator.next (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:69:21)
                  at asyncGeneratorStep (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
                  at _next (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:9)
                  at /opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/asyncToGenerator.js:27:7
                  at new Promise (<anonymous>)
                  at Peer.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/asyncToGenerator.js:19:12)
                  at Peer.exec (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/json-rpc-peer/dist/index.js:182:20)
              
              1 Reply Last reply Reply Quote 0
              • olivierlambertO Offline
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by

                Have you switched to the right branch, as explained in the first post?

                brezlordB 1 Reply Last reply Reply Quote 0
                • brezlordB Offline
                  brezlord @olivierlambert
                  last edited by

                  @olivierlambert yes vmware

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

                    Ah, there's a typo in the command name, I fixed it in our doc, thinking it was just a typo from the example šŸ˜†

                    vm.importFomEsxi is the "right" command. @florent will fix this šŸ˜‰

                    FYI: xo-cli list-commands will display all the commands, that's how I found out.

                    brezlordB florentF 3 Replies Last reply Reply Quote 1
                    • brezlordB Offline
                      brezlord @olivierlambert
                      last edited by

                      @olivierlambert thanks heaps. Now I get the following error.

                      root@xoa:~# xo-cli vm.importFomEsxi host=192.168.40.203 user='root' password='password' sslVerify=false vm=11 sr=648548b5-a789-6c72-2518-407a12717fad network=83594c5b-8b5b-b45f-d3a7-7e5301468dc8
                      āœ– HANDLE_INVALID(network, OpaqueRef:478f9e9d-7592-40a2-ab07-10a0a6982e45)
                      JsonRpcError: HANDLE_INVALID(network, OpaqueRef:478f9e9d-7592-40a2-ab07-10a0a6982e45)
                          at Peer._callee$ (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/json-rpc-peer/dist/index.js:139:44)
                          at tryCatch (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:44:17)
                          at Generator.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:125:22)
                          at Generator.next (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:69:21)
                          at asyncGeneratorStep (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
                          at _next (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:9)
                          at /opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/asyncToGenerator.js:27:7
                          at new Promise (<anonymous>)
                          at Peer.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/asyncToGenerator.js:19:12)
                          at Peer.exec (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/json-rpc-peer/dist/index.js:182:20)
                      
                      1 Reply Last reply Reply Quote 0
                      • brezlordB Offline
                        brezlord @olivierlambert
                        last edited by

                        @olivierlambert I've created a new network and it's now working, yay.

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

                          Okay please tell us the final outcome šŸ™‚

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

                            @olivierlambert said in VMware migration tool: we need your feedback!:

                            Ah, there's a typo in the command name, I fixed it in our doc, thinking it was just a typo from the example šŸ˜†

                            vm.importFomEsxi is the "right" command. @florent will fix this šŸ˜‰

                            FYI: xo-cli list-commands will display all the commands, that's how I found out.

                            my bad, I pushed the branch, with a lot of fixes , and prelminary work for the delta on esxi 7 ( not working for now )

                            1 Reply Last reply Reply Quote 1
                            • brezlordB Offline
                              brezlord @olivierlambert
                              last edited by

                              @olivierlambert will do, thanks.

                              1 Reply Last reply Reply Quote 0
                              • brezlordB Offline
                                brezlord
                                last edited by

                                Thank you both for your help.

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

                                  You are welcome šŸ™‚ Eager to get your feedback on the outcome, keep us posted!

                                  brezlordB 1 Reply Last reply Reply Quote 0
                                  • brezlordB Offline
                                    brezlord @olivierlambert
                                    last edited by brezlord

                                    @olivierlambert I managed to get a CentOS 7 vm imported and running. I'm now trying to import an Ubuntu vm and I get the bellow error.

                                    root@xoa:~# xo-cli vm.importFomEsxi host=192.168.40.203 user='root' password='password' sslVerify=false vm=12 sr=648548b5-a789-6c72-2518-407a12717fad network=0b3e9312-541d-a036-06b4-2bd63c53d852
                                    āœ– Cannot create property 'detailed' on string 'ubuntu-64'
                                    JsonRpcError: Cannot create property 'detailed' on string 'ubuntu-64'
                                        at Peer._callee$ (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/json-rpc-peer/dist/index.js:139:44)
                                        at tryCatch (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:44:17)
                                        at Generator.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:125:22)
                                        at Generator.next (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:69:21)
                                        at asyncGeneratorStep (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
                                        at _next (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:9)
                                        at /opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/asyncToGenerator.js:27:7
                                        at new Promise (<anonymous>)
                                        at Peer.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/@babel/runtime/helpers/asyncToGenerator.js:19:12)
                                        at Peer.exec (/opt/xo/xo-builds/xen-orchestra-202301220427/node_modules/json-rpc-peer/dist/index.js:182:20)
                                    
                                    florentF 1 Reply Last reply Reply Quote 0
                                    • Y Offline
                                      ysageev
                                      last edited by ysageev

                                      Hi, I am getting the following error:

                                      $ xo-cli vm.importFomEsxi host=192.XXX.XXX.XXX user=USERNAME password=MYPASS sslVerify=false vm=3 sr=d5a9a2f3-3e94-b73f-f8fd-dcefdc356804 network=557d6a0f-ff4c-7692-b342-0671c0a8385b
                                      
                                      Ɨ Cannot read properties of undefined (reading 'current')
                                      JsonRpcError: Cannot read properties of undefined (reading 'current')
                                          at Peer._callee$ (C:\Users\asdf\AppData\Roaming\npm\node_modules\xo-cli\node_modules\json-rpc-peer\dist\index.js:139:44)
                                          at tryCatch (C:\Users\asdf\AppData\Roaming\npm\node_modules\xo-cli\node_modules\@babel\runtime\helpers\regeneratorRuntime.js:44:17)
                                          at Generator.<anonymous> (C:\Users\asdf\AppData\Roaming\npm\node_modules\xo-cli\node_modules\@babel\runtime\helpers\regeneratorRuntime.js:125:22)
                                          at Generator.next (C:\Users\asdf\AppData\Roaming\npm\node_modules\xo-cli\node_modules\@babel\runtime\helpers\regeneratorRuntime.js:69:21)
                                          at asyncGeneratorStep (C:\Users\asdf\AppData\Roaming\npm\node_modules\xo-cli\node_modules\@babel\runtime\helpers\asyncToGenerator.js:3:24)
                                          at _next (C:\Users\asdf\AppData\Roaming\npm\node_modules\xo-cli\node_modules\@babel\runtime\helpers\asyncToGenerator.js:22:9)
                                          at C:\Users\asdf\AppData\Roaming\npm\node_modules\xo-cli\node_modules\@babel\runtime\helpers\asyncToGenerator.js:27:7
                                          at new Promise (<anonymous>)
                                          at Peer.<anonymous> (C:\Users\asdf\AppData\Roaming\npm\node_modules\xo-cli\node_modules\@babel\runtime\helpers\asyncToGenerator.js:19:12)
                                          at Peer.exec (C:\Users\asdf\AppData\Roaming\npm\node_modules\xo-cli\node_modules\json-rpc-peer\dist\index.js:182:20)
                                      
                                      1 Reply Last reply Reply Quote 0
                                      • florentF Offline
                                        florent Vates 🪐 XO Team
                                        last edited by

                                        @brezlord The real error messages are hidden, I will try to fix it

                                        @ysageev does the VM has snapshots ? is it running ?

                                        Y 1 Reply Last reply Reply Quote 0
                                        • Y Offline
                                          ysageev @florent
                                          last edited by ysageev

                                          @florent It is off, no snapshots.

                                          Off:
                                          4710cc84-7eb3-4d2f-9bbd-9fcf898c3dd5-image.png

                                          Files:
                                          e074afac-65b3-42d2-b12e-6919d5380dd8-image.png

                                          I also disabled Change Block Tracking and deleted the ctk file.

                                          If it helps, I'm using ESXi-6.7.0-20190802001-standard and the VM is a 10GB old CentOS.

                                          Update: On the server side, the error looks like this:

                                          vm.importFomEsxi
                                          {
                                            "host": "192.168.1.107",
                                            "user": "XXXXXXX",
                                            "password": "* obfuscated *",
                                            "sslVerify": false,
                                            "vm": "3",
                                            "sr": "d5a9a2f3-3e94-b73f-f8fd-dcefdc356804",
                                            "network": "557d6a0f-ff4c-7692-b342-0671c0a8385b"
                                          }
                                          {
                                            "message": "Cannot read properties of undefined (reading 'current')",
                                            "name": "TypeError",
                                            "stack": "TypeError: Cannot read properties of undefined (reading 'current')
                                              at parseVmsd (file:///usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/vmware-explorer/parsers/vmsd.mjs:48:30)
                                              at Esxi.getTransferableVmMetadata (file:///usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/vmware-explorer/esxi.mjs:250:23)
                                              at processTicksAndRejections (node:internal/process/task_queues:95:5)
                                              at MigrateVm.migrationfromEsxi (file:///usr/local/lib/node_modules/xo-server/src/xo-mixins/migrate-vm.mjs:122:28)
                                              at Xo.importFomEsxi (file:///usr/local/lib/node_modules/xo-server/src/api/vm.mjs:1304:10)
                                              at Api.#callApiMethod (file:///usr/local/lib/node_modules/xo-server/src/xo-mixins/api.mjs:394:20)"
                                          }
                                          

                                          It looks like the presence/dependency of the VMSD file and the tool's attempt to process it has something to do with the problem.

                                          Update: The .vmsd file is empty.

                                          planedropP 1 Reply Last reply Reply Quote 1
                                          • planedropP Online
                                            planedrop Top contributor @ysageev
                                            last edited by

                                            @ysageev I'm running across the same error when trying to do some imports, for testing I deleted the vmsd file (didn't think that would do anything at all) and got an error about not being able to find the VM (which is what I thought would happen), re-added the vmsd but still getting this "cannot read properties of undefined" error.

                                            I also tried with a different VM, this time a Windows one (was Ubuntu on the first try) and get a slightly different error:

                                            Cannot convert undefined or null to object
                                            
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post