Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Mike,
Can you please try if latest drivers solve the problem. If it is solved then we will have to use them for WLK.
Vadim says that it resembles , so can you try to turn on the flexpriority.
Comment 11RHEL Program Management
2013-10-17 01:15:08 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Description of problem: BSOD 9c happened during running WLK job "Device Path Exerciser" with virtio-win-prewhql-48 driver on winxp guest. Version-Release number of selected component (if applicable): Red Hat Enterprise Linux Server release 6.4 (Santiago) kernel-2.6.32-414.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.397.el6.x86_64 virtio-win-prewhql-0.1-48 spice-server-0.12.4-2.el6.x86_64 seabios-0.6.1.2-28.el6.x86_64 vgabios-0.6b-3.7.el6.noarch How reproducible: 100% Steps to Reproduce: 1.Boot guest with CLI: /usr/libexec/qemu-kvm -M rhel6.5.0 -m 2G -smp 2,cores=2 -cpu cpu64-rhel6 -usb -device usb-tablet -drive file=winxp-32.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none -device virtio-blk-pci,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no -device rtl8139,netdev=hostnet0,mac=00:53:55:51:3c:a0,bus=pci.0,addr=0x6 -netdev tap,sndbuf=0,id=hostnet1,script=/etc/qemu-ifup0,downscript=no -device rtl8139,netdev=hostnet1,mac=00:53:45:51:3c:10,bus=pci.0,addr=0x7 -uuid 179270aa-45bb-4394-a9cf-3e8114d8556e -no-kvm-pit-reinjection -drive file=disk1.raw,if=none,id=drive-virtio1,cache=none,werror=stop,rerror=stop,format=raw -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,format=raw -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,format=raw -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,format=raw -device virtio-blk-pci,drive=drive-virtio4,id=virtio-blk-pci4 -chardev socket,id=111a,path=/tmp/monitor-winxp-32-block,server,nowait -mon chardev=111a,mode=readline -name winxp32-block-48 -vnc :1 -vga cirrus -rtc base=localtime,clock=host,driftfix=slew -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -monitor stdio 2.running WLK job "Device Path Exerciser" 3. Actual results: BSOD 9C happened when running task "RunJob - Device Path Exerciser - Library Job" Expected results: "Device Path Exerciser" job could pass without any error. Windbg info: Use !analyze -v to get detailed debugging information. BugCheck C9, {c, b791daec, 0, 0} *** ERROR: Module load completed but symbols could not be loaded for viostor.sys Probably caused by : viostor.sys Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) The IO manager has caught a misbehaving driver. Arguments: Arg1: 0000000c, Invalid IOSB in IRP at APC IopCompleteRequest (appears to be on stack that was unwound) Arg2: b791daec, IOSB address Arg3: 00000000, IRP address Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0xc9_c DRIVER_VERIFIER_IO_VIOLATION_TYPE: c IOSB_ADDRESS: ffffffffb791daec IRP_ADDRESS: 8a6c4f00 DEFAULT_BUCKET_ID: DRIVER_FAULT PROCESS_NAME: devpathexer.exe DEVICE_OBJECT: 89af8a30 DRIVER_OBJECT: 89b8ea08 IMAGE_NAME: viostor.sys DEBUG_FLR_IMAGE_TIMESTAMP: 50b4b225 MODULE_NAME: viostor FAULTING_MODULE: bacbc000 viostor LAST_CONTROL_TRANSFER: from 80658714 to 804f9f33 STACK_TEXT: b791dc84 80658714 000000c9 0000000c b791daec nt!KeBugCheckEx+0x1b b791dca0 804f4b55 8a6c4f40 b791dd40 b791dd44 nt!IovpCompleteRequest+0x4c b791dcfc 804ff843 8a6c4f40 b791dd48 b791dd3c nt!IopCompleteRequest+0x39 b791dd4c 806e6ef2 00000001 00000000 b791dd64 nt!KiDeliverApc+0xb3 b791dd4c 77c43ab1 00000001 00000000 b791dd64 hal!HalpApcInterrupt+0xc6 WARNING: Frame IP not in any known module. Following frames may be wrong. 00c1feec 00000000 00000000 00000000 00000000 0x77c43ab1 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: 0xc9_c_VRF_IMAGE_viostor.sys_DATE_2012_11_27 BUCKET_ID: 0xc9_c_VRF_IMAGE_viostor.sys_DATE_2012_11_27 Followup: MachineOwner ---------