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.
Hit this issue again on guest RHEL-Server-6.0-64 with -pcidevice option, if without -pcidevice option, guest cannot suspend to memory with write error.
Hit this issue on guest RHEL-Server-6.0-32 with/without -pcidevice option.
--Host
# rpm -qa|grep kvm
kmod-kvm-83-215.el5
kmod-kvm-debug-83-215.el5
kvm-qemu-img-83-215.el5
kvm-tools-83-215.el5
etherboot-zroms-kvm-5.4.4-13.el5
kvm-debuginfo-83-215.el5
kvm-83-215.el5
# uname -r
2.6.18-232.el5
--Guest
For RHEL-Server-6.0-64
# uname -r
2.6.32-71.el6.x86_64
For RHEL-Server-6.0-32
# uname -r
2.6.32-71.el6.i686
+++ This bug was initially created as a clone of Bug #647108 +++
Description of problem:
Version-Release number of selected component (if applicable):
--Host
#rpm -qa | grep kvm
etherboot-zroms-kvm-5.4.4-13.el5
kvm-qemu-img-83-204.el5
kmod-kvm-83-204.el5
kvm-tools-83-204.el5
kvm-83-205.el5
etherboot-roms-kvm-5.4.4-13.el5
kvm-debuginfo-83-204.el5
#uname -r
2.6.18-227.el5
#rpm -qa | grep spic
qspice-0.3.0-56.el5
qspice-debuginfo-0.3.0-56.el5
qspice-libs-0.3.0-56.el5
-Guest
#uname -r
2.6.18-194.el5
How reproducible:
Steps to Reproduce:
1.boot guest with spice and qxl
#/usr/libexec/qemu-kvm -M rhel5.6.0 -m 2G -smp 2 -drive file=/root/chayang/testcasefor5u6.raw,if=ide,format=raw,boot=on,cache=none,werror=stop -net nic,vlan=0,macaddr=24:23:12:25:b1:5a,model=e1000 -net tap,vlan=0,script=/etc/qemu-ifup -boot c -monitor stdio -spice host=0,ic=on,port=5930,disable-ticketing -qxl 1
2.connect to guest via spice client
# spice -h 10.66.91.43 -p 5930
3.Do s3 in guest
echo mem > /sys/power/state
Actual results:
guest can't resume successfully,details info please have a look at attchment
Expected results:
guest resume successfully
Additional info:
--- Additional comment from chayang on 2010-10-27 04:56:57 EDT ---
Please note:
I also tested s3 using vnc,didn't hit this issue
--- Additional comment from chayang on 2010-10-28 04:26:15 EDT ---
Created attachment 456181[details]
when resume from S3
Comment 9RHEL Program Management
2011-01-07 04:07:04 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
This request was erroneously denied for the current release of Red Hat
Enterprise Linux. The error has been fixed and this request has been
re-proposed for the current release.
Comment 11RHEL Program Management
2011-02-01 05:39:58 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 12RHEL Program Management
2011-02-01 18:54:44 UTC
This request was erroneously denied for the current release of
Red Hat Enterprise Linux. The error has been fixed and this
request has been re-proposed for the current release.