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.
After sanity test for this fix mingw-qemu-ga-win-102.0.3-0.el8_4 on win2016-64(q35), that fix works well and I run the following command lines that are included by default on RHV:
_QEMU_ACTIVE_USERS_COMMAND = 'guest-get-users'
_QEMU_DEVICES_COMMAND = 'guest-get-devices'
_QEMU_GUEST_INFO_COMMAND = 'guest-info'
_QEMU_HOST_NAME_COMMAND = 'guest-get-host-name'
_QEMU_NETWORK_INTERFACES_COMMAND = 'guest-network-get-interfaces'
_QEMU_OSINFO_COMMAND = 'guest-get-osinfo'
_QEMU_TIMEZONE_COMMAND = 'guest-get-timezone'
_QEMU_FSINFO_COMMAND = 'guest-get-fsinfo'
_QEMU_DISKS_COMMAND = 'guest-get-disks'
This fix package mingw-qemu-ga-win-102.0.3-0.el8_4 works well from QE side.
Reproduce this issue with the last qga version mingw-qemu-ga-win-102.0.0-2.el8, steps to reproduce : 1. bootup win2016 guest and install qga: 2. connect qga. 3. run following command in terminal (host). [root@dell-per440-01 ~]#cat <(for i in {1..1000}; do echo '{"execute":"guest-get-osinfo"}'; sleep 2; echo '{"execute":"guest-get-devices"}'; sleep 2; done) | nc -U /tmp/qga.sock > log 4. while check the handles of QEMU-ga and memory in a loop with following command (guest): Run powershell and execute following command to check memory. PS C:\Users\Administrator> while(1) { Get-Process -ProcessName qemu-ga; sleep 5 } Handles NPM(K) PM(K) WS(K) CPU(s) Id SI ProcessName ------- ------ ----- ----- ------ -- -- ----------- 143 13 1764 8340 0.02 1132 0 qemu-ga 152 14 2044 9176 0.05 1132 0 qemu-ga 152 14 2108 9240 0.06 1132 0 qemu-ga 152 14 2288 9436 0.20 1132 0 qemu-ga 152 14 2328 9492 0.22 1132 0 qemu-ga 152 14 2992 10116 0.67 1132 0 qemu-ga 152 14 3000 10112 0.69 1132 0 qemu-ga 152 14 3108 10136 0.70 1132 0 qemu-ga ... ... 152 14 3472 10572 1.03 1132 0 qemu-ga 152 14 3472 10572 1.05 1132 0 qemu-ga ... ... 152 14 3748 10836 1.14 1132 0 qemu-ga 152 14 3752 10840 1.17 1132 0 qemu-ga 152 14 4048 11112 1.47 1132 0 qemu-ga Actual result: Memory keep raising up. Expected result: Memory should maintain a safety range and floating in that range. Verify this issue with the latest qga version mingw-qemu-ga-win-102.0.1-2.el8_4 steps to verify as above: Actual result: PS C:\Users\Administrator> while(1) { Get-process -processname qemu-ga; sleep 5 } Handles NPM(K) PM(K) WS(K) CPU(s) Id SI ProcessName ------- ------ ----- ----- ------ -- -- ----------- 143 9 1840 8380 0.03 3996 0 qemu-ga 152 14 2068 9192 0.05 3996 0 qemu-ga 152 14 2052 9196 0.08 3996 0 qemu-ga 152 14 2052 9196 0.11 3996 0 qemu-ga 152 14 2040 9200 0.14 3996 0 qemu-ga 152 14 2040 9200 0.16 3996 0 qemu-ga 152 14 2040 9200 0.19 3996 0 qemu-ga 152 14 2040 9200 0.20 3996 0 qemu-ga 152 14 2040 9200 0.22 3996 0 qemu-ga 152 13 1976 9168 0.23 3996 0 qemu-ga 152 13 2000 9180 0.27 3996 0 qemu-ga 152 13 1980 9172 0.28 3996 0 qemu-ga 152 13 1988 9180 0.30 3996 0 qemu-ga 152 13 1988 9180 0.31 3996 0 qemu-ga 152 13 1988 9180 0.34 3996 0 qemu-ga 152 14 2052 9220 0.36 3996 0 qemu-ga 152 14 2056 9224 0.38 3996 0 qemu-ga 152 14 2056 9224 0.39 3996 0 qemu-ga 152 14 2056 9224 0.42 3996 0 qemu-ga 152 14 2056 9224 0.44 3996 0 qemu-ga 152 14 2056 9224 0.45 3996 0 qemu-ga 152 14 2056 9224 0.47 3996 0 qemu-ga 152 14 2056 9224 0.50 3996 0 qemu-ga 152 14 2056 9224 0.52 3996 0 qemu-ga 152 14 2060 9228 0.53 3996 0 qemu-ga 152 14 2132 9292 0.55 3996 0 qemu-ga 152 14 2132 9292 0.58 3996 0 qemu-ga 152 14 2132 9292 0.59 3996 0 qemu-ga 152 14 2132 9292 0.61 3996 0 qemu-ga 152 14 2132 9292 0.63 3996 0 qemu-ga 152 14 2156 9292 0.67 3996 0 qemu-ga 152 14 2136 9296 0.69 3996 0 qemu-ga 152 14 2140 9300 0.70 3996 0 qemu-ga 152 14 2152 9300 0.72 3996 0 qemu-ga 152 14 2136 9296 0.75 3996 0 qemu-ga 152 14 2136 9296 0.77 3996 0 qemu-ga 152 14 2212 9300 0.78 3996 0 qemu-ga 152 14 2244 9336 0.80 3996 0 qemu-ga 152 14 2136 9296 0.83 3996 0 qemu-ga 152 14 2132 9292 0.84 3996 0 qemu-ga 152 14 2132 9292 0.86 3996 0 qemu-ga 152 14 2244 9344 0.88 3996 0 qemu-ga 152 14 2136 9296 0.91 3996 0 qemu-ga 152 14 2212 9300 0.92 3996 0 qemu-ga Expected result: Memory should maintain a safety range and floating in that range.