Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
I think this is related to the "exclamation marks" in the device manager.
Until you have a driver, all that Windows can do is report a generic name based on the PCI class. The PCI class is the same for virtio-blk and virtio-scsi. The valid classes are
#define PCI_CLASS_STORAGE_SCSI 0x0100
#define PCI_CLASS_STORAGE_IDE 0x0101
#define PCI_CLASS_STORAGE_RAID 0x0104
#define PCI_CLASS_STORAGE_SATA 0x0106
#define PCI_CLASS_STORAGE_EXPRESS 0x0108
#define PCI_CLASS_STORAGE_OTHER 0x0180
but WHQL requires virtio-blk to use PCI_CLASS_STORAGE_SCSI and not, for example, PCI_CLASS_STORAGE_OTHER. See this upstream commit:
commit 5c634ef30d75fd7024929b34d383eea1bae732d7
Author: Mark McLoughlin <markmc>
Date: Tue Jul 7 12:09:10 2009 +0100
Change default PCI class of virtio-blk to PCI_CLASS_STORAGE_SCSI
Windows virtio driver cannot pass DTM (certification) tests while the
storage class is PCI_CLASS_STORAGE_UNKNOWN.
A new qdev type is introduced to allow devices using the old class
to be created for compatibility with qemu-0.10.x.
Reported-by: Dor Laor <dlaor>
Signed-off-by: Mark McLoughlin <markmc>
Signed-off-by: Anthony Liguori <aliguori.com>
I think this is related to the "exclamation marks" in the device manager. Until you have a driver, all that Windows can do is report a generic name based on the PCI class. The PCI class is the same for virtio-blk and virtio-scsi. The valid classes are #define PCI_CLASS_STORAGE_SCSI 0x0100 #define PCI_CLASS_STORAGE_IDE 0x0101 #define PCI_CLASS_STORAGE_RAID 0x0104 #define PCI_CLASS_STORAGE_SATA 0x0106 #define PCI_CLASS_STORAGE_EXPRESS 0x0108 #define PCI_CLASS_STORAGE_OTHER 0x0180 but WHQL requires virtio-blk to use PCI_CLASS_STORAGE_SCSI and not, for example, PCI_CLASS_STORAGE_OTHER. See this upstream commit: commit 5c634ef30d75fd7024929b34d383eea1bae732d7 Author: Mark McLoughlin <markmc> Date: Tue Jul 7 12:09:10 2009 +0100 Change default PCI class of virtio-blk to PCI_CLASS_STORAGE_SCSI Windows virtio driver cannot pass DTM (certification) tests while the storage class is PCI_CLASS_STORAGE_UNKNOWN. A new qdev type is introduced to allow devices using the old class to be created for compatibility with qemu-0.10.x. Reported-by: Dor Laor <dlaor> Signed-off-by: Mark McLoughlin <markmc> Signed-off-by: Anthony Liguori <aliguori.com>