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 1972070 - Add Windows Server 2022 version support for mingw-qemu-ga
Summary: Add Windows Server 2022 version support for mingw-qemu-ga
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virtio-win
Version: 9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 9.0
Assignee: Yvugenfi@redhat.com
QA Contact: dehanmeng
URL:
Whiteboard:
: 1998845 (view as bug list)
Depends On: 1992643
Blocks: 1998845
TreeView+ depends on / blocked
 
Reported: 2021-06-15 08:10 UTC by dehanmeng
Modified: 2023-03-14 15:12 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1998845 (view as bug list)
Environment:
Last Closed: 2022-11-15 06:47:44 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description dehanmeng 2021-06-15 08:10:34 UTC 
Description of problem:
test qga on guest win2022-64 for getting osinfo, but the version of guest is different between guest and qga 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.bootup win2022 guest 
2.send qga command 
{"execute": "guest-get-osinfo"}
{"return": {"name": "Microsoft Windows", "kernel-release": "20344", "version": "N/A", "variant": "server", "pretty-name": "Windows Server 2022 Datacenter", "version-id": "N/A", "variant-id": "server", "kernel-version": "10.0", "machine": "x86_64", "id": "mswindows"}}

Actual results:
"version": "N/A"

Expected results:
version should be "2022"

Additional info:
Comment 2 dehanmeng 2021-06-22 08:48:21 UTC 
Hi all,
Verify it with the latest version of qemu-ga mingw-qemu-ga-win-102.5.0-0.el8

1. bootup win2022 guest.
2. send qga command to check the version of windows:
[root@dell-per440-12 1934492]# nc -U /tmp/avocado_q5dckrpu/serial-org.qemu.guest_agent.0-20210621-001149-sbtfzkAa
{"execute":"guest-get-osinfo"}
{"return": {"name": "Microsoft Windows", "kernel-release": "20344", "version": "Microsoft Windows Server 2022", "variant": "server", "pretty-name": "Windows Server 2022 Datacenter", "version-id": "2022", "variant-id": "server", "kernel-version": "10.0", "machine": "x86_64", "id": "mswindows"}}

Actual result:
return the correct windows version that is "Microsoft Windows Server 2022"

Expected result:
as above.

This issue is gone, thanks for your effort Yan.
Thanks
Dehan Meng
Comment 3 dehanmeng 2021-08-30 01:33:56 UTC 
*** Bug 1998845 has been marked as a duplicate of this bug. ***
Comment 4 dehanmeng 2021-08-30 01:35:30 UTC 
Hit this issue again on win2022 with version mingw-qemu-ga-win-102.7.0-0.el8

Steps to Reproduce:
1.bootup win2022 guest 
2.send qga command 
{"execute": "guest-get-osinfo"}
{"return": {"name": "Microsoft Windows", "kernel-release": "20348", "version": "N/A", "variant": "server", "pretty-name": "Windows Server 2022 Datacenter", "version-id": "N/A", "variant-id": "server", "kernel-version": "10.0", "machine": "x86_64", "id": "mswindows"}}

Actual results:
"version": "N/A"

