Transferred the Win10 virtual machine from hyper-v to proxmox

[Walery]

Transferred the Win10 virtual machine from hyper-v to proxmox. Disk converted by StarWind V2V Converter from .vhdx to .qcow2.
The VM has booted up. I install the virtio-win-0.1.185.iso drivers, reboot the virtual machine and after that win10 is no longer loaded. The start boot option hangs.
Tell me how to reanimate?

 

[Dominic]

Could you post qm config <vmid>. Have you tried another virtio iso version already?

 

[Walery]

Could you post qm config <vmid>. Have you tried another virtio iso version already?

root@prox:~# qm config 102
agent: 1
bios: ovmf
boot: order=ide2;sata0;net0
cores: 2
efidisk0: vm:102/vm-102-disk-1.qcow2,size=128K
ide2: none,media=cdrom
memory: 4096
name: t2
net0: e1000=C2:CBD:37:ED:E7,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
sata0: vm:102/win10_1607.qcow2,size=45G
scsihw: virtio-scsi-pci
smbios1: uuid=95963d08-898f-4afd-a92e-32732d308d23
sockets: 1
vmgenid: 7bf49d5b-bf15-45f2-98f9-941f99001aad
root@prox:~#

Not. I used the latest stable release virtio iso.


P.S.
Booting from the Windows 10 iso and choosing "Repair your computer" then "Exit and continue to Windows 10" will let me boot just fine.
After downloading, I click shutdown. After this, the system no longer boots? Is the bootloader damaged?
I tried to restore the bootloader but it didn't help.

i found this problem
https://forum.proxmox.com/threads/uefi-boot-problem.66887/
I also use Windows 10 Enterprice 2016 LTSB

 

[Walery]

I continued the experiment. Transferred Windows server 2016 from from hyper-v to proxmox and after installing the virtio driver the system boots normally.
Windows server 2016 standart
1607
14393.4046


Version that doesn't work
Windows 10 2016 LTSB 1607 14393.4225

 

[Dominic]

....
i found this problem
https://forum.proxmox.com/threads/uefi-boot-problem.66887/
I also use Windows 10 Enterprice 2016 LTSB

The statement that Proxmox VE has problems with some Windows image and KVM does not sounds strange to me, because Proxmox VE does actually use KVM. If you start a VM in Proxmox VE you can

ps -aux | grep kvm

and you will see the the exact KVM command that gets executed. Therefore, if you somehow get your VM working manually then you can compare the parameters of the processes.

Could you please try one or two additional versions of the virtio drivers?

Furthermore,

1. make sure to always update your boot order
   

   boot: order=ide2;sata0;net0

   ide2 is empty in your case.

2. sata0: vm:102/win10_1607.qcow2,size=45G

   This is not recommended and will likely bring you into trouble. You should rename your disk image to vm-102-disk-0.qcow2. To rule out errors I would then qm rescan --vmid 102 to automatically find and add the image as unused disk. You can then go to the GUI and attach it again. Or, you just change win10_1607 in the config to vm-102-disk-0 after renaming the image. Check the boot order again.

 

[Walery]

ps -aux | grep kvm

and you will see the the exact KVM command that gets executed. Therefore, if you somehow get your VM working manually then you can compare the parameters of the processes.

root@prox:~# ps -aux | grep kvm
root 22080 8.6 12.9 4911852 4241736 ? Sl Feb11 98:16 /usr/bin/kvm -id 102 -name t2 -no-shutdown -chardev socket,id=qmp,path=/var/run/qemu-server/102.qmp,server,nowait -mon chardev=qmp,mode=control -chardev socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5 -mon chardev=qmp-event,mode=control -pidfile /var/run/qemu-server/102.pid -daemonize -smbios type=1,uuid=95963d08-898f-4afd-a92e-32732d308d23 -drive if=pflash,unit=0,format=raw,readonly,file=/usr/share/pve-edk2-firmware//OVMF_CODE.fd -drive if=pflash,unit=1,format=qcow2,id=drive-efidisk0,file=/mnt/hostrun/content/images/102/vm-102-disk-1.qcow2 -smp 2,sockets=1,cores=2,maxcpus=2 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg -vnc unix:/var/run/qemu-server/102.vnc,password -no-hpet -cpu kvm64,enforce,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vpindex,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep -m 4096 -device pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e -device pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f -device vmgenid,guid=7bf49d5b-bf15-45f2-98f9-941f99001aad -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -device usb-tablet,id=tablet,bus=uhci.0,port=1 -device VGA,id=vga,bus=pci.0,addr=0x2 -chardev socket,path=/var/run/qemu-server/102.qga,server,nowait,id=qga0 -device virtio-serial,id=qga0,bus=pci.0,addr=0x8 -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi initiator-name=iqn.1993-08.org.debian:01:b44d438070d7 -drive file=/var/lib/vz/template/iso/en-ru_windows_10_enterprise_ltsb_2016_with_update_14393.4169_aio_2in1_x64_v21.01.12_by_adguard.iso,if=none,id=drive-ide2,media=cdrom,aio=threads -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=100 -device ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7 -drive file=/mnt/hostrun/content/images/102/win10_1607.qcow2,if=none,id=drive-sata0,format=qcow2,cache=none,aio=native,detect-zeroes=on -device ide-hd,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=101 -netdev type=tap,id=net0,ifname=tap102i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown -device e1000,mac=C2:CBD:37:ED:E7,netdev=net0,bus=pci.0,addr=0x12,id=net0 -rtc driftfix=slew,base=localtime -machine type=pc+pve0 -global kvm-pit.lost_tick_policy=discard
root 22084 0.0 0.0 0 0 ? S Feb11 0:00 [kvm-nx-lpage-re]
root 22128 0.2 0.0 0 0 ? S Feb11 3:11 [kvm-pit/22080]
root 61719 0.0 0.0 6072 892 pts/0 S+ 11:08 0:00 grep kvm
root@prox:~#

boot: order=ide2;sata0;net0

ide2 is empty in your case.

ide2 is dvd-rom and it is disabled (empty)

 

[Walery]

Hello. I have installed PVE 6.3-4. Created storage (store1) (ZFS).
Converted disk from Hyper-v win10.vhdx to win10.qcow2
Created a new virtual machine in PVE. The win10.qcow2 disk was copied using WinSCP to the storage (store1) (ZFS). How can I connect the win10.qcow2 drive to the created virtual machine?

P.S.
As far as I understand, I cannot use .qcow2 disks in ZFS
Need to only use .raw?

 

[Dominic]

Usually you should not see .qcow2 in your ZFS dataset name.

You have to add your disk image to the config as in the code snippet in enumeration point 2 above. Or try to use qm importdisk which handles issues like setting correct names for you.