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 I get the following error now.

      root@xoa:~# xo-cli vm.importFromEsxi host=192.168.40.203 user='root' password='obfuscated ' sslVerify=false vm=30 sr=accb1cf1-92b7-5d47-e2c4-e7d8a282c448 network=83594c5b-8b5b-b45f-d3a7-7e5301468dc8 thin=true
āœ– 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-202301251747/node_modules/json-rpc-peer/dist/index.js:139:44)
    at tryCatch (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:44:17)
    at Generator.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:125:22)
    at Generator.next (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:69:21)
    at asyncGeneratorStep (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
    at _next (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:9)
    at /opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/@babel/runtime/helpers/asyncToGenerator.js:27:7
    at new Promise (<anonymous>)
    at Peer.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/@babel/runtime/helpers/asyncToGenerator.js:19:12)
    at Peer.exec (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/json-rpc-peer/dist/index.js:182:20)

      vm.importFromEsxi
{
  "host": "192.168.40.203",
  "user": "root",
  "password": "* obfuscated *",
  "sslVerify": false,
  "vm": "30",
  "sr": "accb1cf1-92b7-5d47-e2c4-e7d8a282c448",
  "network": "83594c5b-8b5b-b45f-d3a7-7e5301468dc8",
  "thin": true
}
{
  "code": "HANDLE_INVALID",
  "params": [
    "network",
    "OpaqueRef:478f9e9d-7592-40a2-ab07-10a0a6982e45"
  ],
  "call": {
    "method": "network.get_MTU",
    "params": [
      "OpaqueRef:478f9e9d-7592-40a2-ab07-10a0a6982e45"
    ]
  },
  "message": "HANDLE_INVALID(network, OpaqueRef:478f9e9d-7592-40a2-ab07-10a0a6982e45)",
  "name": "XapiError",
  "stack": "XapiError: HANDLE_INVALID(network, OpaqueRef:478f9e9d-7592-40a2-ab07-10a0a6982e45)
    at Function.wrap (/opt/xo/xo-builds/xen-orchestra-202301251747/packages/xen-api/src/_XapiError.js:16:12)
    at /opt/xo/xo-builds/xen-orchestra-202301251747/packages/xen-api/src/transports/json-rpc.js:37:27
    at AsyncResource.runInAsyncScope (node:async_hooks:204:9)
    at cb (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/bluebird/js/release/util.js:355:42)
    at tryCatcher (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/bluebird/js/release/promise.js:729:18)
    at _drainQueueStep (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/opt/xo/xo-builds/xen-orchestra-202301251747/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (node:internal/timers:471:21)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}
      florentF 1 Reply Last reply Reply Quote 0
      • florentF Offline
        florent Vates šŸŖ XO Team @brezlord
        last edited by

        @brezlord that looks lik an invlaid network id , are you sure it's ok ?
        (this was not visible before since the code was skipping VIFs creation)

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

          @florent It's copied direct from XO web UI.

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

            Are you sure it's not a PIF? Can you do a xe network-param-list uuid=<UUID>?

            If it doesn't work, then do it for a PIF: xe pif-param-list uuid=<UUID>

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

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

              xe network-param-list uuid=

              yes you are right I had an error in the uuid. I copied it from the host and not the pool.

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

                Does it work now? In XO6, we'll do everything to avoid the confusion between a PIF and a network, it should be more clear than it is today.

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

                  @olivierlambert yes. I very excited to test out XO6.

                  1 Reply Last reply Reply Quote 0
                  • planedropP Offline
                    planedrop Top contributor
                    last edited by

                    Just as some additional feedback about this, I tried with thin=true today on a small 20GB Ubuntu VM and it worked great!!

                    I do have a suggestion though, I'd love to see a task in XOA about reading the blocks from the ESXi VM. When I entered the command, I thought nothing was working because a task never started, but when I checked network stats on the host it was very clear it was reading from ESXi. Once it finished reading, it imported the disk (which created a task) and the actual VHD space used is only 7.5GB!

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

                      Yes, as I explain, the first pass is just reading the whole VMware disk once. It's only doing the transfer on second pass.

                      That's why there's no XCP-ng task in the first pass (since until now, we only have XCP-ng tasks, there's no XO tasks).

                      But it's changing, we are about to release XO tasks, so it will be easier to track the job šŸ™‚

                      planedropP 1 Reply Last reply Reply Quote 0
                      • planedropP Offline
                        planedrop Top contributor @olivierlambert
                        last edited by

                        @olivierlambert Totally makes sense, this is great news.

                        Thanks again! I'll be testing the tool on some very large VMs in the coming weeks so I'll report back if anything weird happens with those.

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

                          @florent When I import a windows 10 VM from ESXi to XCP-ng the boot firmware was incorrectly set to bios when the source VM was uefi. I would also be advantageous to have the mac address(s) copied over by default or at least on option.

                          Thanks,
                          Simon

                          florentF 2 Replies Last reply Reply Quote 0
                          • florentF Offline
                            florent Vates šŸŖ XO Team @brezlord
                            last edited by

                            @brezlord nice catch, I will work on it today

                            @planedrop : task progression is in the work with @julien-f , and I hope they'll reach maturity soon

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

                              @brezlord mac address and uefi should works now

                              brezlordB 2 Replies Last reply Reply Quote 2
                              • brezlordB Offline
                                brezlord @florent
                                last edited by

                                @florent I will rebuild XO and re-import and give feedback. Thanks.

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

                                  It's now available directly on master (from the sources) or on latest XOA release channel šŸ™‚ (I updated the first post accordingly)

                                  planedropP 1 Reply Last reply Reply Quote 1
                                  • planedropP Offline
                                    planedrop Top contributor @olivierlambert
                                    last edited by

                                    @olivierlambert Awesome, super exciting stuff!

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

                                      @florent Everything is working now, Thanks. I have sucsefully migrated Windows and Linux VMs.

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

                                        Perfect! Now expect all of this but in a simple wizard in the UI, that will be a great tool for everyone who want to make the migration (and we hope to get a decent share of those users with our new support bundle)

                                        1 Reply Last reply Reply Quote 1
                                        • S Offline
                                          severhart
                                          last edited by

                                          This post is deleted!
                                          1 Reply Last reply Reply Quote 0
                                          • S Offline
                                            severhart
                                            last edited by olivierlambert

                                            After running for hours, get the following

                                            āœ– sesparse Vmdk reading is not functionnal yet FP-FileServer/FP-FileServer-000001-sesparse.vmdk
JsonRpcError: sesparse Vmdk reading is not functionnal yet FP-FileServer/FP-FileServer-000001-sesparse.vmdk
    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)
                                            florentF 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post