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
    298 Posts 33 Posters 160.8k Views
    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
      olivierlambert Vates šŸŖ Co-Founder CEO
      last edited by

      The problem by doing that automatically is you can have bad surprises. We'll probably just skip it after adding the option.

      1 Reply Last reply Reply Quote 1
      • S
        severhart @florent
        last edited by severhart

        @florent none of the drives are over 2tb, largest is 900GB, so I will assume it is due to snapshots?

        Drives are
        127GB
        900GB
        325GB
        250GB
        500GB

        1 Reply Last reply Reply Quote 0
        • olivierlambertO
          olivierlambert Vates šŸŖ Co-Founder CEO
          last edited by

          @severhart as Flo said, it's because of your VMware version (6.5+) that is using another "diff" format not yet supported. In your case, you should do a cold migration for now, until we support this diff format šŸ™‚

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

            Total noob here jumping in at the deep end.

            I get

             xo-cli vm.importFromEsxi host=xxx.xxx.xxx.xxx user=w...w password='u .... l' sslVerify=false vm=16 network=a1044bf9-4c06-8ae0-060c-e3462dd4524f sr=9b465ed4-e6d2-7a67-b5e0-5edc4915adac stopSource=true thin=true  

āœ– Cannot read properties of undefined (reading 'stream')
JsonRpcError: Cannot read properties of undefined (reading 'stream')
    at Peer._callee$ (/opt/xo/xo-builds/xen-orchestra-202302081722/node_modules/json-rpc-peer/dist/index.js:139:44)
    at tryCatch (/opt/xo/xo-builds/xen-orchestra-202302081722/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:44:17)
    at Generator.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202302081722/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:125:22)
    at Generator.next (/opt/xo/xo-builds/xen-orchestra-202302081722/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:69:21)
    at asyncGeneratorStep (/opt/xo/xo-builds/xen-orchestra-202302081722/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
    at _next (/opt/xo/xo-builds/xen-orchestra-202302081722/node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:9)
    at /opt/xo/xo-builds/xen-orchestra-202302081722/node_modules/@babel/runtime/helpers/asyncToGenerator.js:27:7
    at new Promise (<anonymous>)
    at Peer.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202302081722/node_modules/@babel/runtime/helpers/asyncToGenerator.js:19:12)
    at Peer.exec (/opt/xo/xo-builds/xen-orchestra-202302081722/node_modules/json-rpc-peer/dist/index.js:182:20)
            florentF 1 Reply Last reply Reply Quote 0
            • olivierlambertO
              olivierlambert Vates šŸŖ Co-Founder CEO
              last edited by

              Hey @magicker can you give us more details? Are you using XOA or XO from the sources? At which version? Also on VMware side, what's your ESXi version?

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

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

                XO from the sources

                XO from github (2 days old)

                esxi .. 7.0.0 (Build 16324942)

                1 Reply Last reply Reply Quote 0
                • olivierlambertO
                  olivierlambert Vates šŸŖ Co-Founder CEO
                  last edited by olivierlambert

                  So the diff for warm migration isn't supported on ESXi 7.0 (yet!). So your VM must be halted first (on the VMware side I mean)

                  M 1 Reply Last reply Reply Quote 0
                  • florentF
                    florent Vates šŸŖ XO Team @magicker
                    last edited by florent

                    hi @magicker

                    you should also have additionnal logs in your xo logs

                    Thank you for testing it

                    regards

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

                      @olivierlambert ah I see.. other than that!! it works.. Just like magic!! v cool

                      1 Reply Last reply Reply Quote 1
                      • R
                        rochemike
                        last edited by rochemike

                        Executing the following command resulted in an error until I powered the VM off:

                        ESXi host ==> VMware ESXi, 6.5.0, 19092475

                        Any ideas?

                        [11:02 10] xoa@xoa:~$ xo-cli vm.importFromEsxi host=xxx.xxx.xxx.xxx user=root password=secret sslVerify=false vm=262 network=13d8ab8a-dfdc-1e5c-0e35-0028af26987a sr=e748751e-02fd-28ae-5fa9-d58f5f0dc50a stopSource=true thin=true
