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 1998933

Summary: The devices info 'driver-date' is not correct on win11
Product: Red Hat Enterprise Linux 9 Reporter: dehanmeng <demeng>
Component: virtio-winAssignee: Kostiantyn Kostiuk <kkostiuk>
virtio-win sub component: qemu-ga-win QA Contact: dehanmeng <demeng>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: jinzhao, juzhang, kkostiuk, lijin, pvlasin, qizhu, yvugenfi
Version: 9.0Keywords: Triaged
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 9.0   
Hardware: x86_64   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2060770 (view as bug list) Environment:
Last Closed: 2022-05-17 15:35:26 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: 1992643, 2061158    
Bug Blocks: 2060770    

Description dehanmeng 2021-08-30 03:40:41 UTC
Description of issues:
Info 'driver-date' of device 'virtio scsi' in guest is not correct: Month and day reversed so that the driver-date from guest is different from qga command.
 

Version-Release number of selected component (if applicable):
seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch
kernel-4.18.0-335.el8.x86_64
qemu-kvm-6.0.0-29.module+el8.5.0+12386+43574bac.x86_64
virtio-win-prewhql-0.1-207.iso
mingw-qemu-ga-win-102.7.0-0.el8

How reproducible:
100%

Steps to Reproduce:
1. bootup win11 guest
2. open 'device manager' and check virtio scsi's driver-date


Actual results:
the driver-date is 05/08/2021
Expected results:
the driver-date shoud be 08/05/2021
Additional info:

Comment 1 Yvugenfi@redhat.com 2021-08-30 08:07:21 UTC
What is the locale selected on the guest? Is it the USA with mm/dd/yyyy date format?

Comment 2 dehanmeng 2021-08-30 08:31:39 UTC
(In reply to Yvugenfi from comment #1)
> What is the locale selected on the guest? Is it the USA with mm/dd/yyyy date
> format?

win11 don't set a default regional format right? but actually you reminded me correctly, after setting a USA region, there are two situation: 
1. when you check via GUI. date format as normal definitely
2. but when I want to check it via cmd: powershell -command "Get-WmiObject Win32_PnPSignedDriver -Filter \"devicename = 'Red Hat VirtIO SCSI pass-through controller'\" | select devicename, driverversion, driverdate, deviceid, friendlyname", the DriverDate was still wrong format. do you know how to change it or whether it's a bug? 
DeviceID                : PCI\VEN_1AF4&DEV_1048&SUBSYS_11001AF4&REV_01\4&24F6AFB5&0&000B
DeviceName              : Red Hat VirtIO SCSI pass-through controller
DevLoader               :
DriverDate              : 20210508000000.******+***
DriverName              :
DriverProviderName      : Red Hat, Inc.
DriverVersion           : 100.85.104.20700

Comment 3 Yvugenfi@redhat.com 2021-09-09 07:58:10 UTC
BTW: What qemu-ga command you used and got wrong date?

Comment 4 dehanmeng 2021-09-09 14:24:31 UTC
(In reply to Yvugenfi from comment #3)
> BTW: What qemu-ga command you used and got wrong date?

Sending command 'guest-get-devices'

Comment 5 Yvugenfi@redhat.com 2021-09-19 12:19:39 UTC
(In reply to dehanmeng from comment #4)
> (In reply to Yvugenfi from comment #3)
> > BTW: What qemu-ga command you used and got wrong date?
> 
> Sending command 'guest-get-devices'

Can you please post a full response to "'guest-get-devices'"?

From qemu 5.2 the returned value for the date is a timestamp and not a date string.

Comment 7 dehanmeng 2022-02-07 03:30:14 UTC
Hi 
For QE perspective, we want to get the build ITM 24 so that QE can have a buffer to verify it and we can handle it if there have regression. anyway, I've set ITM to 26. by the way, after ITM26, all bz should be have exception+/blocker+. 

Thanks

Comment 8 Yvugenfi@redhat.com 2022-02-12 17:10:03 UTC
(In reply to dehanmeng from comment #7)
> Hi 
> For QE perspective, we want to get the build ITM 24 so that QE can have a
> buffer to verify it and we can handle it if there have regression. anyway,
> I've set ITM to 26. by the way, after ITM26, all bz should be have
> exception+/blocker+. 
> 
> Thanks

We are in progress of building a new build for CentOS Stream\RHEL9

Comment 16 Yvugenfi@redhat.com 2022-03-16 10:12:33 UTC
The fix is in the build: mingw-qemu-ga-win-103.0.0-1.el9_0

Comment 17 dehanmeng 2022-03-18 01:31:45 UTC
work for me now. (win11 iso: en-us_windows_11_business_editions_x64_dvd_3a304c08.iso)

Comment 20 errata-xmlrpc 2022-05-17 15:35:26 UTC
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 (new packages: virtio-win), 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/RHBA-2022:3890