VMware migration tool: we need your feedback!

alexredston

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.

alexredston

@florent Excellent!

ysageev

@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.

olivierlambert

@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.

brezlord

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.

florent

@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

brezlord

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

florent

@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

brezlord

@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)

florent

@brezlord is your xo in http or https ?

brezlord

@florent https

olivierlambert

If you don't have valid certificates, you need to add --allowUnauthorized in the registration command.

brezlord

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

--allowUnauthorized

thanks that did it.

olivierlambert

Okay, keep us posted on the VMware migration tool then

brezlord

@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)

olivierlambert

Have you switched to the right branch, as explained in the first post?

brezlord

@olivierlambert yes vmware

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.

brezlord

@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)

brezlord

@olivierlambert I've created a new network and it's now working, yay.