Description of problem:
Version-Release number of selected component (if applicable):
# rpm -qa|grep kvm
# uname -r
# uname -r
Steps to Reproduce:
1.boot a guest
# /usr/libexec/qemu-kvm -no-hpet -rtc-td-hack -usbdevice tablet -startdate now -name rhel6.0-32 -smp 2 -m 4G -boot c -drive file=/root/zhangjunyi/rhel6_32.qcow2,media=disk,if=virtio,cache=none,format=qcow2,werror=stop,boot=on -vnc :18 -cpu qemu64 -M rhel5.6.0 -notify all -balloon none -monitor stdio -net none
2. connect to guest with vnc
# vncviewer 10.66.72.60:18
3. suspend to disk
# echo disk > /sys/power/state
qemu-kvm process got killed during resume from s4
qemu-kvm process exists during resume from s4
1. I tried with -pcidevice and without -pcidevice, both hit this issue.
2. qemu-kvm exited with message: guest moved used index from 73534 to 0
3. attached screenshot and kernel message during resume
Created attachment 462829 [details]
kernel console output
During resume from s4, I sometimes can see the login hins, but it exited soon
It did't hit this issue with ide interface
A similar bz for rhel6 occurred -- virtio-blk does not support s4 correctly.
Not even sure it'll be in rhel6.1; so rhel5.x is in the same boat.
Added Kevin Wolf to cc: to confirm.
Correct. There was another bug for it and it was decided that a possible future support for suspend/resume won't be backported to RHEL 5. I'm not sure if there's one open for RHEL 6, but Amit was working on it upstream.
*** This bug has been marked as a duplicate of bug 516769 ***