VMWare import Suddenly Reporting (500) error

Bradomski

New Member
Sep 13, 2024
10
1
3
Hello,

We are currently mid migration and have all of a sudden run into an issue with using the ESX import feature.

We have imported about 50 VMs with the import feature flawlessly. Now all of a sudden, we are getting (500) errors for 'Storage not activated'
1729083079833.png
I can see the VMs in the list, this pops up after I select 'Import' on a specific VM.
Any idea as to why?
 
pvesm status shows 1729083788114.png

Which aligns with the error.
Running pvesm list storage yields 'failed to spawn fuse mount, process exited with status 65280'

I do not see any logs on the ESXi side

No changes in networking as far as I am aware.
 
Yep. I was consulting that post as well. I have already attempted the mgmt network reset on ESX to no avail. Ensured the SOAP settings were set to 0 to no avail. Just looking to try and figure out this issue as it doesn't appear all that prevalent however still a problem.
 
It works for me by upgrading the proxmox to the latest version and run apt install pve-esxi-import-tools -y
 
Last edited:
  • Like
Reactions: fiona
It works for me by upgrading the proxmox to the latest version and run apt install pve-esxi-import-tools -y
For reference, there was a recent fix from @dherzig that is available since pve-esxi-import-tools >= 0.7.3.