Bug 669314

Summary: (virtio-win-1.1.17) Can not generate crash dump file after BSOD of Windows guests.
Product: Red Hat Enterprise Linux 6 Reporter: Qunfang Zhang <qzhang>
Component: virtio-winAssignee: Vadim Rozenfeld <vrozenfe>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: dawu, lihuang, ndai, vrozenfe, ykaul
Target Milestone: rcKeywords: Regression, TestBlocker
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: virtio-win-1.1.18 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 14:31:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Qunfang Zhang 2011-01-13 10:17:40 UTC 
Description of problem:
Run "Crashdump Support Test(logo)" job of whql virtio block testing, always failed. Guest can not find the MEMORY.dmp file.
Generate a BSOD manually,can not collect dump file and there's an error in qemu monitor:

(qemu) block I/O error in device 'drive-virtio0': Input/output error (5)

DTM log:
Start Test 1/13/2011 9:58:00.673 AM Loading Dump File Test 
End Test 1/13/2011 9:58:00.673 AM Loading Dump File Test 
Result:   Fail 
Repro:   crashdumptest.exe -autorun -y C:\symbols -dtm 

Command line:
/usr/libexec/qemu-kvm -m 2G -smp 2 -cpu cpu64-rhel6,+x2apic,family=0xf -usbdevice tablet -drive file=win7-32-blk.raw,if=none,id=drive-virtio0,boot=on,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio0,id=virtio-blk-pci0 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device e1000,netdev=hostnet0,mac=00:10:40:32:2a:3a,bus=pci.0,addr=0x4 -boot c -uuid 6b61e56c-931d-4c40-8371-7dfb37725a59 -rtc-td-hack -no-kvm-pit-reinjection -monitor stdio -name win7-32-blk -vnc :10 -drive file=disk1.raw,if=none,id=drive-virtio1,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio1,id=virtio-blk-pci1 -drive file=disk2.raw,if=none,id=drive-virtio2,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio2,id=virtio-blk-pci2 -drive file=disk3.raw,if=none,id=drive-virtio3,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio3,id=virtio-blk-pci3 -drive file=disk4.raw,if=none,id=drive-virtio4,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio4,id=virtio-blk-pci4

Version-Release number of selected component (if applicable):
virtio-win-1.1.17
kernel-2.6.32-95.el6.x86_64
qemu-kvm-0.12.1.2-2.129.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Run whql "Crashdump Support Test(logo)" job" or generate BSOD Manually.
2.
3.
  
Actual results:
Can not generate dump file.

Expected results:


Additional info:
Comment 3 Vadim Rozenfeld 2011-01-22 20:07:36 UTC 
Please try the latest driver from:
http://download.lab.bos.redhat.com/devel/RHEV/virtio-win/1.1.18/
Vadim.
Comment 4 dawu 2011-01-25 09:21:10 UTC 
Verified this issue with the latest driver 1.1.18, it does not reproduce, dump file can be generated and whql job of "Crashdump Support Test(logo)" passed without error.
Comment 5 errata-xmlrpc 2011-05-19 14:31:41 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0782.html