Description of problem: the file /sys/power/status of rhel5u4 server is empty. and cannot suspend. both 32bits and 64bits rhel5u4s. Version-Release number of selected component (if applicable): kvm-83-83.el5 How reproducible: 100% reproducible Steps to Reproduce: 1. install rhel5u4 from tree RHEL5.4-Server-20090701.0 (with kernel 2.6.18-156) 2. in the guest issue command `cat /sys/power/status` 3. in the guest issue command `echo "disk" > /sys/power/status` Actual results: 1. after step2, the content of the file if empty. 2. after step3, error msg pops up, invalid argument. Expected results: 1. after step2, the content should be "disk mem" 2. after step3, the guest should suspend. Additional info: 1. command install geust: /usr/libexec/qemu-kvm -drive file=5u4_x86_64.qcow2,media=disk,if=ide,cache=off,index=0,serial=fb-bde1-8bcf10f72b98 -net nic,macaddr=20:20:20:00:16:79,model=e1000 -net tap,script=/etc/qemu-ifup -rtc-td-hack -no-hpet -usbdevice tablet -cpu qemu64,+sse2 -smp 2 -m 2G -vnc :12 -drive file=/root/29/isos/boot.iso,media=cdrom,if=ide -boot c 2. rhel5u4 server 32bits can suspend on physical machine, and the content of /sys/power/status is not empty. 3. rhel5u4 server 64bits cannot suspend.
Moving to NEW to mark it as free to be taken by the other developers.
FYI. rhel5u4 server (20090701.0) i386/x86_84 on physical box is support suspend . [root@dhcp-66-70-3 ~]#cat /sys/power/state standy mem disk rhel5u4 guest, /sys/power/state is empty. and in rhel5u3 i386/x86_64 guest. suspend is supported [root@dhcp-66-70-21 ~]#cat /sys/power/state mem disk
On which kvm release it worked (if any) in the past
We did not cover RHEL5U4 on the old versions of kvm. but at least, this issue does exist on -- [root@o18 ~]# cat /etc/redhat-release Red Hat Enterprise Virtualization Hypervisor release 5.4-2.0.99 (8.2) [root@o18 ~]# uname -a Linux o18 2.6.18-155.el5 #1 SMP Fri Jun 19 17:06:31 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux -- still no content in the file of the guests.
please attach dmesg of rhel5.3 and rhel5.4 running in a guest
Created attachment 350577 [details] dmesg of 5u3 as the description
Created attachment 350578 [details] dmesg of 5u4 - cannot suspend $description
Created attachment 350580 [details] dmesg of 5u4 non-xenkernel - cannot suspend $description
Created attachment 350585 [details] dmesg - 5u3 x86 32bits non-xen non-pae dmesg CLI: /usr/libexec/qemu-kvm -drive file=5.3s-32.img,media=disk,if=ide,cache=off,index=0,serial=fb-bde1-8bcf10f72b98 -net nic,macaddr=20:20:20:00:16:79,model=e1000 -net tap,script=/etc/qemu-ifup -rtc-td-hack -no-hpet -usbdevice tablet -cpu qemu64,+sse2 -smp 2 -m 1G -vnc :12
Created attachment 350586 [details] dmesg - 5u3 x86_64 non-xen non-pae dmesg CLI: /usr/libexec/qemu-kvm -drive file=5.3s-64.img,media=disk,if=ide,cache=off,index=0,serial=fb-bde1-8bcf10f72b98 -net nic,macaddr=20:20:20:00:16:79,model=e1000 -net tap,script=/etc/qemu-ifup -rtc-td-hack -no-hpet -usbdevice tablet -cpu qemu64,+sse2 -smp 2 -m 1G -vnc :12
Created attachment 350587 [details] dmesg - 5u4 x86 32bits non-xen non-pae dmesg CLI: /usr/libexec/qemu-kvm -drive file=5u4_x86_64.qcow2,media=disk,if=ide,cache=off,index=0,serial=fb-bde1-8bcf10f72b98 -net nic,macaddr=20:20:20:00:16:79,model=e1000 -net tap,script=/etc/qemu-ifup -rtc-td-hack -no-hpet -usbdevice tablet -cpu qemu64,+sse2 -smp 2 -m 1G -vnc :12
Created attachment 350588 [details] dmesg - 5u4 x86_64 non-xen non-pae dmesg CLI: /usr/libexec/qemu-kvm -drive file=5u4_x86_64.qcow2,media=disk,if=ide,cache=off,index=0,serial=fb-bde1-8bcf10f72b98 -net nic,macaddr=20:20:20:00:16:79,model=e1000 -net tap,script=/etc/qemu-ifup -rtc-td-hack -no-hpet -usbdevice tablet -cpu qemu64,+sse2 -smp 2 -m 1G -vnc :12
(In reply to comment #11) > Created an attachment (id=350587) [details] > dmesg - 5u4 x86 32bits non-xen non-pae > > dmesg > > CLI: > /usr/libexec/qemu-kvm -drive > file=5u4_x86_64.qcow2,media=disk,if=ide,cache=off,index=0,serial=fb-bde1-8bcf10f72b98 > -net nic,macaddr=20:20:20:00:16:79,model=e1000 -net tap,script=/etc/qemu-ifup > -rtc-td-hack -no-hpet -usbdevice tablet -cpu qemu64,+sse2 -smp 2 -m 1G -vnc :12 correct CLI: /usr/libexec/qemu-kvm -drive file=5u4_x86.qcow2,media=disk,if=ide,cache=off,index=0,serial=fb-bde1-8bcf10f72b98 -net nic,macaddr=20:20:20:00:16:79,model=e1000 -net tap,script=/etc/qemu-ifup -rtc-td-hack -no-hpet -usbdevice tablet -cpu qemu64,+sse2 -smp 2 -m 1G -vnc :12
just tested on xen-kernel and pae-kernel when filing this bug. Because xen kernel does not support S3, and I cannot reproduce this on pae-kernel. propose for closing this bug as "not a bug" or "cannot reproduce"( or "works for me"?).
retested and passed. please close this bug as NOTABUG. Thanks.