virtualbox.org

Thanks for the info, Raven. That U drive was throwing me off...

I tried a virtio-scsi disk in a Windows 10 2004 guest. The controller needed the Red Hat drivers, and appears to load well. But the attached disk does not appear in Device Manager or Disk Management.

I tried the same thing in a Windows 7 guest and got the same result. With the Red Hat drivers, the scsi controller appeared, but the attached disk is MIA.

Either we are doing something wrong, or there is something not kosher about the virtio-scsi implementation yet.

I concur so far with Aphrodite & Raven, the virtio-scsi controller appears, but the attached disk does not appear.

I tested QEMU for Windows with virtio-scsi controller, and if the disk image format (qcow2 or raw) was not defined in blockdev parameter, Win10 guest detected a disk capacity is 0 (zero).

Perhaps Virtualbox should tell virtio-scsi pass-through-controller Windows guest os that is using the vdi disk format.

I have the same issue with:

• Windows Server 2019 guest os,
  latest Virtualbox (6.1.18),
  lastest virtio driver (virtio-win-gt-x64.msi - 2020-11-24 02:37 5.9M) downloaded from fedorapeople

Anyone know how to solve this?