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.
Description of problem:
On windows 11, guest agent reports incorrect data
Version-Release number of selected component (if applicable):
4.11
How reproducible:
100%
Steps to Reproduce:
1.Create windows 11 vm
2.Install qemu guest agent
3.Check data with virtctl guestosinfo or oc describe vmi
Actual results:
Tried 2 with different qemu-ga versions:
QEMU-GA 102.7.0:
Guest OS Info:
Id: mswindows
Kernel Release: 22000
Kernel Version: 10.0
Name: Microsoft Windows
Pretty Name: Windows 10 Enterprise
Version: 10
Version Id: 10
QEMU-GA 103.0.0:
Guest OS Info:
Id: mswindows
Kernel Release: 22000
Kernel Version: 10.0
Name: Microsoft Windows
Pretty Name: Windows 10 Enterprise
Version: 11
Version Id: 11
Expected results:
Both versions should show Pretty Name: Windows 11 Enterprise
On 102.0.7 Version and Version Id should be 11
Additional info:
This BZ was re-assigned to the Guest Agent component because we think that's where this information was coming from. Feel free to re-assign if you believe this was in error.
Moving this to RHEL9 and virtio-win/qemu-ga-win since that's where a fix would have start, then the bz could be cloned to RHEL8 (please don't clone yet though).
Comment 4Kostiantyn Kostiuk
2022-06-14 09:47:48 UTC
The guest agent returns only the proper "version" and "version-id" for Windows 11.
The "pretty-name" is read from the registry and will be incorrect until the
MS updates the registry. We do not have any solution to get "pretty-name" without
localization and with a proper Windows number.
Comment 6Yvugenfi@redhat.com
2022-06-16 08:24:53 UTC
Description of problem: On windows 11, guest agent reports incorrect data Version-Release number of selected component (if applicable): 4.11 How reproducible: 100% Steps to Reproduce: 1.Create windows 11 vm 2.Install qemu guest agent 3.Check data with virtctl guestosinfo or oc describe vmi Actual results: Tried 2 with different qemu-ga versions: QEMU-GA 102.7.0: Guest OS Info: Id: mswindows Kernel Release: 22000 Kernel Version: 10.0 Name: Microsoft Windows Pretty Name: Windows 10 Enterprise Version: 10 Version Id: 10 QEMU-GA 103.0.0: Guest OS Info: Id: mswindows Kernel Release: 22000 Kernel Version: 10.0 Name: Microsoft Windows Pretty Name: Windows 10 Enterprise Version: 11 Version Id: 11 Expected results: Both versions should show Pretty Name: Windows 11 Enterprise On 102.0.7 Version and Version Id should be 11 Additional info: