Migrating Windows to Proxmox/Virtio SCSI single device without intermediary IDE/sata boot drive

[ThomasGlanzmann]

Hello,
I get often asked by customers how to install the virto
drivers before the migration in a way that they can be
immediatly be used with virtio scsi single devices without
an intermediary boot using an ide drive and an empy virtio
scsi single device. And today we solved the issue in a
qskills proxmox training. The trick is: Device Manager > Add
legacy hardware > Next > (*) Install the hardware ... >
Storage Controllers > Have Disk > d:\amd64\2k25\vioscsi
(.inf) > Red Hat Virtio SCSI pass-through controller. You
can than immediatly delete delete the device again: Red Hat
VirtIO SCSI pass-through controller > Uninstall device >
Uninstall (Do *not* check Attempt to remove the driver for
this device because than you end up with the usual blue
screen). We then vibecoded everything we needed to perform
an automated migration: Put the drivers for virtio scsi and
virtio scsi single device, install virtio drivers, install
qemu agent, uninstall vmware tools, document the network
settings and put all network cards per dhcp. Find the
powershell scripts on my homepage.

Cheers,
Thomas

 

[santiagobiali]

This powershell works too, where D:\ is your virtio drive (or folder) and 2k22 your OS version:

Get-ChildItem -Recurse -File D:\ | Where-Object {$_.Extension -eq ".inf" -and $_.FullName -like '*\2k22\amd64*'} | ForEach-Object { PNPUtil.exe /add-driver "$($_.FullName)" /install }

 

[ThomasGlanzmann]

I tried your approach on a w2k25. Fresh w2k25, latest virtio.iso. Your prompt but 2k22 replaced with 2k25 and the VM gives me a blue screen on first boot. With the phantom device approach above it boots without bluescreen. I just found out that someone else has a script with the same method on github: croit / load-virtio-scsi-on-boot