VMware migration tool: we need your feedback!

magicker

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.

olivierlambert

Weird, you should have at least a reason why it stopped

florent

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

magicker

@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

markhewitt1978

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.

florent

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

florent

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

magicker

@florent What is the location of the logs?

florent

@magicker
it depends hos you installled xo-server, but in general it's in journalctl -u xo-server

ulasdem

Hi,

I have 2 succesfull migrate (Windows and Linux). Windows migrate was successfull but i have to configure network interface after vm opened (as i know this is known issue and about Windows). On the Linux vm (Centos 7) i have regenerate initram and LVM structure, and it is working good now. But today i am trying with different vm's and i am gettin the error below:

xoa@xo-from-source:~$ xo-cli vm.importFromEsxi host=xxxxx user=xxxxxpassword=xxxxx sslVerify=false vm=3133 network=f6c27xxxxxxxx2e5 sr=61e7d4xxxxxxxd8ec3
✖ Cannot read properties of undefined (reading 'footer')
JsonRpcError: Cannot read properties of undefined (reading 'footer')
     at Peer._callee$ (/opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/json-rpc-peer/dist/index.js:139:44)
     at tryCatch (/opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:44:17)
     at Generator.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:125:22)
     at Generator.next (/opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:69:21)
     at asyncGeneratorStep (/opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
     at _next (/opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:9)
     at /opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/@babel/runtime/helpers/asyncToGenerator.js:27:7
     at new Promise (<anonymous>)
     at Peer.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/@babel/runtime/helpers/asyncToGenerator.js:19:12)
     at Peer.exec (/opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/json-rpc-peer/dist/index.js:182:20)

And I am getting this error below. I am sure, My Vm id is correct. I tried clone this vm for change id. But it doesn't changed.

xoa@xo-from-source:~$ xo-cli vm.importFromEsxi host=xxxxx user=xxxxx password=xxxxxx sslVerify=false vm=3161 network=f6c27exxxxxxxxa2e5 sr=61exxxxxxd8ec3
✖ VM 3161 not found
JsonRpcError: VM 3161 not found
     at Peer._callee$ (/opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/json-rpc-peer/dist/index.js:139:44)
     at tryCatch (/opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:44:17)
     at Generator.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:125:22)
     at Generator.next (/opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:69:21)
     at asyncGeneratorStep (/opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
     at _next (/opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:9)
     at /opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/@babel/runtime/helpers/asyncToGenerator.js:27:7
     at new Promise (<anonymous>)
     at Peer.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/@babel/runtime/helpers/asyncToGenerator.js:19:12)
     at Peer.exec (/opt/xo/xo-builds/xen-orchestra-202302101204/node_modules/json-rpc-peer/dist/index.js:182:20)

You can see my vm's id in this ss : https://prnt.sc/l29WdT8JVaYy

And my third problem is I have a windows vm around 500 GB and migration continues for 40 hour. There is no status indicator or error message and i can't understand if is there a problem or another thing. I have tried with Xoa before 5.79 update, there was a status indicator on tasks tab. Now I am using XO from source and 5.79 update. I can't see any indicator

I am using:

xo server 5.109.0
xo-web 5.111.0
VMware ESXi, 6.7.0, 15160138

florent

@ulasdem I will look into the error message, at least I will make it more informative. How many VM have you in this esxi ? is it more than 100 ?

For the long running import : there is a visible Task only when we reached the importing phase. The first step (when using thin=true) will read the whole disks to detect empty blocks. For now it's visible only in the logs, but we're working on it.

ulasdem

@florent Thank you for your message. I have 122 Vm on my one ESXI Host and i am planning to distribute this vms to xcp hosts in our other DC. Does it affecting migration tool how many vms are in ESXI?

florent

@ulasdem yes, I think I saw that there is limitation to the api, but didn't reach the limit on our test pools

I will try to work around this

KPS

Hi!

I did my first migration: Everything looks good!

The only thing, that should be noted:
You need to provide the VM-ID in your script. The ID that is shown through vSphere was not valid for your script. I had to login the the current ESXi-host and to get the ID with:

vim-cmd vmsvc/getallvms | grep NAME

olivierlambert

That will be "solved" with the next release: you'll have a VM selector directly in the web UI

florent

@ulasdem can you try this branch ? https://github.com/vatesfr/xen-orchestra/pull/6662
there is a new command esxi.connect that should show all the VM of an ESXI ( even after the first 100 ones)

@KPS thank you, I note the command

fbeauchamp opened this pull request in vatesfr/xen-orchestra

closed Feat(xo-server): implement Api for esxi migration UX #6662

severhart

Have successfully migrated 2 VMs from ESXI, doing MANY Hyper-v migrations, and have a suggestion / feature..
THIS is likely not the forum for this, but I know you guys are in a similar situation...

Is it possible to add within XOA or the XCP-ng Center to allow attaching to a hyper-v cluster and do drag and drop style of migrations from hyper-v to XCP?
I had something similar setup for a past company that allowed me to attach to any type of cluster and manage all from within a single pane of glass ( Until all migrations were complete )

ulasdem

@florent I will try this branch and inform you in next week

florent

@severhart that would really put the orchestra in xen orchestra , but it would be a huge workload

olivierlambert

We are potentially investigating if HyperV APIs are friendly to do a similar thing than we do with VMware.

However, we do not have the objective to have XO managing VMware or HyperV clusters (at least, not for the next 3 years)