Error during migration of a VMware VM to Proxmox

[Axiizix]

Hello,
I’m currently testing the migration of virtual machines from a vCenter to a Proxmox cluster, but I’m encountering a storage-related error:

“ERROR: Proxmox::WrapperProxmox::WrapperProxmoxImpl::ConnectSSH: Failed to open remote file: rbd:SharedVMs/vm-107-disk-0:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/SharedVMs.keyring”

“SharedVMs” is my shared CEPH storage.

All network flows are correctly opened, and I’m using the root account on the Proxmox side, so there shouldn’t be any permission issues.

Has anyone already encountered this problem?

[yaroslav (staff)]

Please share the entire log.

[Axiizix]

log in attachments

[yaroslav (staff)]

Please tell me more about the setup. What is the ESXi version you have? Did you try converting from ESXi, not the vCenter?
Did you try converting an offline VM disk?

[Axiizix]

Hello,
Thanks for your reply. I tried both from the vCenter and directly from the ESXi host, but without success.
The ESXi is running version 8U3 with vSAN storage. My Proxmox hosts are running version 8.3.5.
I’m using the root account for both ESXi and Proxmox.

The VM migration starts, but as soon as it tries to begin copying the storage (the VM was successfully recreated on the Proxmox side.), the V2V converter crashes abruptly after few seconds.

Would you happen to have the list of required network flows so I can double-check that side?

[yaroslav (staff)]

I will discuss it internally.
Thanks!

[ScooterSG1]

We are experiencing the same issue. Does anyone know if a previous version worked? The latest does not. Also, how can I download an earlier version?

[yaroslav (staff)]

There is no way to download the previous versions. I will update this thread once I hear from my colleagues.

[yaroslav (staff)]

This is a known issue.
The migration should work in future builds. Please keep an eye on the release notes https://www.starwindsoftware.com/v2v-co ... ease-notes.

[yaroslav (staff)]

Also, check out these threads.
https://forum.proxmox.com/threads/proxm ... em.153062/
https://forum.proxmox.com/threads/qemu- ... ost-682012

[willits]

This is a known issue.
The migration should work in future builds. Please keep an eye on the release notes https://www.starwindsoftware.com/v2v-co ... ease-notes.

Any update on this? I may be having the same issue. When I try to convert a VM from esx host or vCenter (v6.7u3) to a proxmox host, right before it starts to copy it crashes. Windows event log shows "Faulting module name: libssh2.dll". Seems like this version is broken so a working version would be much appreciated!

[yaroslav (staff)]

That's s non-StarWind DLL. Could you please let me know what is the OS installed on the machine that runs v2v?
See more https://stackoverflow.com/questions/221 ... on-windows

[willits]

That's s non-StarWind DLL. Could you please let me know what is the OS installed on the machine that runs v2v?
See more https://stackoverflow.com/questions/221 ... on-windows

I tried it on both my Windows 11, and a fresh Windows Server 2022 vm, same result. "Faulting Application name: V2V_Converter, version 9.0.1.755"

[yaroslav (staff)]

Download the DLL in question and put it in the V2V Converter's folder. See the similar issue https://stackoverflow.com/questions/221 ... on-windows.
I will check it additionally with my team.

[yaroslav (staff)]

Thanks for your patience.
I had a word with the dev team. This *.dll should be there (it comes with the installer). Try reinstalling the software.