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 1957377 - Downstream qemu-ga should report the build number and not QEMU version
Summary: Downstream qemu-ga should report the build number and not QEMU version
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virtio-win
Version: 8.4
Hardware: x86_64
OS: Windows
high
medium
Target Milestone: beta
: 8.5
Assignee: Yvugenfi@redhat.com
QA Contact: dehanmeng
URL:
Whiteboard:
Depends On:
Blocks: 1974317
TreeView+ depends on / blocked
 
Reported: 2021-05-05 17:23 UTC by Arik
Modified: 2024-10-01 18:06 UTC (History)
13 users (show)

Fixed In Version: mingw-qemu-ga-win-102.2.0-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1974317 (view as bug list)
Environment:
Last Closed: 2021-11-09 18:52:47 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2021:4341 0 None None None 2021-11-09 18:53:27 UTC

Description Arik 2021-05-05 17:23:43 UTC 
With virtio-win 1.9.16 we see in agents.json:

{
  "arch": "x86",
  "agent_version": "102.0.0-2",
  "name": "Red Hat QEMU guest agent"
},
{
  "arch": "amd64",
  "agent_version": "102.0.0-2",
  "name": "Red Hat QEMU guest agent"
},

while qemu-ga itself now reports version 5.2.0 (see https://bugzilla.redhat.com/show_bug.cgi?id=1936298#c34).

This makes RHV showing the user that there is an update to qemu-ga although the user uses the latest version.
Comment 1 dehanmeng 2021-05-06 09:18:50 UTC 
Reproduce this issue successfully,

Versions:
virtio-win-prewhql-198.iso
mingw-qemu-ga-win-102.0.0-2.el8

Steps:
1.boot up win2016 guest
2.Connect guest via qga and send qga-cmd 'guest-info' to query qga version
[root@dell-per440-12 kar]# nc -U /tmp/avocado_uaggkdgh/serial-org.qemu.guest_agent.0-20210505-043826-fZOMC62q
{"execute":"guest-info"}
{"return": {"version": "5.2.0", "supported_commands": [{"enabled": true, "name": "guest-get-devices", "success-response": true}, {"enabled": true, "name": "guest-get-osinfo", "success-response": true}, {"enabled": true, "name": "guest-get-timezone", "success-response": true}, {"enabled": true, "name": "guest-get-users", "success-response": true}, {"enabled": true, "name": "guest-get-host-name", "success-response": true}, {"enabled": true, "name": "guest-exec", "success-response": true}, {"enabled": true, "name": "guest-exec-status", "success-response": true}, {"enabled": false, "name": "guest-get-memory-block-info", "success-response": true}, {"enabled": false, "name": "guest-set-memory-blocks", "success-response": true}....
3.Query qga version via cmd:
[root@dell-per440-12 kar]#  cat /usr/share/virtio-win/agents.json
{
  "agents": [
    {
      "arch": "x86",
      "agent_version": "102.0.0-2",
      "name": "Red Hat QEMU guest agent"
    },
    {
      "arch": "amd64",
      "agent_version": "102.0.0-2",
      "name": "Red Hat QEMU guest agent"
    }
Comment 2 dehanmeng 2021-05-06 09:29:05 UTC 
(In reply to dehanmeng from comment #1)
> Reproduce this issue successfully,
> 
> Versions:
> virtio-win-prewhql-198.iso
> mingw-qemu-ga-win-102.0.0-2.el8
> 
> Steps:
> 1.boot up win2016 guest
> 2.Connect guest via qga and send qga-cmd 'guest-info' to query qga version
> [root@dell-per440-12 kar]# nc -U
> /tmp/avocado_uaggkdgh/serial-org.qemu.guest_agent.0-20210505-043826-fZOMC62q
> {"execute":"guest-info"}
> {"return": {"version": "5.2.0", "supported_commands": [{"enabled": true,
> "name": "guest-get-devices", "success-response": true}, {"enabled": true,
> "name": "guest-get-osinfo", "success-response": true}, {"enabled": true,
> "name": "guest-get-timezone", "success-response": true}, {"enabled": true,
> "name": "guest-get-users", "success-response": true}, {"enabled": true,
> "name": "guest-get-host-name", "success-response": true}, {"enabled": true,
> "name": "guest-exec", "success-response": true}, {"enabled": true, "name":
> "guest-exec-status", "success-response": true}, {"enabled": false, "name":
> "guest-get-memory-block-info", "success-response": true}, {"enabled": false,
> "name": "guest-set-memory-blocks", "success-response": true}....
> 3.Query qga version via cmd:
> [root@dell-per440-12 kar]#  cat /usr/share/virtio-win/agents.json
> {
>   "agents": [
>     {
>       "arch": "x86",
>       "agent_version": "102.0.0-2",
>       "name": "Red Hat QEMU guest agent"
>     },
>     {
>       "arch": "amd64",
>       "agent_version": "102.0.0-2",
>       "name": "Red Hat QEMU guest agent"
>     }

virtio-win 1.9.16virtio-win 1.9.16 still hit this issue. and the issue was considered a normal change at first, so this problem was not pointed out.
Comment 3 ali.khalidy 2021-06-02 21:28:48 UTC 
Hello,

can we get an eta for this? We have this exact same issue as well.
Comment 12 Yvugenfi@redhat.com 2021-06-17 11:20:05 UTC 
The fix in mingw-qemu-ga-win-102.4.0-0.el8
Comment 13 dehanmeng 2021-06-18 01:11:09 UTC 
Tried to verify this issue on win2016-64 guest with the fixed build mingw-qemu-ga-win-102.2.0-2.el8, but the issue seems still be there. the version of build still is '5.2'

Actual result.
[root@dell-per440-01 whql_autotest]# nc -U /tmp/avocado_3ysnlr_l/serial-org.qemu.guest_agent.0-20210607-121055-kSowKNHY
{"execute":"guest-info"}
{"return": {"version": "5.2.0", "supported_commands": [{"enabled": true, "name": "guest-get-devices", "success-response": true},...........}
Comment 14 dehanmeng 2021-06-18 01:45:39 UTC 
Sorry about the last comment, I reuse the latest version of qemu-ga build. and try to verify it again. now the result is correct.

Verify steps as comment.

Actual result:
[root@dell-per440-01 Verify_bug]# nc -U /tmp/avocado_3ysnlr_l/serial-org.qemu.guest_agent.0-20210607-121055-kSowKNHY
{"execute":"guest-info"}
{"return": {"version": "102.4.0", "supported_commands"........} 
Expected result:
{"return": {"version": "102.4.0", "supported_commands"........} 


Thanks for your effort Yan, This issue is gone.
Comment 21 errata-xmlrpc 2021-11-09 18:52:47 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 (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:4341
Note You need to log in before you can comment on or make changes to this bug.