VMware import 404 error
-
Excited about the new VMware import. However, I am receiving the following when attempting. Details: (Xen Orchestra latest build, and VSphere
Maybe something I'm missing? Thanks in advance for any suggestions.vm.importFromEsxi { "host": "192.168.101.241", "network": "3fab0a14-a39c-235d-df0e-9b9b77789eed", "password": "* obfuscated *", "sr": "4b937ea6-9772-09ad-af25-a7adcebb5a82", "sslVerify": false, "stopSource": true, "thin": true, "user": "administrator@vsphere.local", "vm": "vm-3007" } { "cause": { "size": 0 }, "message": "404 Not Found https://192.168.101.241/folder/TPASQL1/TPASQL1.vmx?dsName=datastore1", "name": "Error", "stack": "Error: 404 Not Found https://192.168.101.241/folder/TPASQL1/TPASQL1.vmx?dsName=datastore1 at Esxi.download (file:///opt/xo/xo-builds/xen-orchestra-202303040838/@xen-orchestra/vmware-explorer/esxi.mjs:71:21) at Esxi.getTransferableVmMetadata (file:///opt/xo/xo-builds/xen-orchestra-202303040838/@xen-orchestra/vmware-explorer/esxi.mjs:228:17) at Task.runInside (/opt/xo/xo-builds/xen-orchestra-202303040838/@vates/task/index.js:158:22) at Task.run (/opt/xo/xo-builds/xen-orchestra-202303040838/@vates/task/index.js:137:20) at MigrateVm.migrationfromEsxi (file:///opt/xo/xo-builds/xen-orchestra-202303040838/packages/xo-server/src/xo-mixins/migrate-vm.mjs:177:28) at Task.runInside (/opt/xo/xo-builds/xen-orchestra-202303040838/@vates/task/index.js:158:22) at Task.run (/opt/xo/xo-builds/xen-orchestra-202303040838/@vates/task/index.js:137:20) at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202303040838/packages/xo-server/src/xo-mixins/api.mjs:394:20)" } -
Hi,
We need more details to be able to assist:
- XOA or XO from the sources? (if the latter, which commit)
- ESXi/vSphere version?
-
@olivierlambert It is XO from sources, and ESXi / Vsphere 8. Thanks.
-
@olivierlambert Xen Orchestra, commit 00a13
-
Which commit? (as asked)you answered in between- Is the VM halted?
-
@olivierlambert I attempted when the VM was running. I just tried it now with the VM halted, but same error.
-
As we explained in our blog posts, we only support delta when it's ESXi < 6.5. So I would say it's normal it doesn't work in your case.
However, I have to admit we didn't test it yet with very recent VMware version. Maybe something changed in the API, I don't know. @florent will take a look when he can

-
@olivierlambert Ok, thank you. I'll look for a possible future update at some point. Many thanks to you and the team for your continued hard work on the project!
-
@sunwriter the fix is not merged in master for now, but it shuld land soon
My guess is that you don't use te default datacenter name -
@sunwriter it is merged into master
-

-
@florent Thank you! Looking forward to migrating more VM's.
-
Hi,
i try to migrate vm from VMWARE esxi / vsphere 7.0.3 , i use the XO from source : xo-server 5.110.1 and xo-web 5.112.1 , commit : 5a2c3 .
VM halted or up same problem : "message": "404 Not Found https://xxxx/folder/baldr1-test_1/baldr1-test.vmx?dc=xxx&dsName=xxx" .
Any suggestions ? thanks ,
Seb . -
Are you sure about the DC Name? 404 means we can't find the file with the URL we build.
-
@s3b can you go to the datastore explorer of your esxi, download the baldr1-test.vmx file with your browser and compare the url with the one on 404 ?
-
@florent @olivierlambert thanks for your fast reply , the url is different when i try to download the file :
https://esx4.xxx.local/folder/baldr1-test_1/baldr1-test.vmx?dcPath=ha-datacenter&dsName=import-proxmox&enc=std -
@s3b we made a typo while cleaning code before merging , it is fixed on this branch
fix_dcpathand, hopefully, it will be merged soon
The PR is here : https://github.com/vatesfr/xen-orchestra/pull/6729/files -
@florent said in VMware import 404 error:
fix_dcpath
great job @florent
, it works well now, just 2 things I don't run xo as root so I had errors on thick storage with vgchange rights so I used thin storage, and I had a problem with the TLS connection because I use a self-signed certificate for xo-server so I had to add in my systemd orchestra service:
Environment=NODE_TLS_REJECT_UNAUTHORIZED=0 and
then it worked very well.
One thing that confused me a bit is that there was no progress bar on the import page but it is clearly visible on the tasks page. Thank you again for the responsiveness and efficiency.
-
@s3b the progress bar is on our roadmap , it will be even more needed when handling multiple import in parallel
-
@florent great !

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