VirtualBox

Opened 4 years ago

Closed 17 months ago

#19674 closed defect (fixed)

VirtIO-SCSI controller fails to see disk

Reported by: Feline Owned by:
Component: virtual disk Version: VirtualBox 6.1.10
Keywords: virtio scsi windows Cc:
Guest type: Windows Host type: Linux

Description

I appreciate that the VirtIO-SCSI support is currently experimental but I have been doing some testing of it. It works fine with my Debian guests, both for attaching data volumes and to boot from.

However, when using Windows 10, I cannot get any disks that are attached to the controller to be seen inside the Windows 10 guest. I have installed the RedHat drivers for Windows from the Fedora site, both the current stable version and the latest build but they both exhibit the same behaviour.

The controller shows up in Device Manager but the disk attached to it does not show in either Device Manager or Disk Management. The Event log seems to show an error when it attempts to start the device but I may have misread the entry.

My Host is Debian 10.4 running VirtualBox 6.1.10. The guest is Windows 10 (Update 2004, OS Build 19041.329) The virtio-scsi drivers are the current stable version - 100.77.104.17100

I have attached the guests machine log and .vbox file. Furthermore, I have attached prints of the Storage Controller and Disks section from Device manager, which show the drive details and the controller information within the Windows 10 guest. I have also attached the guest Event Log entries for the controller.

If there are any other troubleshooting procedures I can take, please ask.

Thank you.

Attachments (5)

Windows Testing.vbox (5.7 KB ) - added by Feline 4 years ago.
Windows Testing-2020-06-19-16-54-20.vboxlog (147.7 KB ) - added by Feline 4 years ago.
Drives.txt (472 bytes ) - added by Feline 4 years ago.
Disks section from Device Manager within Guest
Storage Controllers.txt (558 bytes ) - added by Feline 4 years ago.
Storage Controller section from Device Manager within Guest
EventLog.txt (3.0 KB ) - added by Feline 4 years ago.
Guest Windows Event Log for the Storage Controller

Download all attachments as: .zip

Change History (13)

by Feline, 4 years ago

Attachment: Windows Testing.vbox added

by Feline, 4 years ago

Attachment: Drives.txt added

Disks section from Device Manager within Guest

by Feline, 4 years ago

Attachment: Storage Controllers.txt added

Storage Controller section from Device Manager within Guest

by Feline, 4 years ago

Attachment: EventLog.txt added

Guest Windows Event Log for the Storage Controller

comment:1 by Feline, 4 years ago

See also forum entry https://forums.virtualbox.org/viewtopic.php?f=6&t=98908 for further discussion.

comment:2 by Telestar, 3 years ago

Last edited 3 years ago by Telestar (previous) (diff)

comment:3 by Telestar, 3 years ago

Same issue is present in Windows 7 x64 and Windows 7 x86 guests under 6.1.22 r144080, both at installation as well as in the OS later. Very annoying.

comment:4 by hydroptix, 2 years ago

Issue still present.

Virtualbox 6.1.32_Ubuntu r149290

Host: Ubuntu 20.04.4 LTS

Guest: Windows 10 build 14393.5006 and Windows 11 build 22000.318

VirtIO Windows drivers v0.1.215

Last edited 2 years ago by hydroptix (previous) (diff)

comment:5 by tagarista89, 2 years ago

Issue still present.

Virtualbox 6.1.34

Host: Ubuntu 22.04 LTS

Guest: Windows 10 21H2

VirtIO Windows drivers v0.1.217

comment:6 by sercallegar, 20 months ago

This is also the case with Win11. Seen with Virtuabox 6.1.36.

The control panel reports the "Red Hat VirtIO SCSI pass-through controller" 100.91.104.22100 as installed and working properly.

However, disks attached to this interface are not visible in the Guest OS.

Furthermore, and I do not know if this is relevant, when I go to see the events associated to the VirtIO SCSI in windows, in the information area it says:

"Device PCI\VEN_1AF4&DEV_1048&SUBSYS_10481AF4&REV_01\3&267a616a&0&78 requires further installation."

as the first event. I do not think that this is important as the following events are probably the mentioned configuration. In fact, the last information message is:

"Device PCI\VEN_1AF4&DEV_1048&SUBSYS_10481AF4&REV_01\3&267a616a&0&78 was started.

Driver Name: oem7.inf Class Guid: {4d36e97b-e325-11ce-bfc1-08002be10318} Service: vioscsi Lower Filters: Upper Filters:"

Last edited 20 months ago by sercallegar (previous) (diff)

comment:7 by sercallegar, 17 months ago

Seems to work now with 7.0.2

comment:8 by aeichner, 17 months ago

Resolution: fixed
Status: newclosed

Thanks for the update, glad it works for you know.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use