Problem with VirtIO in Windows Server 2012 r2 installation

G

Godoy

New Member
Sep 23, 2022
4
0
1
Hello, I am having difficulties installing the VirtIO drivers when I try to install Windows Server 2012 r2, I always get the message "no signed device drivers were found. Make sure that the installation media contains the correct drivers, and the click OK ".
I followed the steps of both the official proxmox guide and in several forum posts, I tried everything and I still can't get it to work.
surely it will be some very absurd mistake or I don't know, seriously if someone would know what I could try I would appreciate it.

Windows Server 2012 r2 x64
VirtIO 1.221
SCSI Controller: VirtIO SCSI
Qemu Agent: Enabled
Memory: 4gb
Processors: 2 (1 socket, 2 cores)
Hard disk: 64gb - cache: writeback - discard: enable
Network: VirtIO(paravirtualized)

Note: Qemu Agent is disabled because then it does not allow the VM to be stoped or Shutdown
 

Attachments

  • 1.png
    1.png
    44.6 KB · Views: 177
  • 2.png
    2.png
    46.6 KB · Views: 164
Hi Moayad, I don't think that is the problem (I saw that in forums they use the last version and it works perfectly), but could I try, do I try with any version or do I try a specific version?
 
The windows install is very picky on the location of drivers.
You can't just set e:\ as driver location, you'll have to define the full path like e:\virtiostor\server2012\amd64\ (or something like that).
 
I tried again to install with version 1.217 of VirtIO, the problem when searching for the drivers persists, I have tried folder by folder and always the same error... but if I let it scan, instead of searching manually by folder, it finds these drivers (photo ).
If I install these drivers will it work the same way? And which one would help me to correctly install Windows Server 2012 r2? since it does not appear as an option
 

Attachments

  • 3.png
    3.png
    66.5 KB · Views: 204
I ran into similar odd issues but can confirm no issues using the Virtio-win-0.1.215 version of the ISO
Only weird thing to note is even after running the installer on the ISO, I had to manually install the correct SPICE driver (if in use) from device manager.
 
  • Like
Reactions: StreetPiet and ITT
Hi, so with this version you said the WS2012r2 drivers appear? if so, I will try again.
I don't know if the use of the SPICE driver is essential for the VM to work correctly, what would be the effect of not installing it?
bleglord said:
I ran into similar odd issues but can confirm no issues using the Virtio-win-0.1.215 version of the ISO
Only weird thing to note is even after running the installer on the ISO, I had to manually install the correct SPICE driver (if in use) from device manager.
Click to expand...
 
Godoy said:
Hi, so with this version you said the WS2012r2 drivers appear? if so, I will try again.
I don't know if the use of the SPICE driver is essential for the VM to work correctly, what would be the effect of not installing it?
Click to expand...
Correct, the auto-loading of the CD drivers was detecting normally during install for the disk drivers. The SPICE driver is only needed if you use the SPICE access from proxmox GUI for a smoother console experience, for RDP/other remote access tools I don't believe it's needed.
 
  • Like
Reactions: Godoy
bleglord said:
I ran into similar odd issues but can confirm no issues using the Virtio-win-0.1.215 version of the ISO
Only weird thing to note is even after running the installer on the ISO, I had to manually install the correct SPICE driver (if in use) from device manager.
Click to expand...
Thank you @bleglord

Under Windows 8.1 Virtio-win-0.1.215 work also (in the install process of the OS)
working.png

I tried the virtio-win-0.1.221 before but they gave
no signed device drivers error

Cheers,
 
Here to report v0.1.225-2 is still broken. v0.1.215-2 /viostor/2k12R2/amd64 worked for me as well.
 
hello, keen to contribute my ten cents worth to this knowledge byte facilitating the migration of windows server 2012R2 from the now less favored vmware ESXI (ancient version 6.0 in my case) to proxmox.
This is in the context of having suffered an exacerbation of RSI in my neck and mouse-clicking hand in the course of understanding and performing the delicate manipulation.
Using the .189 iso as advised above seems to have been the deal maker, ie virtio-win-0.1.189.iso, rather than more recent ISO versions of .240 and .248 (even though the directory structure and path to the vioscsi.sys driver in the ISO seems to be the same ie D:vioscsi\2k12\amd64\vioscsi.inf).

To summarise, use the proxmox built in import ESXI tool. In my case I accepted the proxmox ESXI importing defaults, including the e1000e network driver, scsi0 for the HDD, sata0 when attaching the .189 ISO and correcting for the windows installation (8/8.x/2012/2012RS) in the importing configuration window.
This completed without incident.
Then when setting this up as a proxmox VM, for the SCSI controller I chose the virtiO SCSI single option rather than the default, for the HDD options I chose 'no cache', Async IO 'native' and 'Discard' was not selected. The network device remained as the e1000e. Ensure the virtio .189 ISO remains attached.
Booting will stall as described above, which is when you need the command line to manually install the vioscsi driver. There is currently an excellent guide for this at https://hull.au/blog/install-virtio-drivers-from-windows-recovery/ which in summary involves these commands:
Code: 
drvload D:vioscsi\2k12\amd64\vioscsi.inf
diskpart
list disk
list volume (to find the windows 2012 Server R2 drive letter eg E:)
E: ie type 'E:' to switch to the windows drive being E:
dism /Image:E:\ /Add-Driver:D:\vioscsi\2k19\amd64\vioscsi.inf (to  insert the vioscsi.inf driver to the windows server installation (E:))
exit (you should be taken back to the blue screen to then resume installation)

in the proxmox video https://www.proxmox.com/en/services...vironment/proxmox-ve-import-wizard-for-vmware there is post installation advice but I don't think this is needed here as the virtiO driver is already installed. But I am happy to take advice on this
HTH!
MSandy
 
Info for someone that not already know:
Keep attention to virtio versions > 0.1.208 and < 0.1.266 that have important issue on virtio scsi driver
 
You must log in or register to reply here.
Top Bottom