Bug 1578775 - [RFE] Add qemufwcfg driver in windows guest tools
Summary: [RFE] Add qemufwcfg driver in windows guest tools
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-guest-tools
Classification: oVirt
Component: VirtIO-Drivers
Version: ---
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ovirt-4.3.0
: ---
Assignee: Sandro Bonazzola
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks: 1488425 1667515
TreeView+ depends on / blocked
 
Reported: 2018-05-16 11:44 UTC by Sandro Bonazzola
Modified: 2019-04-28 10:45 UTC (History)
5 users (show)

Fixed In Version: ovirt-wgt-4.3-1
Doc Type: Enhancement
Doc Text:
The qemufwcfg driver has been added for the built-in firmware configuration (fw_cfg) system device on Windows 10 and Windows Server 2016 guests. As a result, fw_cfg devices are now identified correctly in the Device Manager on these guests.
Clone Of:
: 1667515 (view as bug list)
Environment:
Last Closed: 2019-02-13 07:42:57 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.3?
rule-engine: planning_ack?
sbonazzo: devel_ack+
lsvaty: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 96388 0 master MERGED virtio: install qemufwcfg driver 2020-10-20 14:21:53 UTC

Description Sandro Bonazzola 2018-05-16 11:44:06 UTC 
* qemufwcfg - for the built-in system FW Cfg device on
Windows 10 and Windows Server 2016. The driver has no functionality,
it only prevents an unrecognized device from showing in Device
Manager.
Comment 2 Petr Matyáš 2019-01-25 13:04:12 UTC 
Verified on ovirt-guest-tools-iso-4.3-0.20181221172138.git3698ef0.el7.noarch.rpm
Comment 5 Sandro Bonazzola 2019-02-13 07:42:57 UTC 
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.