How to Migrate VMs from VMware Vsphere to Proxmox cluster 8.1.4 (I cant Upgrade).

[Kuldeep.Roy]

I'm trying to migrate a VM from VMware vSphere to a Proxmox 8.1.4 cluster. Due to some constraints, I cannot upgrade Proxmox, so I need to work within this version.

To perform the migration, I used StarWind V2V Converter. However, I am getting this error.

2/1 17:03:16.378 75a0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: CreateVM
2/1 17:03:16.378 75a0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Set disks
2/1 17:03:16.378 75a0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: disk name i, pîÚ
2/1 17:03:16.378 75a0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Sending request
2/1 17:03:16.762 75a0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Responce is received
2/1 17:03:16.762 75a0 Facility ???ERROR: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Can not create virtual machine: 400
2/1 17:03:16.762 75a0 Facility ???WARNING: CPPConverting::Convert: CANCEL
2/1 17:06:43.679 15cf8 Facility ???INFO: VMConverter::ESXIConverter::Connection::<lambda_8874940e4602bbfc5e7b4b277e23eb86>:perator (): Timeout ESX connection
2/1 17:12:10.130 13698 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eLocation
2/1 17:12:11.507 13698 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eESXConnection

I think the disk name also comes as alphanumeric, I checked my VM name, and it has no spaces and special characters.

I have tried manual migration by exporting the VM as .vmdk then converting to qcow2 and scp to /var/lib/vz/images
but it is very long process as the VM sizes are pretty big.

 

[FrankList80]

I have to admit i do not know the StarWind Converter. With what i successfully migrated (manual sadly) Linux-VMs from XCP-NG to Proxmox was via "good ol" Clonezilla ISO Image and using the "Network Mode" (Reminder: use static IP adresses there). You have to start the Clonezilla ISO on "both sides", then one is 'Receiver' and one is 'Sender'. I would advise to have a dedicated NIC just for this exercise. I was able to convert 60-70 different "flavours and colors" of Linux-VMs with that. Unfortunately i have and still have with Windows-VMS. (Unsolved so far - still a lot of Bluescreens). I let the customer run a Legacy-Hypervisor until these Workloads "fade away".

---

​

[Virtualization Support for SME and NGOs | DLI Solutions ]

 

[ghusson]

I had problems importing from VMWare when disks where not in thick provisioning or with snapshots.
If you want, you can try this tool for windows VMs : https://learn.microsoft.com/en-us/sysinternals/downloads/disk2vhd
I already moved servers like that. But be carefull to the eventual lost of licensing (need to activate windows again).
Some info here : https://forum.proxmox.com/threads/m...dows-server-2016-essentials-to-proxmox.58499/