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:
qemu-ga stores the fsfreeze state in /tmp.  For RHEL7, /run would be a better match.

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


How reproducible:


Steps to Reproduce:
1. Run "qemu-ga --help"
  
Actual results:
The default statedir is shown to be /tmp.

Expected results:
The default statedir is shown to be /run.

Additional info:
Upstream we should probably make the default changeable at configure-time, so that the RHEL7 patch would touch the spec file only.

Patches posted upstream and have already been accepted by qemu-ga's maintainer:

https://lists.gnu.org/archive/html/qemu-devel/2012-10/msg00476.html

Merged upstream (commits 785c23ae5c and 6a3c8c14c). To test this, run latest qemu-ga in the guest, freeze the FS and do:

 # ls -la /var/run/ (or /usr/local/var/run)

And check if a file named qga.state.isfrozen has been created.

*** Bug 836275 has been marked as a duplicate of this bug. ***

Verify this bug as follow version:
Host:
# uname -r
3.10.0-79.el7.x86_64
# rpm -q qemu-kvm
qemu-kvm-1.5.3-41.el7.x86_64

Guest:RHEl7

qemu-guest-agent-1.5.3-41.el7.x86_64.rpm 

Steps:
1.# qemu-ga --help
...
  -t, --statedir    specify dir to store state information (absolute paths
                    only, default is /var/run)
...
2.on host
#nc -U /tmp/qga.sock
{"execute":"guest-fsfreeze-freeze" }
{"return": 2}
3. check state file
# ll /var/run/qga.state 
-rw-r--r--. 1 root root 25 Jan 25 22:33 /var/run/qga.state

Results:
After step 1:The Paths is /var/run
After step 3: A file named qga.state.isfrozen has been created.


According to above test ,this bug fixed.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.