Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1979469

Summary: [virtio-win][viofs] virtio-fs hardware id is not consistent with guest device manager
Product: Red Hat Enterprise Linux 8 Reporter: menli <menli>
Component: virtio-winAssignee: Virtualization Maintenance <virt-maint>
virtio-win sub component: virtio-win-prewhql QA Contact: xiagao
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: high    
Priority: high CC: coli, lijin, mdean, vrozenfe, xiagao
Version: 8.5Keywords: Triaged
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: x86_64   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1913664 Environment:
Last Closed: 2021-12-16 11:54:57 UTC Type: ---
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: 1913664    
Bug Blocks:    

Comment 3 menli@redhat.com 2021-07-06 07:15:45 UTC 
check with virtio-win-prewhql-195

check hardware id is PCI\VEN_1AF4&DEV_105A&SUBSYS_11001AF4&REV_00 in viofs.inf file, last digital not match that(REV_01) in device manager.
That should be the reason why we can not update viofs driver from windows update.
Comment 4 menli@redhat.com 2021-07-06 07:31:15 UTC 
(In reply to menli from comment #3)
> check with virtio-win-prewhql-195
> 
> check hardware id is PCI\VEN_1AF4&DEV_105A&SUBSYS_11001AF4&REV_00 in
> viofs.inf file, last digital not match that(REV_01) in device manager.
> That should be the reason why we can not update viofs driver from windows
> update.

hardware id:
.inf file:      PCI\VEN_1AF4&DEV_105A&SUBSYS_11001AF4&REV_00
device manager: PCI\VEN_1AF4&DEV_105A&SUBSYS_11001AF4&REV_01
Comment 5 xiagao 2021-07-13 01:22:40 UTC 
Hi Meirav,
Can we fix this bz in RHEL8.5.0, as it will make windows update failed.

Thanks,
Xiaoling
Comment 6 Gal Hammer 2021-07-20 09:02:48 UTC 
https://github.com/virtio-win/kvm-guest-drivers-windows/pull/605
Comment 7 xiagao 2021-07-27 03:19:27 UTC 
Check viofs.inf file for win10+ in virtio-win-prewhql-205,get device id is as below.
# cat viofs.inf  |grep 'PCI\\VEN_1AF4&DEV_105A&SUBSYS'
%VirtioFs.DeviceDesc% = VirtioFs_Device, PCI\VEN_1AF4&DEV_105A&SUBSYS_11001AF4&REV_01, PCI\VEN_1AF4&DEV_105A


Device id in guest device manager is as below.
PCI\VEN_1AF4&DEV_105A&SUBSYS_11001AF4&REV_01


The device ID is the same.So verify it with 205 version.