RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2153745 - fwcfg drivers don't seem to work
Summary: fwcfg drivers don't seem to work
Keywords:
Status: CLOSED DUPLICATE of bug 2141876
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virtio-win
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Vadim Rozenfeld
QA Contact: leidwang@redhat.com
URL:
Whiteboard:
Depends On: 2141876
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-15 10:43 UTC by Laszlo Ersek
Modified: 2023-03-30 03:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-26 03:28:22 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2151752 0 medium CLOSED qemufwcfg device cannot start or has no driver after v2v converting windows guests 2023-07-18 08:30:26 UTC
Red Hat Issue Tracker RHELPLAN-142435 0 None None None 2022-12-15 10:44:31 UTC

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 ***
Note You need to log in before you can comment on or make changes to this bug.