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.

Bug 1972052

Summary: Improve error message when 'guest-fsfreeze-freeze' is issued twice[windows]
Product: Red Hat Enterprise Linux 8 Reporter: dehanmeng <demeng>
Component: virtio-winAssignee: Kostiantyn Kostiuk <kkostiuk>
virtio-win sub component: qemu-ga-win QA Contact: dehanmeng <demeng>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: unspecified    
Priority: medium CC: jinzhao, lijin, virt-maint, yvugenfi
Version: 8.5Keywords: Triaged
Target Milestone: betaFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: mingw-qemu-ga-win-102.10.0-0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1928806 Environment:
Last Closed: 2022-05-16 09:43:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1928806    
Bug Blocks:    

Comment 6 dehanmeng 2021-10-25 01:08:50 UTC 
Hi Yan, could you please set a appropriate DTM? thanks.
Comment 9 dehanmeng 2022-02-07 04:15:00 UTC 
Reproduce this issue with  mingw-qemu-ga-win-102.7.0-0
Steps:
1. boot up windows server 2019 VM
2. Install mingw-qemu-ga-win-102.7.0-0
3. Connect guest on host via:
[root@dell-per440-12 ~]# nc -U /tmp/avocado_wc5y71da/serial-org.qemu.guest_agent.0-20211228-054849-f1g7U4Qy
4. send freeze command twice:

Actual result:
{"execute":"guest-fsfreeze-freeze"}
{"return": 2}
{"execute":"guest-fsfreeze-freeze"}
{"error": {"class": "CommandNotFound", "desc": "The command guest-fsfreeze-freeze has been disabled for this instance"}}

Expected result:
{"execute":"guest-fsfreeze-freeze"}
{"error": {"class": "CommandNotFound", "desc": "Command guest-fsfreeze-freeze has been disabled: the agent is in frozen state"}}


Verify this issue with mingw-qemu-ga-win-102.10.0-0
steps as above

Actual result:
{"execute":"guest-fsfreeze-freeze"}
{"return": 2}
{"execute":"guest-fsfreeze-freeze"}
{"error": {"class": "CommandNotFound", "desc": "Command guest-fsfreeze-freeze has been disabled: the agent is in frozen state"}}

Expected result:
as above