ESXi import failing

itsnota2ma

New Member
Feb 5, 2025
22
1
3
Milwaukee, WI
I finally figured out how to get my Dell SAN multipath configured. I am connect to the vCenter and can see the VM's. When I try to import a VM, I get this error:

can't open '/run/pve/import/esxi/......Webserver.vmx' - Transport endpoint is not connected (500)

I sifted through the forum here and several people had the same issue, however none of them posted how it was fixed. The VM is off and does not have any snapshots. Not sure what the issue is.
 
Please refer to the following regarding migration. It supports various migration methods.

https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE

I do not know which migration method the original poster first tried, but I assume they most likely used “Automatic ESXi Import: Step by Step” from the URL above, which is integrated into the GUI.

As described there, migration via vCenter is also possible, but it is not recommended.
Also, even if you connect directly to the server, you are still subject to ESXi API throttling.
As a result, if you try to migrate a VM above a certain size, the process may fail due to a timeout.
The exact size at which timeouts occur depends on the environment, but in my environment, about 2 TB was the rough threshold.

You could try another product such as Veeam, or you could try one of the other methods described in the wiki.
I often use “Attach Disk & Move Disk (minimal downtime)”.
That is because the VM downtime is small, and as long as you can access the .vmdk, there is no need to prepare tools such as OVF Tool.
 
Please refer to the following regarding migration. It supports various migration methods.

https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE

I do not know which migration method the original poster first tried, but I assume they most likely used “Automatic ESXi Import: Step by Step” from the URL above, which is integrated into the GUI.

As described there, migration via vCenter is also possible, but it is not recommended.
Also, even if you connect directly to the server, you are still subject to ESXi API throttling.
As a result, if you try to migrate a VM above a certain size, the process may fail due to a timeout.
The exact size at which timeouts occur depends on the environment, but in my environment, about 2 TB was the rough threshold.

You could try another product such as Veeam, or you could try one of the other methods described in the wiki.
I often use “Attach Disk & Move Disk (minimal downtime)”.
That is because the VM downtime is small, and as long as you can access the .vmdk, there is no need to prepare tools such as OVF Tool.
@d.oishi
I have tried the Veeam route, which also failed. I have also tried to upload a file (80GB) to the datastore, which also failed half-way through. I am starting to think it has to do with the way the LVM is configured?? I know Dell does not formally support ProxMox, so I cannot lean on them to help me out either. Because the datastore is RAW, I am not able to SSH files to it and have ProxMox recognize them.
 
I have tried the Veeam route, which also failed. I have also tried to upload a file (80GB) to the datastore, which also failed half-way through. I am starting to think it has to do with the way the LVM is configured?? I know Dell does not formally support ProxMox, so I cannot lean on them to help me out either.
Since Veeam officially supports Proxmox, you may want to reach out to Veeam for assistance.
Also, if this is a critical environment and you need to complete the migration quickly, purchasing a Proxmox subscription could be another option.

https://www.proxmox.com/en/products/proxmox-virtual-environment/pricing

Because the datastore is RAW, I am not able to SSH files to it and have ProxMox recognize them.
As an alternative that does not depend on the hypervisor layer, Clonezilla might also be worth trying.
It is introduced there as a P2V option, but it can also be used for V2V.

https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE
 
  • Like
Reactions: UdoB