ESXi Import Timeout

[bv-joey]

When trying to import from a slower ESXi host that has a larger number of virtual machines, 120-125 in my current situation, Proxmox fails to add the server in the storage list with a "Connection error - Timeout" message. This appears to be related to the 30 second timeout that is set in the Proxmox GUI.


I can successfully open another smaller ESXi host (78 VMs) from the same Proxmox node, and I was able to get one of the larger servers to at least appear in the list (120 VMs), however I cannot open it for import.

In reviewing /run/pve/import/esxi/<server>/manifest.json, I see that it collected at least some if not all of that server's information, however I cannot load it after the fact, getting just a "communication failure (0)" error in the UI when I try to access the storage object in the Server View.


If anyone has any guidance on either increasing that 30 second timeout, or a way to execute this import via the CLI, that'd be great.

 

[jdancer]

You need to disable maxSessionCount and sessionTimeout on the ESXi host per https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE#Automatic_ESXi_Import:_Step_by_Step

 

[bv-joey]

You need to disable maxSessionCount and sessionTimeout on the ESXi host per https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE#Automatic_ESXi_Import:_Step_by_Step

While I appreciate the tip, it's unrelated.

Already turned off those settings, and that's a 30 minute timeout anyways not seconds. It's clear this is a GUI/API timeout based off similar posts such as https://forum.proxmox.com/threads/c...orage-disks-30-sec-timeout.133756/post-590138

 

[azzii]

I have the same problem. And it is also described in the topic:
https://forum.proxmox.com/threads/m...dding-esxi-virtualmachines-to-proxmox.147379/

/usr/libexec/pve-esxi-import-tools/listvms.py generate manifest correctly. tcpdump shows active packet exchange with the ESX host even after an error occurs. Judging by the log on the ESX side, proxmox successfully logs in to the host and even receives VMX files.

 

[Primox]

I had the same issue yesterday and my issue is a Datastore on ESXi that fail to connect. Note that no vm are related to this datastore in fact after deleting it all goes well.