Bug 2153745

Summary:	fwcfg drivers don't seem to work
Product:	Red Hat Enterprise Linux 9	Reporter:	Laszlo Ersek <lersek>
Component:	virtio-win	Assignee:	Vadim Rozenfeld <vrozenfe>
virtio-win sub component:	distribution	QA Contact:	leidwang <leidwang>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	coli, jinzhao, juzhang, qizhu
Version:	9.1
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-12-26 03:28:22 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:	2141876
Bug Blocks:

Description Laszlo Ersek 2022-12-15 10:43:31 UTC

* Description of problem:
Neither the qemufwcfg (stub) driver nor the fwcfg (complete) driver seems to work.

* Version-Release number of selected component (if applicable):
virtio-win-1.9.30-0.el9_1.noarch

* Steps to Reproduce:
1. Install Windows 2019 guest (en-us_windows_server_2019_updated_aug_2021_x64_dvd_a6431a28.iso) on QEMU/KVM/libvirt

2. From the virtio-win ISO, locate either the qemufwcfg (stub) driver's INF file, or the fwcfg (complete) driver's INF file.

3. Right click; pick Install.

4. Go to Device Manager, View | Show hidden devices, investigate the QEMU FWCfg/FwCfg device's status under System devices. (Different "w" spellings in the different drivers.)

* Actual results:

- the qemufwcfg driver does not cause an exclamation mark to appear over the device's icon, but the properties dialog says "No drivers are installed for this
  device"

- the fwcfg driver triggers an exclamation mark, and the properties dialog says "This device cannot start. (Code 10) Bad data"

* Expected results:

Presumably, with both drivers, the Properties dialog should report something like "this device is operating properly".

* Additional info:
- Bug report extracted from findings under bug 2151752.
- Seems reproducible with Windows 2022 and Win11 as well.

Comment 3 Qianqian Zhu 2022-12-26 03:28:22 UTC

Hi Laszlo,

I believe this issue will be fixed once bz 2141876 was fixed, and once fwcfg is supported qemufwcfg is useless. So I am closing this as duplicated with bz 2141876.

*** This bug has been marked as a duplicate of bug 2141876 ***