āœ– Cannot read properties of undefined (reading 'stream')
JsonRpcError: Cannot read properties of undefined (reading 'stream')
    at Peer._callee$ (/usr/local/lib/node_modules/xo-cli/node_modules/json-rpc-peer/dist/index.js:139:44)
    at tryCatch (/usr/local/lib/node_modules/xo-cli/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:44:17)
    at Generator.<anonymous> (/usr/local/lib/node_modules/xo-cli/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:125:22)
    at Generator.next (/usr/local/lib/node_modules/xo-cli/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:69:21)
    at asyncGeneratorStep (/usr/local/lib/node_modules/xo-cli/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
    at _next (/usr/local/lib/node_modules/xo-cli/node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:9)
    at /usr/local/lib/node_modules/xo-cli/node_modules/@babel/runtime/helpers/asyncToGenerator.js:27:7
    at new Promise (<anonymous>)
    at Peer.<anonymous> (/usr/local/lib/node_modules/xo-cli/node_modules/@babel/runtime/helpers/asyncToGenerator.js:19:12)
    at Peer.exec (/usr/local/lib/node_modules/xo-cli/node_modules/json-rpc-peer/dist/index.js:182:20)
[11:02 10] xoa@xoa:~$
                        1 Reply Last reply Reply Quote 0
                        • olivierlambertO
                          olivierlambert Vates šŸŖ Co-Founder CEO
                          last edited by

                          Same answer than my previous post: since ESXi 6.5, there's a new diff algorithm šŸ™‚ @florent is working on it, but it's even more complicated than the "legacy" one šŸ˜‰

                          R 1 Reply Last reply Reply Quote 0
                          • R
                            rochemike @olivierlambert
                            last edited by

                            @olivierlambert oh ok, I saw that and thought your comment was specific to the ESXi 7 version.

                            Thanks for the speedy response. I'd love to know how you clone yourself to be so responsive 24/7. Or am I talking to a Vates instance of ChatGPT?

                            1 Reply Last reply Reply Quote 1
                            • olivierlambertO
                              olivierlambert Vates šŸŖ Co-Founder CEO
                              last edited by

                              Sometimes I wonder šŸ˜“ But mostly because community is always my priority, regardless the fact we are a company with more than 30 people nowadays (with everything included on what is means).

                              M 1 Reply Last reply Reply Quote 1
                              • M
                                magicker @olivierlambert
                                last edited by

                                new issue.. I am trying to pull a vm (powered off) from a server I have already pulled 3 vms from (no problems)

                                However, this time it takes a few seconds before the command ends.

                                I can see the vm however, no disk is pulled over at all.

                                no obvious errors in logs.

                                florentF 1 Reply Last reply Reply Quote 0
                                • olivierlambertO
                                  olivierlambert Vates šŸŖ Co-Founder CEO
                                  last edited by

                                  Weird, you should have at least a reason why it stopped šŸ¤”

                                  1 Reply Last reply Reply Quote 0
                                  • florentF
                                    florent Vates šŸŖ XO Team @magicker
                                    last edited by

                                    @magicker
                                    that's a great start that 3 VM goes through without problems
                                    is your esxi still responsive after ? did you retry later ? what are the disks size of the failed vm ?

                                    M 1 Reply Last reply Reply Quote 0
                                    • M
                                      magicker @florent
                                      last edited by

                                      @florent Yes, esxi is just fine. All running VMs are happy. I have pulled one more off this server after the failed attempt. Have tried about 6 times .. same result.. VM appears.. process completes after a few seconds.. no disk appears

                                      The disc config seems very boring and normal.

                                      https://images.dx3webs.com/Zdiy2T.png

                                      https://images.dx3webs.com/y4vMSZ.png

                                      florentF K 2 Replies Last reply Reply Quote 0
                                      • M
                                        markhewitt1978
                                        last edited by

                                        Interested in this. I currently have an entire dedicated server running ESXi solely for the purpose of running a licening server for load balancers. ie lowest of low impact.

                                        Would love to get that into xcp-ng so the server can be used for something else.

                                        florentF 1 Reply Last reply Reply Quote 0
                                        • florentF
                                          florent Vates šŸŖ XO Team @magicker
                                          last edited by

                                          @magicker is there any logs on xo-sevrer side ? If you use a xoa, can you open a ticket and a support tunnel ?

                                          M 1 Reply Last reply Reply Quote 0
                                          • florentF
                                            florent Vates šŸŖ XO Team @markhewitt1978
                                            last edited by

                                            @markhewitt1978 that is exaclty the goal of this tool allow users to migrate to xcp/xo stack easily

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