P2V Win Srv 2016 not booting on Proxmox

[Jetro]

Hello everyone,

It's a couple days I'm struggling with a Windows Server 2016 migration. Here what I've done:

1. Installed VirtIO drivers on the phisical srv (even if probably it's useless)
2. Exported a qcow2 image with Starwind P2V Converter
3. Imported the qcow2 on proxmox and created a vm with following settings

root@pve2:~# qm config 202
agent: 0
boot: order=scsi0
cores: 4
cpu: host
efidisk0: pve2-zfs:vm-202-disk-1,efitype=4m,pre-enrolled-keys=1,size=1M
hotplug: usb
ide0: local:iso/VirtIO_Drivers_Win_0.1.229.iso,media=cdrom,size=522284K
ide1: local:iso/WindowsServer2016_Eval_it-it.iso,media=cdrom,size=6776980K
machine: pc-i440fx-8.0
memory: 8192
meta: creation-qemu=8.0.2,ctime=1689768063
name: Srv2016
numa: 0
ostype: win10
scsi0: pve2-zfs:vm-202-disk-0,cache=writeback,discard=on,size=953838M
scsihw: virtio-scsi-pci
smbios1: uuid=(...)
sockets: 1
vmgenid: (...)

Booted from the iso installation image and successfully re-installed vioscsi.inf (from the latest version linked on proxmox wiki) with the following command:

dism /image:C:\ /add-driver /driver:vioscsi.inf

Then exited and tried to boot Windows but got BSOD with the famous error:

INACCESSIBLE_BOOT_DEVICE

---
I've tried many combinations, with standard BIOS it doesn't recognize boot device and setting the disk image as SATA or IDE device doesn't boot with a different error:

KMODE EXCEPTION NOT HANDLES

It really looks like something driver related, but I have no idea on how to boot that.

Additional info:
- If I try to re-install Windows, after driver install, I can see the virtual drive.
- If I assign the virtual drive to another Windows VM with virtio drivers I can see and browse it.