Bug 959011

Summary: [whql][netkvm]Device Path Exerciser job faild as BSOD(D1) on win2k3-32/64 guest.
Product: Red Hat Enterprise Linux 6 Reporter: Min Deng <mdeng>
Component: virtio-winAssignee: Yvugenfi <yvugenfi>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.5CC: acathrow, bcao, bsarathy, dfleytma, juzhang, lijin, michen, qzhang
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Please don't document. Regression between the internal builds.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-22 00:04:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
DUMPfiles
none
win2k3-64-MEMORY.DMP
none
Dumpfiles base on the latest driver (60) none

Description Min Deng 2013-05-03 01:13:31 UTC 
Description of problem:
The job failed as bsod occurs

Version-Release number of selected component (if applicable):
virtio-win-prewhql-59
How reproducible:
5 times

Steps to Reproduce:
1.Boot up guest with the following CLI
  /usr/libexec/qemu-kvm -m 2G -smp 4 -cpu cpu64-rhel6,+x2apic -usb -device usb-tablet -drive file=win2k3-64-nic1.raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,sndbuf=0,id=hostnet0,vhost=on,script=/etc/qemu-ifup-private,downscript=no -device virtio-net-pci,netdev=hostnet0,mac=03:57:24:21:a3:41,bus=pci.0,addr=0x4,id=virtio-net-pci0 -netdev tap,sndbuf=0,id=hostnet2,script=/etc/qemu-ifup,downscript=no -device e1000,netdev=hostnet2,mac=00:36:53:c1:4a:20,bus=pci.0,addr=0x6 -uuid bde8f241-bed4-450a-a8a9-ca10b91d69f2 -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win2012-nic1,server,nowait -mon chardev=111a,mode=readline -vnc :1 -rtc base=localtime,clock=host,driftfix=slew -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -vga cirrus
2.Submit the job to HCK
Actual results:
The job always failed due to BSOD issue.

Expected results:
The job can pass

Additional info:
Comment 2 Min Deng 2013-05-03 02:09:16 UTC 
Created attachment 742980 [details]
hck-log

The guest always failed at sub job DisableEDTSupport
Comment 3 Min Deng 2013-05-03 02:23:00 UTC 
Created attachment 742983 [details]
DUMPfiles
Comment 6 Dmitry Fleytman 2013-05-12 12:25:07 UTC 

*** This bug has been marked as a duplicate of bug 912926 ***
Comment 8 Dmitry Fleytman 2013-05-16 07:19:29 UTC 
Hello Min,

Please attach crash dump for the latest version.

Thanks,
Dmitry
Comment 9 guo jiang 2013-05-16 08:54:09 UTC 
Created attachment 748668 [details]
win2k3-64-MEMORY.DMP
Comment 13 Min Deng 2013-05-16 09:33:19 UTC 
Created attachment 748699 [details]
Dumpfiles base on the latest driver (60)
Comment 16 Min Deng 2013-05-21 03:24:33 UTC 
Hi all,

   QE re-run the job named Device Path Exerciser with build 61 on windows 2k3(32/64) platform.

   Actual Results,the job can pass with any issues.
   
   Expected Results,the job will pass.

   So the original issue has been fixed on build 61,thanks.

Best Regards
Min
Comment 17 Yvugenfi@redhat.com 2013-05-21 07:38:18 UTC 
(In reply to dengmin from comment #16)
> Hi all,
> 
>    QE re-run the job named Device Path Exerciser with build 61 on windows
> 2k3(32/64) platform.
> 
>    Actual Results,the job can pass with any issues.
>    
>    Expected Results,the job will pass.
> 
>    So the original issue has been fixed on build 61,thanks.
> 
> Best Regards
> Min

Thanks! 
Please move to verified.
Comment 18 Mike Cao 2013-05-21 10:57:22 UTC 
Based on comment #17 ,move status to VERIFIED
Comment 20 errata-xmlrpc 2013-11-22 00:04:49 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1729.html