VMware import 404 error

olivierlambert

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

sunwriter

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

florent

@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

florent

@sunwriter it is merged into master

olivierlambert

sunwriter

@florent Thank you! Looking forward to migrating more VM's.

s3b

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 .

olivierlambert

Are you sure about the DC Name? 404 means we can't find the file with the URL we build.

florent

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

s3b

@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

florent

@s3b we made a typo while cleaning code before merging , it is fixed on this branch fix_dcpath and, hopefully, it will be merged soon
The PR is here : https://github.com/vatesfr/xen-orchestra/pull/6729/files

fbeauchamp opened this pull request in vatesfr/xen-orchestra

closed fix(vmware-explorer): fix dcPath parameter #6729

s3b

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

florent

@s3b the progress bar is on our roadmap , it will be even more needed when handling multiple import in parallel

s3b

@florent great !

s3b

@florent false joy , i have a problem now with another VM , this vm is on same place as baldr1-test , error :

message": "404 Not Found https://10.30.xx.xx/folder/undefined?dcPath=Webxxx&dsName=undefined",

th Vm is baldr2-test , the dsName should be the same but is undefined .

florent

@s3b dsName should be the datastore

what is the datastore name ? Are the vmx and vmdk files on the same one ? what is fileName of this disk in the vmx file ?

s3b

@florent the dsNAme is import-proxmox like for baldr1-test.
There is no .vmx so i think i have to delete from inventory the VM and recreate the vm and attach the disk . For now there is just 2 files :
[import-proxmox] baldr2-test/baldr2-test-import-ctk.vmdk
and
[import-proxmox] baldr2-test/baldr2-test-import.vmdk

.

florent

@s3b The vmx file is mandatory for the import, I didn't know that it was not for running on an esxi

Recreating it should solve the problem, I will improve our error handling on this case

s3b

@florent , delete vm from inventory , recreate the vm , move disk from old folder to new folder and then attach the disk to vm works fine

florent

@s3b I am more a XCP guy