Bug 908725
| Summary: | virtio win inf does not specify revision ID | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Michael S. Tsirkin <mst> |
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4 | CC: | acathrow, areis, bcao, bsarathy, juzhang, lnovich, michen, rhod |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-11-22 00:03:29 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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 |
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: