New Import Wizard Available for Migrating VMware ESXi Based Virtual Machines

[jlauro]

I started importing with the default import config and the process was extremely slow, so that I had to cancel the process.
I was at 5% of 64 GB after 2 hours !.

What can I do ?. Anything more to do before migration ?

Make sure there is no snapshots on the vm you are trying to import. (surprisingly extremely important for performance)
Make sure the management interfaces on both the vmware server and proxmox server are both good. (ie: not 1gb unless all are 1gb anyways).
Have the management interfaces on the same subnet so no routers slowing the transfer.
Test network connectivity. From the proxmox host:

ping vmwarehost 15000 -c 100 -q -A

1gb to 1gb on my homelab looks like:
PING 10.254.201.23 (10.254.201.23) 15000(15028) bytes of data.

--- 10.254.201.23 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99ms
rtt min/avg/max/mdev = 0.527/0.589/0.910/0.070 ms, ipg/ewma 1.001/0.575 ms

A 10gb looks more like:
PING vm8 (10.0.2.208) 15000(15028) bytes of data.

--- vm8.ces.cvnt.net ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 141ms
rtt min/avg/max/mdev = 0.098/0.155/0.237/0.030 ms, ipg/ewma 1.424/0.152 ms

The ping specifically has 15,000 bytes to so that it will ensure things like MTU are set correctly on both as it's bigger than both normal and typical jumbo frames to force fragmentation.

 

[Futurematic]

Make sure there is no snapshots on the vm you are trying to import. (surprisingly extremely important for performance)
Make sure the management interfaces on both the vmware server and proxmox server are both good. (ie: not 1gb unless all are 1gb anyways).
Have the management interfaces on the same subnet so no routers slowing the transfer.
Test network connectivity. From the proxmox host:

ping vmwarehost 15000 -c 100 -q -A

1gb to 1gb on my homelab looks like:
PING 10.254.201.23 (10.254.201.23) 15000(15028) bytes of data.

--- 10.254.201.23 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99ms
rtt min/avg/max/mdev = 0.527/0.589/0.910/0.070 ms, ipg/ewma 1.001/0.575 ms

A 10gb looks more like:
PING vm8 (10.0.2.208) 15000(15028) bytes of data.

--- vm8.ces.cvnt.net ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 141ms
rtt min/avg/max/mdev = 0.098/0.155/0.237/0.030 ms, ipg/ewma 1.424/0.152 ms

The ping specifically has 15,000 bytes to so that it will ensure things like MTU are set correctly on both as it's bigger than both normal and typical jumbo frames to force fragmentation.

Thanks a lot for the reply. It was the snapshot which seemed to be the problem. After deleting the snapshot migration was without problems !.

 

[kadarpik]

This is very nice tool but works in 50% of cases, latest error I got from vmware 6.5.0 Update 3 (Build 18678235) is can not stat vmdk file, this happens immidiate at the beginning of import process. I have imported other vm guest from the same host, it is question of the vm guest.

Second error is vmdk and guest names with spaces, this is not the esxi import tool favourite, it fails with error.