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.
    • A Offline
      alexredston
      last edited by

      Hi, very excited by this migration tool, as after much faffing about with Vmware converter I found that my VMs were quite impractical to import do to the size fo the OVA files, so I have built XO with the vmware branch but the xo-cli command does not give me the vm.importFomEsxi / vm.importFromEsxi command.

      Perhaps I am being a muppet? My xo-cli is v0.14.2

      I have also tried checking out the the vmware PR #6595 which is 18 commits ahead.

      Running xo-cli system.getServerVersion I seem to be way ahead on 5.107.5

      Keen to test this important feature out, but a little confused as to how to get the correct version of xo-cli and XO to test it.

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

        Are you using the xo-cli binary built from XO folder?

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

          @alexredston nice catch, the methods weren't listed in list-command, it's fixed on the vmware branch

          Regards

          Florent

          A 1 Reply Last reply Reply Quote 1
          • A Offline
            alexredston
            last edited by

            Hi guys, thank you both for your helpful and very prompt responses. I am just running a build with the latest vmware source and will report back.

            Had hoped to do it over Christmas but it was really busy for us with many colleagues away.

            1 Reply Last reply Reply Quote 0
            • A Offline
              alexredston @florent
              last edited by

              @florent Excellent!

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