Bug 584268 - "WHQL:Common Scenario Stress with IO" failed in network test for all Windows 2008 OS and Block test for Windows 2008 x64
Summary: "WHQL:Common Scenario Stress with IO" failed in network test for all Windows ...
Keywords:
Status: CLOSED DUPLICATE of bug 566786
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xenpv-win
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Xen Maintainance List
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-21 07:47 UTC by Xiaoli Tian
Modified: 2010-10-07 16:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-21 12:49:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
BSOD screen shot (121.15 KB, image/png)
2010-04-21 08:58 UTC, Xiaoli Tian 		no flags Details
View All

Description Xiaoli Tian 2010-04-21 07:47:00 UTC 
Description of problem:
"WHQL:Common Scenario Stress with IO" failed in network test for all Windows 2008 OS and failed in Block test for Windows 2008 x64
the  task "Execute Common_Scenario_Stress_With_IO-Script" would pass but have finished different count of jobs in different Windows OS ,and the next task "check if test was completed" would always failed 

Version-Release number of selected component (if applicable):
version of Xen-PV Driver:04/12/2010,1.1.0.3
Kenel is :kernel-xen-2.6.18-195.el5

How reproducible:
always

Steps to Reproduce:
1.prepare the WHQL test environment.
2.install the xenpv-win driver for the guest to be tested
3.start to test Common Scenario Stress with IO
  
Actual results:
failed

Expected results:
pass
Additional info:
Comment 1 Xiaoli Tian 2010-04-21 08:58:18 UTC 
Created attachment 408021 [details]
BSOD  screen shot

task "check if test was completed" cause BSOD,
the BSOD screen shot is attached
and no dump files are found.
Comment 2 Paolo Bonzini 2010-04-21 12:49:41 UTC 

*** This bug has been marked as a duplicate of bug 566786 ***
Note You need to log in before you can comment on or make changes to this bug.