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.
Cause:
Due to a bug in libvirt code, it was possible to successfully call suspend on a pmsuspended domain. The difference is while in the former case guest OS doesn't know it is being suspended (suspend is just a matter of hypervisor), in the latter case, guest OS cooperation is required. This result in, e.g. guest clock to be synchronized after the resume. Obviously, these two cases are mutually exclusive.
Consequence:
Libvirt returned success on operation which should fail.
Fix:
A check for this special case has been added.
Result:
Libvirt will now refuse to suspend a pmsuspended domain.
Description of problem:
when guest in pmsuspend status, should forbid suspend&resume guest.
Version-Release number of selected component (if applicable):
libvirt-0.10.0-0rc0.el6.x86_64
qemu-kvm-0.12.1.2-2.295.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. install qemu-ga in the domain [qemu-guest-agent] and add xml into
domain
<channel type='unix'>
<source mode='bind' path='/var/lib/libvirt/qemu/tests3.agent'/>
<target type='virtio' name='org.qemu.guest_agent.0'/>
<alias name='channel0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
2. start domain and login domain , run qemu-ga -d in the domain
#qemu-ga -d
#
3.in the host run pmsuspend
#virsh dompmsuspend $domain --target mem
check domain status
#virsh domstate $domain
pmsuspended
4.suspend& resume $domain
#virsh suspend $domain
Domain tests3 suspended
#virsh resume $domain
Domain tests3 resumed
#virsh state $domain
running
use virt-viewer to check guest, seem in pmsuspend status.
Actual results:
see step 4
Expected results:
when guest in s3 , should not do suspend&resume
Additional info:
Moving to POST:
commit 385ee0e982080d03ce0d11eab32396c0d7057961
Author: Michal Privoznik <mprivozn>
AuthorDate: Thu Aug 23 15:26:20 2012 +0200
Commit: Michal Privoznik <mprivozn>
CommitDate: Thu Aug 23 17:48:44 2012 +0200
qemu: forbid suspend if already pmsuspended
If a domain is pmsuspended then virsh suspend will succeed. Beside
obvious flaw, virsh resume will report success and change domain
state to running which is another mistake. Therefore we must forbid
any attempts for suspend and resume when pmsuspended.
v0.10.0-rc1-16-g385ee0e
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2013-0276.html
Description of problem: when guest in pmsuspend status, should forbid suspend&resume guest. Version-Release number of selected component (if applicable): libvirt-0.10.0-0rc0.el6.x86_64 qemu-kvm-0.12.1.2-2.295.el6.x86_64 How reproducible: always Steps to Reproduce: 1. install qemu-ga in the domain [qemu-guest-agent] and add xml into domain <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/tests3.agent'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> 2. start domain and login domain , run qemu-ga -d in the domain #qemu-ga -d # 3.in the host run pmsuspend #virsh dompmsuspend $domain --target mem check domain status #virsh domstate $domain pmsuspended 4.suspend& resume $domain #virsh suspend $domain Domain tests3 suspended #virsh resume $domain Domain tests3 resumed #virsh state $domain running use virt-viewer to check guest, seem in pmsuspend status. Actual results: see step 4 Expected results: when guest in s3 , should not do suspend&resume Additional info: