Migrating Hyper-V to Proxmox - what I learned

[fdcastel]

For those interested, I have compiled a set of instructions and scripts to address this problem, available here:

https://github.com/fdcastel/Hyper-V-Automation#windows-prepare-a-vhdx-for-qemu-migration

The provided scripts automate the process of taking a VHDX file, installing VirtIO drivers, and converting the VHDX to QCOW2 format.

 

[hazymat]

Out of interest do you know of similar guides for migrating Linux guests running on Hyper-V over to Proxmox?

For example, presumably I don't need to install VirtIO drivers or equivalent? What do I select for SCSI controller (default? virtio scsi?), BIOS, etc?

 

[fdcastel]

I can't think of a better one than Reading The Fine Manual:

https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_emulated_devices_and_paravirtualized_devices

It is highly recommended to use the virtio devices whenever you can, as they provide a big performance improvement and are generally better maintained.

 

[hazymat]

I can't think of a better one than Reading The Fine Manual:

https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_emulated_devices_and_paravirtualized_devices

Thanks, although that manual doesn't explain issues around different disk types in Hyper-V etc., for example I have imported a disk that was previously exported from Hyper-V (previously an IDE virtual disk) which worked fine. But now I am moving on to importing SCSI virtual disks and the VM is just not booting up as it can't see a boot disk.

I find the docs are great at being technical about the product itself, but not so good at describing issues around the use of the product. So you are left to discover an issue yourself which often takes a lot of research in the dark, only to find that the docs, whilst being good at describing the product, don't actually describe edge cases quite so well.

Hence I was asking here on a thread where someone had already pre-empted a lot of the issues importing Hyper-V virtual machines (of a windows VM), to see if there was a similar guide for doing the same but for a Linux VM where issues of drivers are dealt with differently.