Hide Forgot
Description of problem: after s4 successfully,boot the guest again to resume with the same command line, guest will appear black screen and not any response. if add clock=pmtmr option to grub start line, guest can resume from s4. Version-Release number of selected component (if applicable): --host kvm-83-232.el5 etherboot-zroms-kvm-5.4.4-15.el5 kmod-kvm-debug-83-232.el5 kvm-tools-83-232.el5 kmod-kvm-83-232.el5 kvm-qemu-img-83-232.el5 kvm-debuginfo-83-232.el5 uname -r 2.6.18-259.el5 How reproducible: Steps to Reproduce: 1./usr/libexec/qemu-kvm -no-hpet -usbdevice tablet -rtc-td-hack -name 57 -smp 2 -m 4G -uuid 9e6f04cf-2ad7-45aa-9333-2d2ee26570c6 -boot c -drive file=/usr/tools/rhel57.qcow2,if=ide,cache=none,boot=on,format=qcow2,werror=stop -net nic,vlan=1,macaddr=52:54:00:94:a3:8b,model=rtl8139 -net tap,vlan=1,script=/etc/qemu-ifup -notify all -balloon none -monitor stdio -vnc :1 2.connect to guest via vnc 3.do s4 in guest echo disk > /sys/power/state 4.after guest shutdown, boot the guest again to resume with the same command line Actual results: guest appears black screen, guest can not resume from s4 Expected results: guest resume successfully Additional info: add clock=pmtmr option to grub start line, guest resume successfully
Created attachment 497696 [details] Serial log (contains Call Trace) Hi Fu, Attached the serial log, can you help to confirm that I touched a same bug.
i saw serial log in attachment, i got the same trace log. do s4 in rhel5.7 host, it can resume.
The first time enable kdump in rhel5.7 guest,kvm-83-230.el5 and kvm-83-232.el5 can reproduce this bug. only in first enable kdump can reproduce it. other cases s4 can be resumed.
(In reply to comment #0) > Description of problem: rhel5.7 guest could not resume from s4 when the first enabled kdump in guest. only in first enable kdump it can be reproduced. > if add clock=pmtmr option to grub start line, guest can resume from s4. > > Version-Release number of selected component (if applicable): > --host > kvm-83-232.el5 > etherboot-zroms-kvm-5.4.4-15.el5 > kmod-kvm-debug-83-232.el5 > kvm-tools-83-232.el5 > kmod-kvm-83-232.el5 > kvm-qemu-img-83-232.el5 > kvm-debuginfo-83-232.el5 > > uname -r > 2.6.18-259.el5 > > How reproducible: > > > Steps to Reproduce: > 1./usr/libexec/qemu-kvm -no-hpet -usbdevice tablet -rtc-td-hack -name 57 -smp 2 > -m 4G -uuid 9e6f04cf-2ad7-45aa-9333-2d2ee26570c6 -boot c -drive > file=/usr/tools/rhel57.qcow2,if=ide,cache=none,boot=on,format=qcow2,werror=stop > -net nic,vlan=1,macaddr=52:54:00:94:a3:8b,model=rtl8139 -net > tap,vlan=1,script=/etc/qemu-ifup -notify all -balloon none -monitor stdio -vnc > :1 > > 2.connect to guest via vnc > 3.do s4 in guest > echo disk > /sys/power/state > 4.after guest shutdown, boot the guest again to resume with the same command > line > > Actual results: > guest appears black screen, guest can not resume from s4 > > Expected results: > guest resume successfully > > > > > Additional info: > add clock=pmtmr option to grub start line, guest resume successfully (In reply to comment #0) > Description of problem: > after s4 successfully,boot the guest again to resume with the same command > line, guest will appear black screen and not any response. > if add clock=pmtmr option to grub start line, guest can resume from s4. > > Version-Release number of selected component (if applicable): > --host > kvm-83-232.el5 > etherboot-zroms-kvm-5.4.4-15.el5 > kmod-kvm-debug-83-232.el5 > kvm-tools-83-232.el5 > kmod-kvm-83-232.el5 > kvm-qemu-img-83-232.el5 > kvm-debuginfo-83-232.el5 > > uname -r > 2.6.18-259.el5 > > How reproducible: > > > Steps to Reproduce: > 1./usr/libexec/qemu-kvm -no-hpet -usbdevice tablet -rtc-td-hack -name 57 -smp 2 > -m 4G -uuid 9e6f04cf-2ad7-45aa-9333-2d2ee26570c6 -boot c -drive > file=/usr/tools/rhel57.qcow2,if=ide,cache=none,boot=on,format=qcow2,werror=stop > -net nic,vlan=1,macaddr=52:54:00:94:a3:8b,model=rtl8139 -net > tap,vlan=1,script=/etc/qemu-ifup -notify all -balloon none -monitor stdio -vnc > :1 > > 2.connect to guest via vnc > 3.do s4 in guest > echo disk > /sys/power/state > 4.after guest shutdown, boot the guest again to resume with the same command > line > > Actual results: > guest appears black screen, guest can not resume from s4 > > Expected results: > guest resume successfully > > > > > Additional info: > add clock=pmtmr option to grub start line, guest resume successfully
Here is a summary: on 2.6.18-260.el5 x86_64 host, with kvm-83-232.el5.x86_64, in 2.6.18-259.el5 x86_64 guest. guest got black screen when resuming from s4, will attach the log. text mode + S4 ---> always desktop + S4 ---> sometimes
Created attachment 498742 [details] CLI: /usr/libexec/qemu-kvm -M rhel5.6.0 -no-hpet -rtc-td-hack -startdate now -name rhel5.7 -smp 2 -m 2048 -cpu qemu64,+sse2 -uuid `uuidgen` -boot c -net nic,vlan=1,macaddr=F0:4D:A2:24:ad:89,model=e100
(In reply to comment #6) > Created attachment 498742 [details] > CLI: /usr/libexec/qemu-kvm -M rhel5.6.0 -no-hpet -rtc-td-hack -startdate now > -name rhel5.7 -smp 2 -m 2048 -cpu qemu64,+sse2 -uuid `uuidgen` -boot c -net > nic,vlan=1,macaddr=F0:4D:A2:24:ad:89,model=e100 /usr/libexec/qemu-kvm -M rhel5.6.0 -no-hpet -rtc-td-hack -startdate now -name rhel5.7 -smp 2 -m 2048 -cpu qemu64,+sse2 -uuid `uuidgen` -boot c -net nic,vlan=1,macaddr=F0:4D:A2:24:ad:89,model=e1000 -net tap,vlan=1,script=/etc/qemu-ifup -drive file=/home/s4test/rhel57.qcow2,media=disk,if=ide,cache=none,boot=on,format=qcow2 -vnc :1 -notify all -balloon none -monitor stdio -serial unix:/tmp/test.sock,server,nowait
And guest networking is not available when guest stuck, cpu usage reached 100%: ping 10.66.x.x PING 10.66.x.x (10.66.x.x) 56(84) bytes of data. From 10.66.x.x icmp_seq=2 Destination Host Unreachable From 10.66.x.x icmp_seq=3 Destination Host Unreachable From 10.66.x.x icmp_seq=4 Destination Host Unreachable ^C --- 10.66.x.x ping statistics --- 6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5086ms pipe 3
*** This bug has been marked as a duplicate of bug 647115 ***