RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 621026 - guest become no response for "date" command after suspend to mem
Summary: guest become no response for "date" command after suspend to mem
Keywords:
Status: CLOSED DUPLICATE of bug 623913
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: beta
: ---
Assignee: Glauber Costa
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: Rhel6KvmTier1
TreeView+ depends on / blocked
 
Reported: 2010-08-04 02:40 UTC by Shirley Zhou
Modified: 2015-03-05 00:52 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-21 22:31:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.