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.

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

How reproducible:
always

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

  
Actual results:
guest driver loads

Expected results:
driver should not load, should prompt with no driver found dialog

Additional info:

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
http://download.devel.redhat.com/brewroot/work/tasks/6819/5586819/virtio-win-prewhql-0.1.zip

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.

http://rhn.redhat.com/errata/RHBA-2013-1729.html