I am trying to migrate some Windows 2019 (that use efi) from my old VMware cluster to a new Proxmox cluster. I Export the VM as an OVF, use the ovftool to convert it to an ova, import that into Proxmox, create an EFI disk, and boot. That's where it stops, it just sits at a shell prompt. No matter what I try, same thing happnes. Tried StarWind V2V converter, tried changing the harddisk from SCSI to IDE and SATA, changed the type of scsi controller to vmware, everything I have found. I would love some help here, this is slowing my migration project down.
Migrating Windows 2019 from VMware
- Thread starter wallerbk
- Start date
I successfully migrate some Server2019 machines with the following:
On the old hypervisor:
1. Execute mergeide.reg within the running VM: https://pve.proxmox.com/wiki/File:Mergeide.zip?ref=bra.live
This allow Windows Server 2019 to boot on an IDE disk controller later on, although it is currently running on a SCSI (virtualized) controller.
2. Clone the machine / disk image of the machine (i personally prefer the Vmware Converter to do that: https://www.heise.de/download/product/vmware-vcenter-converter-44320 )
On the new proxmox hypervisor:
3. Create a new machine with an 1 GB HDD as your prefered storage-type ( you should use virtio-scsi )
Use machine type q35
4. run qm import command with the exported vmdk drive via CLI:
qm importdisk <ID> <VMDK> <storage>
e.g.: qm importdisk 100 Server-01.local-0.vmdk local-zfs
5. The disk shows up in the VM but is not attached. Attach the disk as IDE [sic!] disk and change boot order to boot from this disk. The machine should boot normally up because you did step 1.
6. Install all virtio driver within the running WinServer 2019 via virtio driver cd rom. The virtio disk driver will be installed because of your empty 1 GB virtio drive from step 3 is found.
7. Shut down the machine:
- detach the 1 GB disk and remove it completely,
- detach your main drive c:\ disk and reattach it as virtio-scsi drive. It should run now, because you installed the driver in step 6
On the old hypervisor:
1. Execute mergeide.reg within the running VM: https://pve.proxmox.com/wiki/File:Mergeide.zip?ref=bra.live
This allow Windows Server 2019 to boot on an IDE disk controller later on, although it is currently running on a SCSI (virtualized) controller.
2. Clone the machine / disk image of the machine (i personally prefer the Vmware Converter to do that: https://www.heise.de/download/product/vmware-vcenter-converter-44320 )
On the new proxmox hypervisor:
3. Create a new machine with an 1 GB HDD as your prefered storage-type ( you should use virtio-scsi )
Use machine type q35
4. run qm import command with the exported vmdk drive via CLI:
qm importdisk <ID> <VMDK> <storage>
e.g.: qm importdisk 100 Server-01.local-0.vmdk local-zfs
5. The disk shows up in the VM but is not attached. Attach the disk as IDE [sic!] disk and change boot order to boot from this disk. The machine should boot normally up because you did step 1.
6. Install all virtio driver within the running WinServer 2019 via virtio driver cd rom. The virtio disk driver will be installed because of your empty 1 GB virtio drive from step 3 is found.
7. Shut down the machine:
- detach the 1 GB disk and remove it completely,
- detach your main drive c:\ disk and reattach it as virtio-scsi drive. It should run now, because you installed the driver in step 6
Last edited:
