Bug 770797

Summary:	BSOD 0x101 found when running SVVP stress job
Product:	Red Hat Enterprise Linux 5	Reporter:	Qin Guan <qguan>
Component:	xenpv-win	Assignee:	Xen Maintainance List <xen-maint>
Status:	CLOSED CANTFIX	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.8	CC:	jzheng, leiwang, pbonzini, qwan, yuzhou
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Windows
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-11 13:16:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	807971

Description Qin Guan 2011-12-29 07:14:30 UTC

Description of problem:
BSOD with stopcode 0x101 always happen when running the SVVP stress related jobs, such as:
"Disk Stress [System LOGO]" or
"System - Common Scenario Stress With IO"

Version-Release number of selected component (if applicable):
kernel-xen-2.6.18-300.el5
xen-3.0.3-135.el5
xenpv-win-1.3.12-3.el5

How reproducible:
Always

Steps to Reproduce:
1. Steps RHEL5.8 xen SUTs (1 max and 4 multiples) for SVVP environment
2. Submit "Disk Stress [System LOGO]" on all of the SUTs
3. BSOD found on all the SUTs (1 max and 4 multiples) when the job "Disk Stress" running

Note that it's not a block problem, as the jobs can still finish without error after the SUTs destroyed and re-created .
 
Actual results:
BSOD with stop code 0x101

Expected results:
No BSOD on SUT

Additional info:
Refer to the attachment and the dump core file.

Comment 2 RHEL Program Management 2012-04-02 10:37:24 UTC

This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 3 Paolo Bonzini 2012-04-11 13:16:02 UTC

This happens when the system is (even lightly) overcommitted.  There is nothing that can be done (backporting Viridian extensions to RHEL-5 is not a possibility).