Bug 1358125
Summary: | Virtio 1.0 driver didn't work on win10 with q35 machine type | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Yiqian Wei <yiwei> |
Component: | virtio-win | Assignee: | Ladi Prosek <lprosek> |
virtio-win sub component: | virtio-win-prewhql | QA Contact: | Virtualization Bugs <virt-bugs> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | high | CC: | ailan, chayang, jinzhao, juzhang, lijin, lprosek, mkolaja, vrozenfe, wyu, xfu, yiwei |
Version: | 7.3 | Keywords: | Reopened |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: |
NO_DOCS
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-04 08:55:23 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: |
Description
Yiqian Wei
2016-07-20 06:36:01 UTC
This is caused by a missing initialization of a bus-related field in viostor, which is why it only reproduces on PCIe. Vioscsi uses a similar code pattern but does not have this issue. Could you try with latest build 124? https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=506954 (In reply to lijin from comment #4) > Could you try with latest build 124? > https://brewweb.engineering.redhat.com/brew/buildinfo?buildID==506954 Hi lijin, I've tested with latest build 124,After driver update, disk can be found. Version: kernel-3.10.0-478.el7.x86_64 qemu-kvm-rhev-2.6.0-15.el7.x86_64 seabios-1.9.1-4.el7.x86_64 virtio-win-prewhql-0.1-124 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. https://rhn.redhat.com/errata/RHBA-2016-2609.html |