Bug 685041 - Crashdump Support Test(LOGO) fails on 2k3-64
Summary: Crashdump Support Test(LOGO) fails on 2k3-64
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xenpv-win
Version: 5.7
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Paolo Bonzini
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-15 06:43 UTC by Rita Wu
Modified: 2013-07-03 01:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-16 01:57:12 UTC
Target Upstream Version:

Attachments (Terms of Use)
screen shot of crashdump job (61.82 KB, image/png)
2011-03-15 06:43 UTC, Rita Wu 		no flags Details
wtl file (4.40 KB, application/octet-stream)
2011-03-15 06:46 UTC, Rita Wu 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Rita Wu 2011-03-15 06:43:08 UTC 
Created attachment 484368 [details]
screen shot of crashdump job

Description of problem:
It fails on "Initialize" sub-job of Crashdump Support Test(LOGO) to make the test machine getting BSOD, for WTT shutdown service is running unexpected before initialization finish. So there is no failure content on task log. 

Version-Release number of selected component (if applicable):
xenpv-win-1.3.4-6.el5.noarch.rpm
kernel-xen-2.6.18-245.el5.x86_64.rpm
xen-3.0.3-123.el5.x86_64.rpm
WLK1.5

How reproducible:
100%

Steps to Reproduce:
1. Setting NetworkNoChecksumOffload=1 and EnumerateDevicesOverride=1 in registry:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rhelscsi
2. Run Crashdump Support Test(LOGO) job

  
Actual results:
Crashdump Support Test(LOGO) fails

Expected results:
Pass.

Additional info:
2k3-32 can pass with the same settings.
Comment 1 Rita Wu 2011-03-15 06:46:20 UTC 
Created attachment 484371 [details]
wtl file
Comment 4 Rita Wu 2011-03-16 01:57:12 UTC 
Pass with inital=mem+1000 page file settings.
Note You need to log in before you can comment on or make changes to this bug.