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 975376 - virsh setmem then dompmsuspend to disk will hang forever
Summary: virsh setmem then dompmsuspend to disk will hang forever
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 878966
Blocks: Virt-S3/S4-7.0
TreeView+ depends on / blocked
 
Reported: 2013-06-18 10:00 UTC by Jincheng Miao
Modified: 2016-04-26 14:58 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 878966
Environment:
Last Closed: 2015-03-05 14:57:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 2 Jincheng Miao 2013-06-19 03:38:15 UTC 
This bug cannot be reproduced again after I update qemu-kvm-1.4.0-3.el7 to qemu-kvm-1.5.0-2.el7. And downgrade the qemu-kvm also will not reproduce it.

the steps like:
1.
# virsh start r7
Domain r7 started

2.
# virsh dompmsuspend r7 --target disk
Domain r7 successfully suspended

3.
# virsh start r7
Domain r7 started

4.
# virsh dompmsuspend r7 --target disk
Domain r7 successfully suspended

5.
# virsh start r7
Domain r7 started

6.
# virsh setmem --live r7 2048000

7.
# virsh dompmsuspend r7 --target disk
error: Domain r7 could not be suspended
error: internal error unable to execute QEMU agent command 'guest-suspend-disk': child process has failed to suspend

the step 7 should hang for this bug, but not.
Note You need to log in before you can comment on or make changes to this bug.