Description of problem: Find this issue when verifying bug 834511. With virtio devices attached and then do s3 for multiple times, guest will gets call trace and can not return back to desktop or console. But network is available. Create this separate bz for this issue because actually s3/s4 is not allowed and bug 834511 could be verified pass. Version-Release number of selected component (if applicable): kernel-2.6.18-330.el5 How reproducible: Always Steps to Reproduce: 1.Boot a rhel5.9 guest with virtio device attached # /usr/libexec/qemu-kvm -no-hpet -no-kvm-pit-reinjection -usbdevice tablet -rtc-td-hack -startdate now -name RHEL5.8-32 -smp 2,cores=2 -k en-us -m 2048 -boot c -net nic,vlan=1,macaddr=00:1a:4a:42:49:00,model=virtio -net tap,vlan=1,ifname=virtio_10_1,script=/etc/qemu-ifup,downscript=no -drive file=/home/rhel5.8-32-virtio.qcow2,media=disk,if=ide,cache=off,format=qcow2,werror=stop -cpu qemu64,+sse2 -M rhel5.6.0 -notify all -balloon none -monitor stdio -vnc :10 2. Inside guest. #pm-suspend 3. #pm-suspend again Actual results: Guest call trace and can not go back to desktop. Expected results: Guest works well. Additional info: Please check attachment.
Created attachment 600213 [details] Guest call trace at the 2nd time doing s3
Thanks for reporting it, but it is exactly due to these issues that we disabled the S3 support, so I am closing this bug.
*** Bug 1012822 has been marked as a duplicate of this bug. ***