Proxmox 8.1 ESXi import storage error 500

buco · Mar 28, 2024

First of all: thanks to the dev team for working hard to accomodate VMware users that possibly might convert to Proxmox! Probably I'm doing something wrong but so far it doesn't work for me.

I've set up a ProxMox POC at work next to our VMware cluster. Obviously, first thing I did after reading about the ESXi import wizard is upgrade

. I added one of our ESXi servers as import storage and it seems to have worked at the time of setup. I was able to see the list of VMs once. Then I get an error 500 if I want to see the list again, I get this in the interface:

Code:

(vim.fault.HostConnectFault) { (500)

Code:

root@pve1:~# systemctl status pve-esxi*
● pve-esxi-fuse-pve1.example.org.scope
     Loaded: loaded (/run/systemd/transient/pve-esxi-fuse-vms1.example.org.scope; transient)
  Transient: yes
     Active: active (running) since Thu 2024-03-28 05:12:48 CET; 52min ago
      Tasks: 34 (limit: 231862)
     Memory: 7.3M
        CPU: 454ms
     CGroup: /system.slice/pve-esxi-fuse-vms1.example.org.scope
             └─141992 /usr/libexec/pve-esxi-import-tools/esxi-folder-fuse --skip-cert-verification --change-user nobody --chang>

Mar 28 05:12:48 pve1 systemd[1]: Started pve-esxi-fuse-vms1.example.org.scope.
Mar 28 05:13:00 pve1 esxi-folder-fus[141992]: pve1 esxi-folder-fuse[141992]: esxi fuse mount ready
lines 1-12/12 (END)

Code:

root@pve1:~# grep vms1 /var/log/*/* # then piped through sed. I redacted out my company's real domain name SAN name and 3 VM names.
grep: /var/log/journal/3d3ea5d411a34d5299bff9ac341c2d7b/system.journal: binary file matches
/var/log/pveproxy/access.log:::ffff:172.22.39.2 - root@pam [28/03/2024:05:13:10 +0100] "GET /api2/extjs/storage/vms1.example.org?_dc=1711599190610 HTTP/1.1" 200 234
/var/log/pveproxy/access.log:::ffff:172.22.39.2 - root@pam [28/03/2024:05:13:27 +0100] "GET /api2/json/nodes/pve3/storage/vms1.example.org/content?content=import HTTP/1.1" 200 837
/var/log/pveproxy/access.log:::ffff:172.22.39.2 - root@pam [28/03/2024:05:14:55 +0100] "GET /api2/extjs/nodes/pve3/storage/vms1.example.org/import-metadata?volume=ha-datacenter%2FSAN01_production02%2Fsomevms.example.org%2Fsomevms.example.org.vmx&_dc=1711599295190 HTTP/1.1" 200 96
/var/log/pveproxy/access.log:::ffff:172.22.39.2 - root@pam [28/03/2024:05:15:00 +0100] "GET /api2/extjs/nodes/pve3/storage/vms1.example.org/import-metadata?volume=ha-datacenter%2FSAN01_production02%2Fsomevms.example.org%2Fsomevms.example.org.vmx&_dc=1711599300895 HTTP/1.1" 200 96
/var/log/pveproxy/access.log:::ffff:172.22.39.2 - root@pam [28/03/2024:05:15:49 +0100] "GET /api2/extjs/nodes/pve3/storage/vms1.example.org/import-metadata?volume=ha-datacenter%2FSAN01_production02%2Fsomevms.example.org%2Fsomevms.example.org.vmx&_dc=1711599349061 HTTP/1.1" 200 96
/var/log/pveproxy/access.log:::ffff:172.22.39.2 - root@pam [28/03/2024:05:16:07 +0100] "GET /api2/json/nodes/pve3/storage/vms1.example.org/content?content=import HTTP/1.1" 500 13
/var/log/pveproxy/access.log:::ffff:172.22.39.2 - root@pam [28/03/2024:05:16:16 +0100] "GET /api2/json/nodes/pve3/storage/vms1.example.org/content?content=import HTTP/1.1" 500 13
/var/log/pveproxy/access.log:::ffff:172.22.39.2 - root@pam [28/03/2024:05:27:54 +0100] "GET /api2/json/nodes/pve3/storage/vms1.example.org/content?content=import HTTP/1.1" 500 13
/var/log/pveproxy/access.log:::ffff:172.22.39.2 - root@pam [28/03/2024:05:28:01 +0100] "GET /api2/json/nodes/pve3/storage/vms1.example.org/content?content=import HTTP/1.1" 500 13
/var/log/pveproxy/access.log:::ffff:172.22.39.2 - root@pam [28/03/2024:05:28:12 +0100] "GET /api2/json/nodes/pve1/storage/vms1.example.org/content?content=import HTTP/1.1" 500 13
/var/log/pveproxy/access.log:::ffff:172.22.39.2 - root@pam [28/03/2024:05:28:15 +0100] "GET /api2/json/nodes/pve2/storage/vms1.example.org/content?content=import HTTP/1.1" 500 13
/var/log/pveproxy/access.log.1:::ffff:172.22.39.7 - root@pam [27/03/2024:20:46:01 +0100] "GET /api2/json/nodes/pve2/storage/vms1.example.org/content?content=import HTTP/1.1" 500 13
/var/log/pveproxy/access.log.1:::ffff:172.22.39.7 - root@pam [27/03/2024:20:46:12 +0100] "GET /api2/extjs/storage/vms1.example.org?_dc=1711568772158 HTTP/1.1" 200 209
/var/log/pveproxy/access.log.1:::ffff:172.22.39.7 - root@pam [27/03/2024:20:46:22 +0100] "PUT /api2/extjs/storage/vms1.example.org HTTP/1.1" 200 65
/var/log/pveproxy/access.log.1:::ffff:172.22.39.7 - root@pam [27/03/2024:20:46:24 +0100] "GET /api2/extjs/storage/vms1.example.org?_dc=1711568784015 HTTP/1.1" 200 209
/var/log/pveproxy/access.log.1:::ffff:172.22.39.7 - root@pam [27/03/2024:20:46:25 +0100] "PUT /api2/extjs/storage/vms1.example.org HTTP/1.1" 200 65
/var/log/pveproxy/access.log.1:::ffff:172.22.39.7 - root@pam [27/03/2024:20:46:28 +0100] "GET /api2/json/nodes/pve2/storage/vms1.example.org/content?content=import HTTP/1.1" 500 13
/var/log/pveproxy/access.log.1:::ffff:172.22.39.7 - root@pam [27/03/2024:20:54:58 +0100] "GET /api2/json/nodes/pve3/storage/vms1.example.org/content?content=import HTTP/1.1" 500 13
/var/log/pveproxy/access.log.1:::ffff:172.22.39.7 - root@pam [27/03/2024:20:55:16 +0100] "GET /api2/json/nodes/pve3/storage/vms1.example.org/content?content=import HTTP/1.1" 500 13
/var/log/pveproxy/access.log.1:::ffff:172.22.39.7 - root@pam [27/03/2024:20:55:49 +0100] "DELETE /api2/extjs/storage//vms1.example.org HTTP/1.1" 200 25
root@pve1:~#

shcshc76 · Mar 28, 2024

same here with two pve and esxi6.7 und 8.0 hosts

buco · Mar 28, 2024

Yeah in the announcement thread I read more people who encounter this issue. Not sure what it is but eager to help out if I need to provide more details/info.

buco · Mar 28, 2024

Ah and after a couple of hours (after posting my initial thread), I refreshed the storage page listing all the VMs and that works again. Not sure about the rest. Maybe it is some rate limiting that is "reset" again? I wasn't trying to do much.

shcshc76 · Mar 28, 2024

after a while i get:

transferred 10.1 GiB of 20.0 GiB (50.29%)
transferred 10.3 GiB of 20.0 GiB (51.30%)
transferred 10.5 GiB of 20.0 GiB (52.30%)
transferred 10.7 GiB of 20.0 GiB (53.31%)
transferred 10.9 GiB of 20.0 GiB (54.32%)
transferred 11.1 GiB of 20.0 GiB (55.32%)
transferred 11.3 GiB of 20.0 GiB (56.33%)
transferred 11.5 GiB of 20.0 GiB (57.33%)
transferred 11.7 GiB of 20.0 GiB (58.34%)
transferred 11.9 GiB of 20.0 GiB (59.35%)
transferred 12.1 GiB of 20.0 GiB (60.35%)
qemu-img: error while reading at byte 13052670976: Function not implemented
TASK ERROR: unable to create VM 102 - cannot import from 'esxi67...

journalctl on pve:

Mär 28 08:49:25 proxmox01 pvedaemon[698403]: <root@pam> starting task UPID

roxmox01:000B6F54:007C958B:66052105:qmcreate:102:root@pam:
Mär 28 08:52:09 proxmox01 pveproxy[698510]: worker exit
Mär 28 08:52:09 proxmox01 pveproxy[1746]: worker 698510 finished
Mär 28 08:52:09 proxmox01 pveproxy[1746]: starting 1 worker(s)
Mär 28 08:52:09 proxmox01 pveproxy[1746]: worker 750651 started
Mär 28 08:55:01 proxmox01 CRON[752570]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mär 28 08:55:01 proxmox01 CRON[752572]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Mär 28 08:55:01 proxmox01 CRON[752570]: pam_unix(cron:session): session closed for user root
Mär 28 08:56:11 proxmox01 esxi-folder-fus[749085]: proxmox01 esxi-folder-fuse[749085]: rate limited, retrying (1 of 5)...
Mär 28 08:56:21 proxmox01 esxi-folder-fus[749085]: proxmox01 esxi-folder-fuse[749085]: rate limited, retrying (2 of 5)...
Mär 28 08:56:31 proxmox01 esxi-folder-fus[749085]: proxmox01 esxi-folder-fuse[749085]: rate limited, retrying (3 of 5)...
Mär 28 08:56:41 proxmox01 esxi-folder-fus[749085]: proxmox01 esxi-folder-fuse[749085]: rate limited, retrying (4 of 5)...
Mär 28 08:56:51 proxmox01 esxi-folder-fus[749085]: proxmox01 esxi-folder-fuse[749085]: rate limited => Response { status: 503, version: HTTP/1.1, headers: {"date": "Thu, 28 Mar 2024 07:56:51 GMT", "connection": "close", "content-security-policy": "block-all-mixed-content", "content-type": "text/plain; charset=utf-8", "strict-transport-security": "max-age=31536000", "x-content-type-options": "nosniff", "x-frame-options": "DENY", "x-xss-protection": "1", "content-length": "0"}, body: Body(Empty) }
Mär 28 08:56:51 proxmox01 esxi-folder-fus[749085]: proxmox01 esxi-folder-fuse[749085]: error handling request: cached read failed: rate limited
Mär 28 08:56:51 proxmox01 kernel: zd0: p1 p2 p3 p4 < >
Mär 28 08:56:51 proxmox01 pvedaemon[749396]: VM 102 creating disks failed
Mär 28 08:56:52 proxmox01 pvedaemon[749396]: unable to create VM 102 - cannot import from 'esxi67.testlabbi.dom:ha-datacenter/Datastore446/Audiocodes02.testlabbi.dom/Audiocodes02.testlabbi.dom.vmdk' - copy failed: command '/usr/bin/qemu-img convert -p -n -t none -f vmdk -O raw /run/pve/import/esxi/..irgendein pfad./vm-102-disk-0' failed: exit code 1
Mär 28 08:56:52 proxmox01 pvedaemon[698403]: <root@pam> end task UPID

roxmox01:000B6F54:007C958B:66052105:qmcreate:102:root@pam: unable to create VM 102 - cannot import from 'esxi67..irgendein pfad und datei...vmdk' - copy failed: command '/usr/bin/qemu-img convert -p -n -t none -f vmdk -O raw /run/pve/import/esxi/esxi67..irgendein pfad und datei..vmdk zeroinit:/dev/zvol/tank1/vm-102-disk-0' failed: exit code 1

buco · Mar 28, 2024

It seems to me like I got further without changing anything in the config. I can now get to the migration wizard. But an import task still fails somehow trying to import the VMDK:
First:

Code:

qemu-img: error while reading at byte 0: Function not implemented

TASK ERROR: unable to create VM 105 - cannot import from 'vms1.example.org:ha-datacenter/SAN01_infra/intranet.example.org/intranet.example.org.vmdk' - copy failed: command '/usr/bin/qemu-img convert -p -n -t none -f vmdk -O raw /run/pve/import/esxi/vms1.example.org/mnt/ha-datacenter/SAN01_infra/intranet.example.org/intranet.example.org.vmdk zeroinit:/dev/zvol/rpool/data/vm-105-disk-0' failed: exit code 1

m3m · Mar 28, 2024

So I have circled back around to Proxmox after what Broadcom is doing and decided to rebuild my cluster again. Once I saw the import option for ESXi, I had to try it. So for testing I nested Proxmox 8 in VMWare and connected a NFS share(for storage) and one EXSi server. Everything connected fine and looked to be working. But I am experiencing the same issue. I followed the preparations and chose a VM with doesn't have a cdrom,EFI or any other special config. And after three failed attempts to migrate, the connection to the ESXi server goes to poo. I have removed it and adding it back but it fails with a 503 errors. Rebooted the proxmox VM and still fails. I wouldn't think that a nested vm of proxmox could be the problem but not ruling it out. It started working and gets to about 14 to 17% then hits an error. Little disappointed but I know this is a brand new feature and neds time to mature. Would to seethis feature work instead of me trying to rebuild each VM one at a time. IF there is anything I could do to help, I am all ears.

transferred 12.8 GiB of 75.0 GiB (17.04%)
qemu-img: error while reading at byte 14159967232: Function not implemented
Logical volume "vm-100-disk-0" successfully removed.
TASK ERROR: unable to create VM 100 - cannot import from 'Rajesh:ha-datacenter/ComicCenter-SSD-App/Monitor-DT/Monitor-DT.vmdk' - copy failed: command '/usr/bin/qemu-img convert -p -n -f vmdk -O raw /run/pve/import/esxi/Rajesh/mnt/ha-datacenter/ComicCenter-SSD-App/Monitor-DT/Monitor-DT.vmdk zeroinit:/dev/pve/vm-100-disk-0' failed: exit code 1

And yes I am a BBT fine and have name my entire environment after the cast.

Journalctl
Mar 28 14:18:26 virtualpve pvedaemon[928]: <root@pam> starting task UPID:virtualpve:00001390:000236DB:6605C282:qmcreate:100:root@pam:
Mar 28 14:20:13 virtualpve esxi-folder-fus[4447]: virtualpve esxi-folder-fuse[4447]: rate limited, retrying (1 of 5)...
Mar 28 14:20:23 virtualpve esxi-folder-fus[4447]: virtualpve esxi-folder-fuse[4447]: rate limited, retrying (2 of 5)...
Mar 28 14:20:33 virtualpve esxi-folder-fus[4447]: virtualpve esxi-folder-fuse[4447]: rate limited, retrying (3 of 5)...
Mar 28 14:20:43 virtualpve esxi-folder-fus[4447]: virtualpve esxi-folder-fuse[4447]: rate limited, retrying (4 of 5)...
Mar 28 14:20:53 virtualpve esxi-folder-fus[4447]: virtualpve esxi-folder-fuse[4447]: rate limited => Response { status: 503, version: HTTP/1.1, headers: {"date": "Thu, 28>
Mar 28 14:20:53 virtualpve esxi-folder-fus[4447]: virtualpve esxi-folder-fuse[4447]: error handling request: cached read failed: rate limited
Mar 28 14:20:54 virtualpve pvedaemon[5008]: VM 100 creating disks failed
Mar 28 14:20:55 virtualpve pvedaemon[5008]: unable to create VM 100 - cannot import from 'Rajesh:ha-datacenter/ComicCenter-SSD-App/Monitor-DT/Monitor-DT.vmdk' - copy fail>
Mar 28 14:20:55 virtualpve pvedaemon[928]: <root@pam> end task UPID:virtualpve:00001390:000236DB:6605C282:qmcreate:100:root@pam: unable to create VM 100 - cannot import f>

m3m · Mar 29, 2024

m3m said:
So I have circled back around to Proxmox after what Broadcom is doing and decided to rebuild my cluster again. Once I saw the import option for ESXi, I had to try it. So for testing I nested Proxmox 8 in VMWare and connected a NFS share(for storage) and one EXSi server. Everything connected fine and looked to be working. But I am experiencing the same issue. I followed the preparations and chose a VM with doesn't have a cdrom,EFI or any other special config. And after three failed attempts to migrate, the connection to the ESXi server goes to poo. I have removed it and adding it back but it fails with a 503 errors. Rebooted the proxmox VM and still fails. I wouldn't think that a nested vm of proxmox could be the problem but not ruling it out. It started working and gets to about 14 to 17% then hits an error. Little disappointed but I know this is a brand new feature and neds time to mature. Would to seethis feature work instead of me trying to rebuild each VM one at a time. IF there is anything I could do to help, I am all ears.

transferred 12.8 GiB of 75.0 GiB (17.04%)
qemu-img: error while reading at byte 14159967232: Function not implemented
Logical volume "vm-100-disk-0" successfully removed.
TASK ERROR: unable to create VM 100 - cannot import from 'Rajesh:ha-datacenter/ComicCenter-SSD-App/Monitor-DT/Monitor-DT.vmdk' - copy failed: command '/usr/bin/qemu-img convert -p -n -f vmdk -O raw /run/pve/import/esxi/Rajesh/mnt/ha-datacenter/ComicCenter-SSD-App/Monitor-DT/Monitor-DT.vmdk zeroinit:/dev/pve/vm-100-disk-0' failed: exit code 1

And yes I am a BBT fine and have name my entire environment after the cast.

Journalctl
Mar 28 14:18:26 virtualpve pvedaemon[928]: <root@pam> starting task UPID:virtualpve:00001390:000236DB:6605C282:qmcreate:100:root@pam:
Mar 28 14:20:13 virtualpve esxi-folder-fus[4447]: virtualpve esxi-folder-fuse[4447]: rate limited, retrying (1 of 5)...
Mar 28 14:20:23 virtualpve esxi-folder-fus[4447]: virtualpve esxi-folder-fuse[4447]: rate limited, retrying (2 of 5)...
Mar 28 14:20:33 virtualpve esxi-folder-fus[4447]: virtualpve esxi-folder-fuse[4447]: rate limited, retrying (3 of 5)...
Mar 28 14:20:43 virtualpve esxi-folder-fus[4447]: virtualpve esxi-folder-fuse[4447]: rate limited, retrying (4 of 5)...
Mar 28 14:20:53 virtualpve esxi-folder-fus[4447]: virtualpve esxi-folder-fuse[4447]: rate limited => Response { status: 503, version: HTTP/1.1, headers: {"date": "Thu, 28>
Mar 28 14:20:53 virtualpve esxi-folder-fus[4447]: virtualpve esxi-folder-fuse[4447]: error handling request: cached read failed: rate limited
Mar 28 14:20:54 virtualpve pvedaemon[5008]: VM 100 creating disks failed
Mar 28 14:20:55 virtualpve pvedaemon[5008]: unable to create VM 100 - cannot import from 'Rajesh:ha-datacenter/ComicCenter-SSD-App/Monitor-DT/Monitor-DT.vmdk' - copy fail>
Mar 28 14:20:55 virtualpve pvedaemon[928]: <root@pam> end task UPID:virtualpve:00001390:000236DB:6605C282:qmcreate:100:root@pam: unable to create VM 100 - cannot import f>

Update!

Even though it is a manual process, the old ovftool still works like a champ. Just have to make sure that you don't have any special configuration in the VM you are migrating ie, UEFI and what type of storage your migrating to so you know which format to convert the VM too(NFS=qcow2 or LVM=raw).

julien10 · Mar 31, 2024

Got the same issue. Rate limiting. Perhaps there's something in ESXi rate limiting these reads? Any way to disable it? yes, ovftool works great but i'd like to use the new import tool as well. I can see it was trying to reconnect due to rate limiting but ultimately failed.

Jeffwolf · Mar 31, 2024

julien10 said:
Got the same issue. Rate limiting. Perhaps there's something in ESXi rate limiting these reads? Any way to disable it? yes, ovftool works great but i'd like to use the new import tool as well. I can see it was trying to reconnect due to rate limiting but ultimately failed.

Hi Julien

I believe I found the solution

On your esxi hosts , ssh to them and edit this file /etc/vmware/hostd/config.xml

search for
......
<soap>
<sessionTimeout>0</sessionTimeout>
</soap>
.......

And change it to

........
<soap>
<sessionTimeout>0</sessionTimeout>
<maxSessionCount>0</maxSessionCount>
</soap>
........

and reboot the host

I am running esxi v6.7 and this worked for me

I was unable to import anything over 10GB .... so far I have tested a 30GB vmdk and all seems to be working.... will continue testing to see limits . but so far dont see any issues.

S474N · Mar 31, 2024

Here is same settings for ESXi 7.x
https://docs.vmware.com/en/VMware-v...UID-E3D95B5C-A888-4E21-A6A0-AFC6A3DC1192.html

Tested on 50GB vmdk and its ok.

julien10 · Mar 31, 2024

Jeffwolf said:
On your esxi hosts , ssh to them and edit this file /etc/vmware/hostd/config.xml

search for
......
<soap>
<sessionTimeout>0</sessionTimeout>
</soap>
.......

And change it to

........
<soap>
<sessionTimeout>0</sessionTimeout>
<maxSessionCount>0</maxSessionCount>
</soap>

Thank you Jeff.

I saw this suggested in another post here. It's worth mentioning you can simply restart hostd by calling "/etc/init.d/hostd restart" rather than rebooting the entire ESXi host. Adjusting maxsessioncount resolved the issue for me, and I was able to successfully import VMs from ESXi to proxmox.

This option is configurable in ESXi 7.0, but I'm using 6.7u3 and I had to use "vi" on the conf file.

sheldor · Apr 1, 2024

We're running on ESXi 6.5. Is anyone aware of a difference in the hostd config.xml file between 6.5 and 6.7? We used vi to search for soap, and there doesn't seem to exist a section with:
<soap>
<sessionTimeout>0</sessionTimeout>
</soap>

julien10 · Apr 2, 2024

Search for <soap> in your config.xml and add the following:

<sessionTimeout>0</sessionTimeout>
<maxSessionCount>0</maxSessionCount>

before the closing </soap> tag.

I'll take a look at one of my legacy 6.5 boxes tonight.

terrorbyte311 · Apr 2, 2024

I can confirm the above fixed my problem. I was running into this issue on my 6.7 host. It had been a while since I updated it, so I patched it up to Update 3 build 20221004001, but that didn't help. Additionally, when it did fail, the web UI would stop working in a couple different ways.

Eventually i just had these commands queued up in my SSH session to the host and would bounce the services to restore connectivity. This didn't impact running workloads, and I probably didn't need all of them but I was getting tired of some things not working quite right.
/etc/init.d/hostd restart
/etc/init.d/vpxa restart
/etc/init.d/rhttpproxy restart

Anyway, my config.xml file didn't have the SOAP statements. Following the above mentioned VMware KB i modified Config.HostAgent.vmacore.soap.sessionTimeout to be 0 via the web GUI.
This placed the SOAP statements towards the bottom of my XML.
I added <maxSessionCount>0</maxSessionCount> just under the session timeout, preserving the white space.
Finally, running /etc/init.d/hostd restart loaded the new config live.

I know this is re-hashing the above, but thanks to everyone I was able to get a successful import and wanted to share my exact steps. I plan on rebuilding the rescued VMs anyway, but this buys me some breathing room before the old host fails (and save on power instead of running the old and new)

sheldor · Apr 2, 2024

julien10 said:
Search for <soap> in your config.xml and add the following:

<sessionTimeout>0</sessionTimeout>
<maxSessionCount>0</maxSessionCount>

before the closing </soap> tag.

I'll take a look at one of my legacy 6.5 boxes tonight.

I guess what I'm saying is there isn't a specific <soap> tag in the config.xml. There are a few tags with the word soap in it, but nothing called only <soap>.

julien10 · Apr 2, 2024

You can just add the soap parameters, it's an xml file after all. But if you're not comfortable doing that you can just go into the web gui and set Config.HostAgent.vmacore.soap.sessionTimeout to 0. Then the <soap> parameter will show up in config.xml.

sheldor · Apr 3, 2024

julien10 said:
You can just add the soap parameters, it's an xml file after all. But if you're not comfortable doing that you can just go into the web gui and set Config.HostAgent.vmacore.soap.sessionTimeout to 0. Then the <soap> parameter will show up in config.xml.

We added it to the XML. Works like a champ on 6.5. Thanks everyone!

delaware · Apr 3, 2024

After reading this thread I changed both values and restarted my 7.0U3n host. I can now add the ESX-Storage but when I select the Esx-Storage I am getting this error:

failed to spawn fuse mount, process exited with status 65280 (500)

I have upgraded every package to lateset, but I wonder if there is some library missing?

julien10 · Apr 6, 2024

delaware said:
After reading this thread I changed both values and restarted my 7.0U3n host. I can now add the ESX-Storage but when I select the Esx-Storage I am getting this error:

failed to spawn fuse mount, process exited with status 65280 (500)

I have upgraded every package to lateset, but I wonder if there is some library missing?

Yes, you're missing something. You should have libpve-storage-perl and pve-esxi-import-tools packages installed. You may also want to check your firewall on the ESXi server to make sure you can connect to it.

Proxmox 8.1 ESXi import storage error 500

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member