Bug 1743480
| Summary: | Getting (code 52) on Virtio Ethernet drive, windows 10 host. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Community] Virtualization Tools | Reporter: | Oz Dror <odror7> | ||||
| Component: | virtio-win | Assignee: | Amnon Ilan <ailan> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | unspecified | CC: | ghammer, haoliu, lijin, virt-maint, vrozenfe, yvugenfi | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Windows | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-12-30 11:03:17 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: | 1376048 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
Hi, Do you have secure boot enabled? Thanks, Yan. Yes secure boot is enabled So where do you find the RHEL WHQL virtio drivers I have disabled secure boot, and now it is working. The problem is that I need to have secure boot this w10 machine is for work. Without secure boot I might not be able to use it. Thanks This is a dup of bz1666705, if secure boot is enabled, msft signed drivers are required. For redhat customers, they can get the whql signed drivers via redhat subscription. For upstream users, "disable the driver verification" could be a workaround. Yan, what's your opinion? (In reply to lijin from comment #6) > This is a dup of bz1666705, if secure boot is enabled, msft signed drivers > are required. > > For redhat customers, they can get the whql signed drivers via redhat > subscription. > For upstream users, "disable the driver verification" could be a workaround. > > Yan, what's your opinion? We are discussing internally the option to provide upstream users with attestation signed drivers. When should I check if it becomes available. Thanks Oz, I suggest to be in touch towards beginning of September regarding the decisions. Hi any news regarding the availability of whql virtio driver. Thanks Hi any news regarding the availability of whql virtio driver. Thanks (In reply to Oz Dror from comment #11) > Hi any news regarding the availability of whql virtio driver. Thanks We will not provide the attestation signed drivers upstream in the near future Are you a Red Hat customer? then you can get the whqled drivers. Otherwise, you can try to whql the drivers with MSFT on your own (with your device ids) Closing as wontfix. Feel free to comment |
Created attachment 1605968 [details] Log file Description of problem: When using OVMF guest BIOS, The Virtio Ethernet driver and other drivers including the balloon and the Serial driver failed to be activate at boot because Windows cannot verify the Driver signatures (code 52) The issue does not occurs with no OVMF bios. Version-Release number of selected component (if applicable): Windows 10 version: Windows 10 pro 1903 Host OS: Ubuntu 19.10 Qemu version: 3.1.0 Virtio-win version: 0.1.171 How reproducible: Every time. If I disable the driver verification in windows 10. the issue goes away.