Virtio Drivers for iSCSI Controller on Windows Server 2016 Code 28

[JSChasle]

I imported a Windows 2016 VM from ESXi into Proxmox 7.4.3 (using the OVF convertion Tool), then changed the Drivre to Sata (So I could boot into the machine). It has 3 drives. Only changed the Boot drive. Then booted into the server installed the Virtio-win-0.1.229 and reboooted and in device manager I see an other perifiral for my SCSI controller as Code 28, tried to install the driver manually from the ISO (using vioscsi/2k16/ folder) but windows says the driver is not the right one. Am I missing something obvious as why the driver can't install. \VEN_1000&DEV_0012&SUBSYS_1000000&REV_00\3&267a616a&1&28

Thanks

 

[emunt6]

My personal experience, the VirtIO is not stable under any Windows OS.
VirtIO is recommended for LINUX ( virtio-net, virtio-scsi ).
Leave the Storage controller to "Default", and assign the discs to the VM as sata0, sata1, sata2, .. etc,. This case, you dont need to add any drivers to the Windows.
You can edit the VM config manually:
/etc/pve/qemu-server/<id>.conf

 

[JSChasle]

My personal experience, the VirtIO is not stable under any Windows OS.
VirtIO is recommended for LINUX ( virtio-net, virtio-scsi ).
Leave the Storage controller to "Default", and assign the discs to the VM as sata0, sata1, sata2, .. etc,. This case, you dont need to add any drivers to the Windows.
You can edit the VM config manually:
/etc/pve/qemu-server/<id>.conf

Hi,

But then using SATA I have awfull read and writes? Like for NVME I dont even reach 500mo (using a a Liquid LQD4500 card). Is there some tweak?

Thanks