VMWare import Suddenly Reporting (500) error

[Bradomski]

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'

I can see the VMs in the list, this pops up after I select 'Import' on a specific VM.
Any idea as to why?

 

[bbgeek17]

Hi @Bradomski ,

Have you looked at "journalctl -n 500" or "journalctl -f" during the migration attempt?
Have you run "pvesm status"? "pvesm list [storage]"
Any errors on ESXi side in the logs?
Any changes in networking?

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Bradomski]

pvesm status shows

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.

 

[bbgeek17]

failed to spawn fuse mount, process exited with status 65280

Plug this into google , it seems you are not the only one reporting this type of error.
For example, here is the first search result for me: https://forum.proxmox.com/threads/proxmox-8-1-esxi-import-storage-error-500.144049/

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Bradomski]

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.