Expected results:
version should be "2022"
Comment 8 Yvugenfi@redhat.com 2021-08-30 07:53:02 UTC 
(In reply to dehanmeng from comment #4)
> Hit this issue again on win2022 with version mingw-qemu-ga-win-102.7.0-0.el8
> 
> Steps to Reproduce:
> 1.bootup win2022 guest 
> 2.send qga command 
> {"execute": "guest-get-osinfo"}
> {"return": {"name": "Microsoft Windows", "kernel-release": "20348",
> "version": "N/A", "variant": "server", "pretty-name": "Windows Server 2022
> Datacenter", "version-id": "N/A", "variant-id": "server", "kernel-version":
> "10.0", "machine": "x86_64", "id": "mswindows"}}
> 
> Actual results:
> "version": "N/A"
> 
> Expected results:
> version should be "2022"

Is this is newer release of Windows Server 2022?
Comment 10 dehanmeng 2021-08-31 07:58:31 UTC 
(In reply to Yvugenfi from comment #8)
> (In reply to dehanmeng from comment #4)
> > Hit this issue again on win2022 with version mingw-qemu-ga-win-102.7.0-0.el8
> > 
> > Steps to Reproduce:
> > 1.bootup win2022 guest 
> > 2.send qga command 
> > {"execute": "guest-get-osinfo"}
> > {"return": {"name": "Microsoft Windows", "kernel-release": "20348",
> > "version": "N/A", "variant": "server", "pretty-name": "Windows Server 2022
> > Datacenter", "version-id": "N/A", "variant-id": "server", "kernel-version":
> > "10.0", "machine": "x86_64", "id": "mswindows"}}
> > 
> > Actual results:
> > "version": "N/A"
> > 
> > Expected results:
> > version should be "2022"
> 
> Is this is newer release of Windows Server 2022?

yes, as you said, that's a newer release of Win2022
Comment 16 John Ferlan 2021-11-17 15:05:36 UTC 
Updated the ITR=9.0.0 since bug moved to RHEL9, removed ZTR, DTM, and ITM values as well as the Fixed in Version value.

If there needs to be a RHEL8 specific bug, then clone to RHEL8
Comment 18 dehanmeng 2021-12-24 03:46:09 UTC 
presently, I tested qga with mingw-qemu-ga-win-102.8.0-0.el8_5,
win-server 2022 can be return in output from command guest-get-osinfo

[root@dell-per730-56 ~]# nc -U /tmp/avocado_ueferioi/serial-org.qemu.guest_agent.0-20211223-121136-55o4p0NQ
{"execute": "guest-get-osinfo"}
{"return": {"name": "Microsoft Windows", "kernel-release": "20348", "version": "Microsoft Windows Server 2022", "variant": "server", "pretty-name": "Windows Server 2022 Datacenter", "version-id": "2022", "variant-id": "server", "kernel-version": "10.0", "machine": "x86_64", "id": "mswindows"}}
so whether this issue has been fixed already ? and Shall we move the status to ON_QA then? if I miss anything and got wrong judgment， please point me out,appreciate it.
Comment 19 Yvugenfi@redhat.com 2021-12-26 22:48:38 UTC 
Nothing changed from https://bugzilla.redhat.com/show_bug.cgi?id=2029674 and it is the same mingw-qemu-ga-win-102.8.0-0.el8_5

How does Avocado execute qemu-ga? Is it a service?

The bug in BZ#2029674 appears depending on the location of the executed qemu-ga.
Comment 20 dehanmeng 2021-12-27 04:01:03 UTC 
(In reply to Yvugenfi from comment #19)
> Nothing changed from https://bugzilla.redhat.com/show_bug.cgi?id=2029674 and
> it is the same mingw-qemu-ga-win-102.8.0-0.el8_5
> 
> How does Avocado execute qemu-ga? Is it a service?
> 
not exactly, avocado just install the qemu-ga.msi and the Qemu guest agent run as default. It doesn't run in cmd like "C:\program Files \Qemu-ga>qemu-ga.exe".
> The bug in BZ#2029674 appears depending on the location of the executed
> qemu-ga.
Comment 21 dehanmeng 2022-01-18 08:20:37 UTC 
Hi Yan, 
For now, this issue isn't hit any more with the latest version of qemu-ga mingw-qemu-ga-win-102.10.0-0.el8_5, the output of command "guest-get-osinfo" as following:

{"execute": "guest-get-osinfo"}
{"return": {"name": "Microsoft Windows", "kernel-release": "20348", "version": "Microsoft Windows Server 2022", "variant": "server", "pretty-name": "Windows Server 2022 Datacenter", "version-id": "2022", "variant-id": "server", "kernel-version": "10.0", "machine": "x86_64", "id": "mswindows"}}

as we can see that the "version"/"version-id" fields are corresponding the correct content, and this situation are the same when I run qemu-ga via two methods. so what's your opinion on it? 

Thanks
Dehan Meng
Comment 22 Yvugenfi@redhat.com 2022-01-18 09:09:07 UTC 
(In reply to dehanmeng from comment #21)
> Hi Yan, 
> For now, this issue isn't hit any more with the latest version of qemu-ga
> mingw-qemu-ga-win-102.10.0-0.el8_5, the output of command "guest-get-osinfo"
> as following:
> 
> {"execute": "guest-get-osinfo"}
> {"return": {"name": "Microsoft Windows", "kernel-release": "20348",
> "version": "Microsoft Windows Server 2022", "variant": "server",
> "pretty-name": "Windows Server 2022 Datacenter", "version-id": "2022",
> "variant-id": "server", "kernel-version": "10.0", "machine": "x86_64", "id":
> "mswindows"}}
> 
> as we can see that the "version"/"version-id" fields are corresponding the
> correct content, and this situation are the same when I run qemu-ga via two
> methods. so what's your opinion on it? 
> 
> Thanks
> Dehan Meng

Hi Dehan,

This bug is for RHEL9. As RHEL 9 is released from Centos stream, we should keep this bug.

Best regards,
Yan.
Comment 23 Qianqian Zhu 2022-01-18 09:43:04 UTC 
Removing its block to bz 1968312 per comment 22.
Comment 28 dehanmeng 2022-03-23 14:21:59 UTC 
because of the latest mingw-qemu-ga-win mingw-qemu-ga-win-103.0.0-1.el9_0 has been approved to add into RHEL9/centos stream. and this issue had been fixed earlier and test result as following:

2022-03-19 06:28:50: {"execute": "guest-get-osinfo"}
2022-03-19 06:28:50: {"return": {"name": "Microsoft Windows", "kernel-release": "20348", "version": "Microsoft Windows Server 2022", "variant": "server", "pretty-name": "Windows Server 2022 Datacenter", "version-id": "2022", "variant-id": "server", "kernel-version": "10.0", "machine": "x86_64", "id": "mswindows"}}

so move this bug to VERIFIED.
Note You need to log in before you can comment on or make changes to this bug.