Bug 1117055
Summary: | viostor and vioscsi driver for Win8\AMD64 is not properly signed | ||
---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | Cole Robinson <crobinso> |
Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | unspecified | CC: | bcao, crobinso, ghammer, lveyde, rbalakri, skalkoto, virt-bugs, virt-maint, virt-maint, vrozenfe, yvugenfi, zman0900 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1113600 | Environment: | |
Last Closed: | 2015-05-05 19:44:37 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: | |||
Bug Depends On: | 1110129, 1113600 | ||
Bug Blocks: |
Description
Cole Robinson
2014-07-07 21:50:44 UTC
Vadim, just to clarify: given that this is reproducible with RHEL as well, I take that to mean that there's no internal virtio-win build that has this fix? If so I'll just wait for a fixed build and a ping to update the fedora drivers (In reply to Cole Robinson from comment #1) > Vadim, just to clarify: given that this is reproducible with RHEL as well, I > take that to mean that there's no internal virtio-win build that has this > fix? If so I'll just wait for a fixed build and a ping to update the fedora > drivers Thanks Cole, Yes, it's it's a common problem reproducible on both - Fedora and RHEL. I'll try to fix it asap. Vadim. *** Bug 1126912 has been marked as a duplicate of this bug. *** This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22 This should be fixed with the latest public ISOs |