VMware migration tool: we need your feedback!
-
@alexredston nice catch, the methods weren't listed in
list-command, it's fixed on the vmware branchRegards
Florent
-
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.
-
@florent Excellent!
-
@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.
-
@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 typingvmwarein the custom release channel. -
O olivierlambert referenced this topic on
-
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.
-
@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
-
@florent it's esxi 7 and yes XO is in the same sub net and can ping the esxi server
-
@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 -
@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) -
@brezlord is your xo in http or https ?
-
@florent https
-
If you don't have valid certificates, you need to add
--allowUnauthorizedin the registration command. -
@olivierlambert said in VMware migration tool: we need your feedback!:
--allowUnauthorized
thanks that did it.
-
Okay, keep us posted on the VMware migration tool then

-
@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) -
Have you switched to the right branch, as explained in the first post?
-
@olivierlambert yes vmware
-
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.importFomEsxiis the "right" command. @florent will fix this
FYI:
xo-cli list-commandswill display all the commands, that's how I found out. -
@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)
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better š
Register Login