Bug 621026

Summary:	guest become no response for "date" command after suspend to mem
Product:	Red Hat Enterprise Linux 6	Reporter:	Shirley Zhou <szhou>
Component:	qemu-kvm	Assignee:	Glauber Costa <gcosta>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	akong, amit.shah, llim, mkenneth, mshao, sneuner, tburke, virt-maint
Target Milestone:	beta	Keywords:	RHELNAK
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-11-21 22:31:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	580951

Description Shirley Zhou 2010-08-04 02:40:15 UTC

Description of problem:
rhel guest become no response for "date" command after s3, and can not ping guest after s3

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.104.el6.x86_64
kernel-2.6.32-54.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1.run rhel6 guest
/usr/libexec/qemu-kvm -m 1G -smp 1 -cpu qemu64,+x2apic -usbdevice tablet -drive file=/mnt/RHEL-Server-6.0-64.qcow2,if=none,id=drive-virtio0,boot=on,werror=stop,rerror=stop,cache=none,format=qcow2 -device virtio-blk-pci,drive=drive-virtio0,id=virtio-blk-pci0 -netdev tap,id=hostnet0,script=/mnt/qemu-ifup,ifname=virtio_nic_1 -device virtio-net-pci,netdev=hostnet0,mac=0a:30:18:3F:40:aa,bus=pci.0,id=virtio1,addr=0x5  -uuid a234127c-8765-1234-95da-1dd0a8891cc4 -name RHEL6-145 -qmp tcp:0:4445,server,nowait   -device virtio-balloon-pci,id=ba1 -monitor stdio -vnc :1
2.do suspend to mem
echo mem >/sys/power/state
3.after guest wake up, type "date" command
  
Actual results:

There is no response for "date" command after step3

Expected results:
date info should shows

Additional info:
1.other commands ,like "ls, cd" are ok after s3
2.if we run "date" before s3, then do s3, then run 'date' , it is ok
3.can not ping guest after s3
4.can not do s3 again after s3
5.this issue does not happen when using ide block and rtl8139 network

Comment 2 RHEL Program Management 2010-08-04 03:07:45 UTC

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 3 Glauber Costa 2010-10-13 14:29:06 UTC

Just to make sure we're doing the same steps, how are you waking up your guest?

Comment 4 Shirley Zhou 2010-10-14 01:46:01 UTC

(In reply to comment #3)
> Just to make sure we're doing the same steps, how are you waking up your guest?

Glauber, the guest will wake up automatically after do # echo mem >/sys/power/state.

Comment 5 Dor Laor 2010-11-21 22:31:11 UTC


*** This bug has been marked as a duplicate of bug 623913 ***