Can't authenticate to Proxmox

VM image converter (VMDK, VHD, VHDX, IMG, RAW, QCOW and QCOW2), P2V migrator
yaroslav (staff)
Staff
Posts: 4373
Joined: Mon Nov 18, 2019 11:11 am

Wed Jun 10, 2026 1:04 pm

The problem with thin disks is that they are inflated during conversion; we are working on the conversion to keep them thin.
Anyway, the very fact that you can't see where you convert is not cool. I've reported it to the dev team.
rhp
Posts: 5
Joined: Mon Jun 08, 2026 12:13 pm

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%.
yaroslav (staff)
Staff
Posts: 4373
Joined: Mon Nov 18, 2019 11:11 am

Wed Jun 10, 2026 1:46 pm

Thank you for your update.
As an alternative, you can try the backup > restore method if your backup software allows for instant recovery.
Post Reply