Cause: inf files come without explicit specification of revision ID.
Consequence: perfectly fine from Windows point of view but violates some virtio spec requirements.
Fix: add revision id to inf files.
Result: inf files explicitly specify revision id as part of HW identification string.
Description of problem:
virtio spec says that drivers should not bind to devices unless
revision ID is 0x0.
virtio-win drivers violate this spec, which will create
backwards compatibility problems down the road.
Version-Release number of selected component (if applicable):
WHQL version from 6.4
Steps to Reproduce:
1. open qemu source, edit hw/virtio-pci.c, change
revision from VIRTIO_PCI_ABI_VERSION to 0x1.
2. start windows guest with any virtio devices besides baloon,
and with virtio drivers loaded
guest driver loads
driver should not load, should prompt with no driver found dialog
Pls show me how to verify it ,Will something be added in XXX.inf ?
(In reply to comment #4)
> Pls show me how to verify it ,Will something be added in XXX.inf ?
yes, it's in INFs
For example for virtio-scsi inf specifies the full
HW id string as:
%RHELScsi.DeviceDesc% = rhelscsi_inst, PCI\VEN_1AF4&DEV_1004&SUBSYS_00081AF4&REV_00
where the last 7 symbols ('REV_00') is the revision ID.
Fixed in build 58
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.