Wed Jun 10, 2026 1:13 pm
Having read the linked article, I realize now that it points to use either the native built-in Proxmox ESXi solution.
Unfortunately that does not seem to be working for us too, as it give high CPU load on the Proxmox node, and Connection Timeouts.
This may be caused by our use of snapshots, which is documented to slow down things.
The alternative of manually importing is the workaround that we are trying to avoid, as we have quite a number of VMs to migrate.
I tried again using the StarWind V2V Converter by connecting directly to the ESXi host and converting a single disk.
I'm getting some additional UI pages, asking me to select or create a VM and the format on the target (RAW/Qcow2).
However, the Storages dropdown is still empty. I can continue the process and hit "Convert" in the end, but then it seems to stay stalled at 0%.