hyper-v to zfs zvol

[flexyz]

Hi

Any suggestions on how I can migrate windows and linux hyper-v images to my proxmox running ZFS - when I create a VM and specify a disk it will create a zvol (I think)

can I use qemu-img convert to raw or something like that and if so how?

Thanks a mill

 

[talos]

Hi,

i use StarWind V2V Converter to convert VMware or Hyper-V Images to Raw. It is a free application for Windows.

Then i create a new VM on an filesystem based storage, replace the disk with the converted one and migrate the disk to the final storage (zfs/lvm/...).

Hope this helps.

 

[Tomas Waldow]

Hi, i use Clonezilla. Here is a tutorial made by my self, it is in Portuguese, but you can translate.
https://www.2w.eti.br/convertendo-maquinas-fisicas-ou-virtuais-para-proxmox-com-clonezilla/

 

[fireon]

StarWind V2V Converter

Really, never used that before. Used always clonzezilla or vmwareconverter. Did this Starwind working well? Am very interested in it.

 

[flexyz]

I am still struggling and It looks like my main issue is that my VM are generation 2 windows - but still not sure.

So I am still trying, I will try CloneZilla today when I have some thing that works and will update here.

Thanks again

 

[flexyz]

I tried CloneZilla, but still no go but I think is related to UEFI bios - I tried this :

**********

qemu-img check -r all '/saspool/shares/temp/BuildMachine.vhdx'

qemu-img convert -f vhdx /saspool/shares/temp/BuildMachine.vhdx /saspool/shares/temp/BuildMachine.raw

dd if=//saspool/shares/temp/BuildMachine.raw of=/dev/zvol/saspool/vms/vm-101-disk-1 bs=1M

(I am using ZFS ZVOLs)

**********

fdisk -l /saspool/shares/temp/BuildMachine.raw

Disk /saspool/shares/temp/BuildMachine.raw: 127 GiB, 136365211648 bytes, 266338304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 26BB161F-D658-452F-B1F2-6C556322798E

***********

If I configure disk as IDE and SCSI controller default LSI my windows is booting...

Virtio drivers are installed but I can't figure out how to change to VirtiO drivers - when I do, it will not boot

Any suggestions?

Thanks!

 

[flexyz]

If I add an additional disk as virtio it works in Windows - but not from boot device

 

[flexyz]

I have something more working now, will try the procedure on another vm and update here..

 

[EnoEmas]

StarWind V2V does the job. https://www.starwindsoftware.com/converter
I have used it to convert Hyper-V VMs to ESXi ones on StarWind Virtual SAN lab cluster. Just works.

 

[flexyz]

Thanks

I ended up with this approach :

01. created a new KVM with same disk size and disk type IDE, BIOS = UEFI and Virtio ISO mounted to CDROM

02. copy vhdx to proxmox

03. qemu-img check -r all xxxxxxx.vhdx

04. qemu-img convert -f vhdx xxxxxxx.vhdx /dev/zvol/saspool/vms/vmxxx

05. verify boot option points to "ide0" and "qemu agent" = YES

06. boot windows

07. add device drivers "PCI communications" -> CDROM\vioserial\xx\yy

08. install qemu-agent

09. add legacy device drivers; balloon, kvmnet, storio, scsi

10. shutdown windows

11. add "virtio" disk 1GB

12. change network to "virtio"

13. boot windows

14. verify windows detects new (virtio) disk

15. shutdown

16. remove, remove virto 1GB disk

17. remove ide0 disk

18. change ide0 to Virtio

19.change boot options -> virtio0

20. start windows

21. done