How to convert VM from proxmox to Hyper-V

[Nexsol]

Hi there!
I need to convert Windows11 VM to Hyper-V.
When I created Windows11, hdd is supposed to be one drive (scsi drive) but raw files are divided by partitions like "EFI Disk = vm-100-disk-0.raw", "HARD Disk (scsi0) = vm-100-disk-1.raw", "TPM State = vm-100-disk-2.raw".
So, I can create three vhdx disks each by qemu-img tool but I can't create one vhdx file has each partitions.
Does anyone who migrate such a Windows VM to Hyper-V?
Please help me!

 

[leesteken]

When I created Windows11, hdd is supposed to be one drive (scsi drive) but raw files are divided by partitions like "EFI Disk = vm-100-disk-0.raw", "HARD Disk (scsi0) = vm-100-disk-1.raw", "TPM State = vm-100-disk-2.raw".

The virtual disk is one file: vm-100-disk1.raw. The EFI Disk is not a (virtual) disk but a place the store the virtual UEFI BIOS settings. Same for the TPM state, which needs to be stored somewhere. Therefore, the other two .raw files are not disk.

So, I can create three vhdx disks each by qemu-img tool but I can't create one vhdx file has each partitions.

I don't know about Hyper-V but no, you probable don't need to do that. Find out how Hyper-V wants the UEFI settings and the TPM state and convert those two .raw files to it.

Does anyone who migrate such a Windows VM to Hyper-V?

You could also ask a Windows Hyper-V forum where there are probably more experts, and just tell the you have a QEMU/KVM VM (which is the underlying technology for Proxmox).

 

[Magnus-mercer]

Hi, maybe you can try Vinchin Backup & Recovery. You don't need to manually export and import disks to migrate virtual machines with it, just operating it in a unified interface. You can try the free version. For your questions, maybe you can also contact our technical team. Hope to get your feedback. Thank you.

 

[Nexsol]

The virtual disk is one file: vm-100-disk1.raw. The EFI Disk is not a (virtual) disk but a place the store the virtual UEFI BIOS settings. Same for the TPM state, which needs to be stored somewhere. Therefore, the other two .raw files are not disk.

I don't know about Hyper-V but no, you probable don't need to do that. Find out how Hyper-V wants the UEFI settings and the TPM state and convert those two .raw files to it.

You could also ask a Windows Hyper-V forum where there are probably more experts, and just tell the you have a QEMU/KVM VM (which is the underlying technology for Proxmox).

Thank you for replying!
I did backup without complession on proxmox to create vma file.
Then I used "vma extract" command to restore the scsi drive as raw file.
It has created one raw file.
So, I used "qemu-img" tool to convert raw file to Hyper-V vhdx file.
Then I created VM on Hyper-V with the vhdx file convered from Proxmox.
Finally, the VM (Windows11) wich has created on proxmox worked on Hyper-V!!
All drivers for Hyper-V VM are automatically installed.
I need to check all applications works correctly.
But I'm relieved
Thanks guys!!

 

[Nexsol]

Hi, maybe you can try Vinchin Backup & Recovery. You don't need to manually export and import disks to migrate virtual machines with it, just operating it in a unified interface. You can try the free version. For your questions, maybe you can also contact our technical team. Hope to get your feedback. Thank you.

Thank you for replying!
I could converted it to Hyper-V myself finally.
Thanks anyway!!