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.4k 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.
    • Y Offline
      ysageev @alexredston
      last edited by

      @alexredston How do we get the "vmware branch" so that we can execute importFomEsxi? I also just used 0.14.2 and have the same problem.

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

        @ysageev if you are using XO from the sources, you should know how to change a branch on Git šŸ˜‰
        If you are on XOA, it's just typing vmware in the custom release channel.

        1 Reply Last reply Reply Quote 0
        • olivierlambertO olivierlambert referenced this topic on
        • brezlordB Offline
          brezlord
          last edited by

          I'm running the latest build form source and from the vmware branch but I cant get the import from ESXi to XCP-ng working, below is the error.

          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
          āœ– no server to connect to!
          Error: no server to connect to!
              at connect (file:///opt/xo/xo-builds/xen-orchestra-202301220427/packages/xo-cli/index.mjs:35:11)
              at async Object.call (file:///opt/xo/xo-builds/xen-orchestra-202301220427/packages/xo-cli/index.mjs:425:14)
              at async main (file:///opt/xo/xo-builds/xen-orchestra-202301220427/packages/xo-cli/index.mjs:268:12)
          

          Any help would be appreciated.

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

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

            192.168.40.203

            hi,

            are you sure the XO server can access this ip ? is there an esxi 6 / 7 running there ?

            regards

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

              @florent it's esxi 7 and yes XO is in the same sub net and can ping the esxi server

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

                @brezlord before using xo-cli to connect to the esxi, you must connect xo-cli to your installation

                with xo-cli --register <url of your xo> <login> and it will sk for the password

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

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

                  xo-cli --register

                  I get the following error when regisering.

                  root@xoa:~# xo-cli --register xoa.corp.com 'admin@corp.com'
                  Password: ************
                  āœ– unable to verify the first certificate
                  Error: unable to verify the first certificate
                      at TLSSocket.onConnectSecure (node:_tls_wrap:1545:34)
                      at TLSSocket.emit (node:events:513:28)
                      at TLSSocket._finishInit (node:_tls_wrap:959:8)
                      at ssl.onhandshakedone (node:_tls_wrap:743:12)
                  
                  florentF 1 Reply Last reply Reply Quote 0
                  • florentF Offline
                    florent Vates 🪐 XO Team @brezlord
                    last edited by

                    @brezlord is your xo in http or https ?

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

                      @florent https

                      1 Reply Last reply Reply Quote 0
                      • olivierlambertO Online
                        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 Online
                            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 Online
                                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 Online
                                    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 Online
                                          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
                                            • First post
                                              Last post