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:
I have an Intel systems - dell-per720(8 CPUS, 32G memory), which is used to start up 2 windows 32bit guests, win 7 sp1 and win 8.1. Keep rebooting these two guests, and run stress to exhaust host memory. BSOD happens after many iterations of reboot in guest.
Version-Release number of selected component (if applicable):
3.10.0-222.el7.x86_64
qemu-kvm-rhev-2.1.2-20.el7.x86_64
How reproducible:
2/2
Steps to Reproduce:
1. Start guests aforementioned
2. Start taskschd and keep them reboot
3. Run stress instance on host to exhaust memory to hundreds MB free:
stress --vm 6 --vm-bytes 2G --vm-keep
Actual results:
For win 7 sp1:
*** Stop: 0x0000005C (0x0000010B,0x00000001,0x000000000,0x00000000)
For win 8.1:
Your PC needs to restart.
Please hold down the power button.
Error Code: 0x0000005C
Parameters:
0x00000110
0xFFD0E9F8
0x00000019
0xC0000001
Expected results:
Additional info:
1.
Microsoft says "0x00000050 PAGE_FAULT_IN_NONPAGED_AREA" at
http://msdn.microsoft.com/en-us/library/windows/hardware/hh994433(v=vs.85).aspx
2. Reproducible with qemu-kvm-rhev-1.5.3-60.el7_0.7.x86_64
(In reply to Chao Yang from comment #0)
> Description of problem:
> I have an Intel systems - dell-per720(8 CPUS, 32G memory), which is used to
> start up 2 windows 32bit guests, win 7 sp1 and win 8.1. Keep rebooting these
> two guests, and run stress to exhaust host memory. BSOD happens after many
> iterations of reboot in guest.
>
> Version-Release number of selected component (if applicable):
> 3.10.0-222.el7.x86_64
> qemu-kvm-rhev-2.1.2-20.el7.x86_64
>
> How reproducible:
> 2/2
>
> Steps to Reproduce:
> 1. Start guests aforementioned
> 2. Start taskschd and keep them reboot
> 3. Run stress instance on host to exhaust memory to hundreds MB free:
>
> stress --vm 6 --vm-bytes 2G --vm-keep
>
> Actual results:
>
> For win 7 sp1:
> *** Stop: 0x0000005C (0x0000010B,0x00000001,0x000000000,0x00000000)
>
> For win 8.1:
> Your PC needs to restart.
> Please hold down the power button.
> Error Code: 0x0000005C
> Parameters:
> 0x00000110
> 0xFFD0E9F8
> 0x00000019
> 0xC0000001
>
>
>
> Expected results:
>
>
> Additional info:
> 1.
> Microsoft says "0x00000050 PAGE_FAULT_IN_NONPAGED_AREA" at
> http://msdn.microsoft.com/en-us/library/windows/hardware/hh994433(v=vs.85).
> aspx
>
Sorry, correction:
0x0000005C HAL_INITIALIZATION_FAILED
> 2. Reproducible with qemu-kvm-rhev-1.5.3-60.el7_0.7.x86_64
(In reply to Gal Hammer from comment #5)
> Looks like a duplicate of bug 1178607.
>
> Which virtio-win drivers are installed? What version?
It is virtio-win-1.7.2-2.el6.noarch for netkvm/block/scsi, virtio-win-prewhql-94 for vioserial, virtio-win-prewhql-96 for balloon/viorng.