Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Found this issue when running job "Common Scenario Stress With IO" for svvp, guest for win2k8-R2 with -smp 64 and -m 256GB often stuck after resuming from S4.
Version-Release number of selected component (if applicable):
kernel-2.6.32-269.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.290.el6.x86_64
Netkvm virtio-win-rewhql-0.1-27
Block virtio-win-rewhql-0.1-26
seabios-0.6.1.2-19.el6.x86_64
How reproducible:
70%
Steps to Reproduce:
Summarize the main steps for job "Common Scenario Stress With IO" for svvp as following:
1. Disable/Enable driver repeatedly for almost 10 times.
2. Do simpeIOStress
3. S4 after IO stress work done.
4. Resuming from S4.
5. Repeate 1-4 steps for many times, such as 12 times.
Actual results:
Guest stuck after resuming from S4,mainly happened in the first several times for S4,please refer to the attached "System_stuck_afterResumingFromS4_1.png".
Expected results:
Guest should resume successfully after S4.
Additional info:
When system_reset from qemu monitor, guest will prompt if "continue with system resume", if select it, you can continue resuming successfully,please refer to the attached "System_stuck_afterResumingFromS4_2.png".
Hi Vadim,
For job "Common Scenario Stress With IO" for svvp, if there is some mistakes in the steps described in the bug,please correct me, thanks!
Best Regards,
Dawn
Hi Dawn,
I don't see any mistake in your description.
Could you please export the System Event Log to a file and upload it as an
attachment?
Best regards,
Vadim.
(In reply to comment #6)
> Please also provide the guest configuration - are virtio drivers used?
Yes ,We use virtio drivers ,We hit this When we run SVVP Test -(system)Sleep stress with IO job .
Mike
Comment 11RHEL Program Management
2012-07-10 06:08:55 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 12RHEL Program Management
2012-07-11 02:07:38 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
This is a tough bug that requires a lot of time and patience.
The price-performance of working on it currently is not good, with all the Win8/HCK issues.
Deferring to 6.5.
(In reply to Ronen Hod from comment #20)
> QE,
> There were so many changes since RHEL6.4. Please recheck.
Hi Xiangchun,
Can you handle this?
Best Regards,
Junyi
(In reply to juzhang from comment #21)
> (In reply to Ronen Hod from comment #20)
> > QE,
> > There were so many changes since RHEL6.4. Please recheck.
>
> Hi Xiangchun,
>
> Can you handle this?
>
> Best Regards,
> Junyi
Junyi,
I will find a machine to re-test it.
As QE didn't find big memory machine. so Re-test it with -m 12G -smp 64.
According to comment 0.
result:
S4 pass, resume pass.
QE will continue to it when finding big memory machine. and update test result it asap.