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.

Description of problem:
We found that all win10+ guests can not get virtio-fs drivers from windows update, other drivers work well.
The only difference between virtio-fs and others is that the viofs hardware id is not consistent.

Version-Release number of selected component (if applicable):
virtio-win-prewhql-191

How reproducible:
100%

Steps to Reproduce:
1. boot win10-32 guest with virtio-fs device
2. check hardware id via device manager
3. check hardware id in viofs.inf file

Actual results:
hardware id in step 2 and step 3 are not same:
.inf file:      PCI\VEN_1AF4&DEV_105A&SUBSYS_00041AF4
device manager: PCI\VEN_1AF4&DEV_105A&SUBSYS_110041AF4(screenshot attached)

Expected results:
hardware id in step 2 and step 3 should be same

Additional info:
1. This issue could be the root cause for "win10+ guest can not get viofs drivers from windows update"
2. 189 can also reproduce, so not regression

Created attachment 1745248 [details]
hardware id in guest device manager

Updated the device's sub system id: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/547

reproduce this issue on virtio-win-prewhql-191

Verified with virtio-win-prewhql-195

check hardware id is PCI\VEN_1AF4&DEV_105A&SUBSYS_11001AF4&REV_00 in viofs.inf file,  can match the hardware id in device manger.

So this issue is fixed, change status to verified.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (virtio-win bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2021:1959