ESXi import error

N

n.peters

New Member
Jan 27, 2025
4
0
1
Germany
Hi there,
i'm pretty new in the proxmox community and i'm currently setting up a 3 node cluster in my office, which will replace our current VMWare cluster.
With some issues here and there, I finally reached the point, where I want to import the VMs from the VMWare cluster, but here comes the problem.
When I first wanted to add the esxi storage, I recieved the following error message:
Screenshot 2025-02-10 095632.png
After I closed and re-opened the window, it somehow worked.

But when I now want to import a VM, I get the following error message:
Screenshot 2025-02-10 100605.png

I have added the VMWare nodes itself with the root user and the whole cluster with the cluster admin, but I still get the same error.
I hope someone can help me figuring this out, thanks in advance.
 
Hello n.peters! How did you try to import the VMs from the VMWare cluster? I just want to point out that there's a special chapter in the documentation on Importing Virtual Machines from other hypervisors, including OVA/OVF import. There's also a special wiki article on this topic.

If that does not help, please provide us with the full task log which should hopefully provide us with more information. To do that, either click on the task in the web GUI, or try to find the corresponding log in /var/log/pve/tasks, e.g. by using ls -lt /var/log/pve/tasks/ to sort the directories by time.
 
Thanks for the fast reply!
I was not able to import any VM until now, because I get the "storage "..." is not activated (500)" error, when I click on import in the esxi storage.
So, if I follow the instructions on the wiki article, "Automatic ESXi Import: Step by Step", I'm getting stuck at step 5.
Screenshot 2025-02-10 121359.png
 
Hmm, are you able to reach/ping the storage? Also if you try it at multiple points in time (e.g. multiple times over a few minutes)? I'm just wondering whether you have some networking issues that might cause the errors you are seeing.

Either way, it would still be useful to see some logs, as we might get some more information. It would be easier than guessing what could go wrong :)
 
I can ping the VMWare cluster with all 3 Nodes. I let the ping run on all nodes for a few minutes and there was 0% package lost. I re-added the storage, just to be sure. I don't now, where I can find the exact logs for storage errors, because there is no task for creating a storage or importing a VM, but I have found something in the system logs:


Code: 
Feb 10 14:30:37 ibtprox1 systemd[1]: Started pve-esxi-fuse-ibtvcsa.scope.
Feb 10 14:30:37 ibtprox1 systemd[1]: run-pve-import-esxi-ibtvcsa-mnt.mount: Deactivated successfully.
Feb 10 14:30:44 ibtprox1 esxi-folder-fuse[2030197]: error looking up file or directory: error when getting file size: "IBTesx"/"VMPool1"/"/ISO_Images/ubuntu-24.04-live-server-amd64.iso"

Caused by:
    http error code 500
Feb 10 14:30:44 ibtprox1 esxi-folder-fuse[2030197]: Error: error when getting file size: "IBTesx"/"VMPool1"/"/ISO_Images/ubuntu-24.04-live-server-amd64.iso"
 http error code 500
Feb 10 14:30:44 ibtprox1 systemd[1]: pve-esxi-fuse-ibtvcsa.scope: Deactivated successfully.
Feb 10 14:30:48 ibtprox1 dbus-daemon[2215]: [system] Connection ":1.11442" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=512)
Feb 10 14:30:48 ibtprox1 pvestatd[3192]: failed to spawn fuse mount, process exited with status 256
Feb 10 14:30:58 ibtprox1 dbus-daemon[2215]: [system] Connection ":1.11442" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=512)
Feb 10 14:30:58 ibtprox1 pvestatd[3192]: failed to spawn fuse mount, process exited with status 256
Feb 10 14:31:12 ibtprox1 dbus-daemon[2215]: [system] Connection ":1.11442" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=512)
Feb 10 14:31:12 ibtprox1 pvestatd[3192]: failed to spawn fuse mount, process exited with status 256
Feb 10 14:31:18 ibtprox1 dbus-daemon[2215]: [system] Connection ":1.11442" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=512)
Feb 10 14:31:18 ibtprox1 pvestatd[3192]: failed to spawn fuse mount, process exited with status 256
Feb 10 14:31:28 ibtprox1 dbus-daemon[2215]: [system] Connection ":1.11442" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=512)
Feb 10 14:31:28 ibtprox1 pvestatd[3192]: failed to spawn fuse mount, process exited with status 256
Feb 10 14:31:33 ibtprox1 sshd[2030614]: Accepted password for root from 134.94.156.5 port 57396 ssh2
Feb 10 14:31:33 ibtprox1 sshd[2030614]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Feb 10 14:31:33 ibtprox1 systemd-logind[2236]: New session 9355 of user root.
Feb 10 14:31:33 ibtprox1 systemd[1]: Started session-9355.scope - Session 9355 of User root.
Feb 10 14:31:33 ibtprox1 sshd[2030614]: pam_env(sshd:session): deprecated reading of user environment enabled
Feb 10 14:31:33 ibtprox1 sshd[2030614]: Received disconnect from 134.94.156.5 port 57396:11: Connection terminated by the client.
Feb 10 14:31:33 ibtprox1 sshd[2030614]: Disconnected from user root 134.94.156.5 port 57396
Feb 10 14:31:33 ibtprox1 sshd[2030614]: pam_unix(sshd:session): session closed for user root
Feb 10 14:31:33 ibtprox1 systemd-logind[2236]: Session 9355 logged out. Waiting for processes to exit.
Feb 10 14:31:33 ibtprox1 systemd[1]: session-9355.scope: Deactivated successfully.
Feb 10 14:31:33 ibtprox1 systemd-logind[2236]: Removed session 9355.
Feb 10 14:31:38 ibtprox1 dbus-daemon[2215]: [system] Connection ":1.11442" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=512)
Feb 10 14:31:38 ibtprox1 pvestatd[3192]: failed to spawn fuse mount, process exited with status 256
Feb 10 14:31:51 ibtprox1 dbus-daemon[2215]: [system] Connection ":1.11442" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=512)
Feb 10 14:31:51 ibtprox1 pvestatd[3192]: failed to spawn fuse mount, process exited with status 256
 
Interesting. At first sight, this looks like there are some issues with the path of the ISO file. I was able to find another thread that seems similar to yours - please check whether the suggestions posted in that thread help.
 
Thank you for your help.
I asked my supervisor to set our VMware cluster in the retread mode, but he is getting an error and he does not want to change too many things, that could solve the error, because he does not want to risk a failure of our production system. So I have to find another way for a proper migration.
 
Just to be sure:
  1. Is the path to the ISO file correct? I'm just wondering whether it might have been deleted, and ESXi might not show an error in that case, but Proxmox VE does.
  2. Is the ISO file actually necessary? If not, you might want to remove it from the import altogether. For me it looks like it's a leftover from the initial installation of Ubuntu Server on the VM.
 
You must log in or register to reply here.
Top Bottom