| Summary: | [virtio-win][viostor] BSOD when upgrade rhel5.7 driver to rhel6.3 current driver (virtio-win-prewhql-0.1-26) on guest with data disk. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | dawu | ||||
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.3 | CC: | acathrow, bcao, bsarathy, dyasny, juzhang, michen, rhod, yvugenfi | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-04-17 09:21:50 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: | |||||
| Attachments: |
|
||||||
I will have some tries from old version of rhel6 such as rhel6.2 to latest rhel6.3 driver, and update the results later. Best Regards, Dawn Dawn, please also help version in which the regression happened, thanks. Closing as a duplicate of the famous Bug 691192. This problem cannot be fixed inside the new driver, as it is the old driver that crashes. It is solved in RHEV-M's installer. *** This bug has been marked as a duplicate of bug 691192 *** |
Created attachment 577945 [details] win7-32-BSOD-upgrade from rhel5.7 to rhel 6.3 Description of problem: BSOD when upgrade rhel5.7 driver to rhel6.3 current driver (virtio-win-prewhql-0.1-26) on win7-32 guest with data disk. Version-Release number of selected component (if applicable): kernel-2.6.32-259.el6.x86_64 qemu-kvm-0.12.1.2-2.270.el6.x86_64 virtio-win-rewhql-0.1-25 seabios-0.6.1.2-16.el6.x86_64 How reproducible: always Steps to Reproduce: 1.Start guest with one data disk with rhel5.7 driver (virtio-win-1.0.3-1.52454) /usr/libexec/qemu-kvm -m 2G -smp 2 -cpu cpu64-rhel6,+x2apic,family=0xf -usb -device usb-tablet -drive file=win7-32-blk-fun.raw,format=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,bootindex=1 -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup0,downscript=no -device e1000,netdev=hostnet0,mac=00:10:1a:01:78:26,bus=pci.0,addr=0x4 -uuid b35f00e9-c93d-4c14-883e-0451a4331d2c -rtc base=localtime,clock=host,driftfix=slew -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/win7-32,server,nowait -mon chardev=111a,mode=readline -monitor stdio -spice disable-ticketing,port=5931 -vga qxl -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 2.Upgrade driver for both two disks (system-disk and data disk) from rhel5.7 to current latest driver virtio-win-prewhql-0.1-26 for rhel6.3 3.Restart to make the upgrade effective. Actual results: Guest hang in shut down and finally BSOD, please refer to the attached "win7-32-BSOD-upgrade-57-26.png", following is the analysis for dump file: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 00000024, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 8881a744, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: 00000024 CURRENT_IRQL: 2 FAULTING_IP: storport!RaidUnitReleaseIrp+11 8881a744 8b7e24 mov edi,dword ptr [esi+24h] DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: 883e1e30 -- (.trap 0xffffffff883e1e30) ErrCode = 00000000 eax=845aaa58 ebx=845aaa58 ecx=845aaaec edx=01000000 esi=00000000 edi=8542035c eip=8881a744 esp=883e1ea4 ebp=883e1eb0 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 storport!RaidUnitReleaseIrp+0x11: 8881a744 8b7e24 mov edi,dword ptr [esi+24h] ds:0023:00000024=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 8881a744 to 826455cb STACK_TEXT: 883e1e30 8881a744 badb0d00 01000000 844e67c0 nt!KiTrap0E+0x2cf 883e1eb0 8881abf6 845aaa58 845aaa58 8542035c storport!RaidUnitReleaseIrp+0x11 883e1eec 8881ae79 846c90e8 84777008 844760e8 storport!RaUnitAsyncError+0x15e 883e1f20 8880c31e 846c90e8 844760a4 85f35824 storport!RaidUnitCompleteRequest+0x11f 883e1f48 8267c1b5 844760a4 84476030 00000000 storport!RaidpAdapterDpcRoutine+0x51 883e1fa4 8267c018 883c1120 85f357a0 00000000 nt!KiExecuteAllDpcs+0xf9 883e1ff4 8267b7dc 9a167a4c 00000000 00000000 nt!KiRetireDpcList+0xd5 883e1ff8 9a167a4c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c WARNING: Frame IP not in any known module. Following frames may be wrong. 8267b7dc 00000000 0000001a 00d6850f bb830000 0x9a167a4c STACK_COMMAND: kb FOLLOWUP_IP: storport!RaidUnitReleaseIrp+11 8881a744 8b7e24 mov edi,dword ptr [esi+24h] SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: storport!RaidUnitReleaseIrp+11 FOLLOWUP_NAME: MachineOwner MODULE_NAME: storport IMAGE_NAME: storport.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79a02 FAILURE_BUCKET_ID: 0xD1_storport!RaidUnitReleaseIrp+11 BUCKET_ID: 0xD1_storport!RaidUnitReleaseIrp+11 Followup: MachineOwner ------------------------------------------------------------------------------- Expected results: Driver upgrade with data disk should successfully without any BSOD. Additional info: 1.This issue does not exist on guest with only one system virtio disk. 2.During rhel6.3 drivers, no this issue happened for upgrade, such as upgrade from virtio-win-prewhql-0.1-16 to virtio-win-prewhql-0.1-26. 3.Tried upgrade from 5.7 to virtio-win-prewhql-0.1-25, also reproduced.