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:
this issue on guest rhel840 with qemu-kvm-4.2.0-38.module+el8.4.0+9133+5346b06d. it's the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=1738820#c0, but it was fixed in rhel830-av and solution as https://bugzilla.redhat.com/show_bug.cgi?id=1738820#c5.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

Reproduce with version :
qemu-kvm-4.2.0-38.module+el8.4.0+9133+5346b06d
RHEL-8.4.0-20201229.n.0 BaseOS x86_64

Steps to Reproduce：
1.Boot rhel840 guest successfully.
2.Check whether there is /etc/qemu-kvm/fsfreeze-hook

Actual result:
There is no /etc/qemu-kvm/fsfreeze-hook in guest, and cannot freeze filesystem from guest.
Expected result:
There are /etc/qemu-kvm/fsfreeze-hook and /etc/qemu-ga/fsfreeze-hook. And can freeze fs successfully.

Verified with version:
qemu-kvm-4.2.0-40.module+el8.4.0+9278+dd53883d
RHEL-8.4.0-20201229.n.0 BaseOS x86_64

Steps to verify like above
As above
Actual result:
There are /etc/qemu-kvm/fsfreeze-hook and /etc/qemu-ga/fsfreeze-hook. And can freeze fs successfully.
Expected result:
There are /etc/qemu-kvm/fsfreeze-hook and /etc/qemu-ga/fsfreeze-hook. And can freeze fs successfully.

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 (Moderate: virt:rhel and virt-devel:rhel security, 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/RHSA-2021:1762