| Summary: | [virtio-win][virtio-scsi]Guest hit BSOD after adding virtio-scsi disk which lies in the second pci | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Min Deng <mdeng> | ||||||
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 6.3 | CC: | acathrow, bcao, bsarathy, dawu, juzhang, michen, rhod, vrozenfe, wdai | ||||||
| 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: | 2013-02-28 12:59:32 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
Created attachment 567843 [details]
Screenshot of BSOD
dengmin ,pls verify this bug on build 30 , Thanks, (In reply to comment #5) > dengmin ,pls verify this bug on build 30 , > > Thanks, Verified the bz on virtio-win-prewhql-0.1-30 Steps,please refer to comments 0's step 1 to step 3 Actual results, 1.The guest always hit BSOD while boot up at step 3 via virtio-win-prewhql-0.1-23 2.The guest boot up successfully without any issues via virtio-win-prewhql-0.1-30 Draw a conclusion,the bz has been fixed on virtio-win-prewhql-0.1-30,thanks. Move status to verified according to comment #6. |
Created attachment 567839 [details] bios Description of problem: The guest has already be installed with virtio-scsi driver successfully before adding the second "-device virtio-scsi-pci". Shut down guest and attach a virtio-scsi disk but it lied in new pci (the second).Boot up guest,it cannot boot itself up and hit BSOD issue. Version-Release number of selected component (if applicable): qemu-kvm-0.12.1.2-2.236.el6.x86_64 virtio-win-prewhql-0.1-23 How reproducible: Always, Steps to Reproduce: 1.Boot up a guest with the following 1-CLI - it included a ide system disk and four virtio-scsi data disks. /usr/libexec/qemu-kvm -m 6G -smp 4 -cpu cpu64-rhel6,+x2apic,family=0xf -usb -device usb-tablet -drive file=win7-32-0229.raw,format=raw,if=none,id=ide0,werror=stop,rerror=stop,cache=none -device ide-drive,drive=ide0,id=ide0-0-0,bootindex=1 -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no -device e1000,netdev=hostnet0,mac=00:14:39:43:47:18 -uuid `uuidgen` -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win2k8-blk-scsi,server,nowait -mon chardev=111a,mode=readline -vnc :1 -rtc base=localtime,clock=host,driftfix=slew -chardev socket,id=seabios_debug,path=/tmp/monitor-seabios,server,nowait -device isa-debugcon,iobase=0x402,chardev=seabios_debug -device virtio-scsi-pci,id=scsi1 -drive file=disk1.raw,if=none,format=raw,cache=none,id=drive-virtio-data1,werror=stop,rerror=stop -device scsi-hd,bus=scsi1.0,id=virtio-data1,drive=drive-virtio-data1 -device virtio-scsi-pci,id=scsi2 -drive file=disk2.raw,if=none,cache=none,format=raw,id=drive-virtio-data2,werror=stop,rerror=stop -device scsi-hd,bus=scsi2.0,id=virtio-data2,drive=drive-virtio-data2 -device virtio-scsi-pci,id=scsi3 -drive file=disk3.raw,cache=none,if=none,format=raw,id=drive-virtio-data3,werror=stop,rerror=stop -device scsi-hd,bus=scsi3.0,id=virtio-data3,drive=drive-virtio-data3 -device virtio-scsi-pci,id=scsi4 -drive file=disk4.raw,if=none,format=raw,cache=none,id=drive-virtio-data4,werror=stop,rerror=stop -device scsi-hd,bus=scsi4.0,id=virtio-data4,drive=drive-virtio-data4 -bios /root/bios.bin 2.Log in guest and install virtio-scsi driver via virtio-win-prewhql-0.1-23 a.QE carefully checked the driver's status from Device Manager,furthermore, all the four disks were installed successfully.No error message was found. b.restart guest and checked them again and they still worked well. 3.changed the system disk to a virtio-scsi disk Please following the below 2-CLI: /usr/libexec/qemu-kvm -m 6G -smp 4 -cpu cpu64-rhel6,+x2apic,family=0xf -usb -device usb-tablet -device virtio-scsi-pci,id=scsi0 -drive file=win7-32-scsi.raw,format=raw,if=none,id=drive-virtio0,cache=none,werror=stop,rerror=stop -device scsi-hd,bus=scsi0.0,drive=drive-virtio0,id=virtio-blk-pci0,bootindex=1 -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no -device e1000,netdev=hostnet0,mac=00:14:39:43:47:18 -uuid `uuidgen` -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win2k8-blk-scsi,server,nowait -mon chardev=111a,mode=readline -vnc :1 -rtc base=localtime,clock=host,driftfix=slew -chardev socket,id=seabios_debug,path=/tmp/monitor-seabios,server,nowait -device isa-debugcon,iobase=0x402,chardev=seabios_debug -device virtio-scsi-pci,id=scsi1 -drive file=disk1.raw,if=none,format=raw,cache=none,id=drive-virtio-data1,werror=stop,rerror=stop -device scsi-hd,bus=scsi1.0,id=virtio-data1,drive=drive-virtio-data1 -device virtio-scsi-pci,id=scsi2 -drive file=disk2.raw,if=none,cache=none,format=raw,id=drive-virtio-data2,werror=stop,rerror=stop -device scsi-hd,bus=scsi2.0,id=virtio-data2,drive=drive-virtio-data2 -device virtio-scsi-pci,id=scsi3 -drive file=disk3.raw,cache=none,if=none,format=raw,id=drive-virtio-data3,werror=stop,rerror=stop -device scsi-hd,bus=scsi3.0,id=virtio-data3,drive=drive-virtio-data3 -device virtio-scsi-pci,id=scsi4 -drive file=disk4.raw,if=none,format=raw,cache=none,id=drive-virtio-data4,werror=stop,rerror=stop -device scsi-hd,bus=scsi4.0,id=virtio-data4,drive=drive-virtio-data4 -bios /root/bios.bin Actual results: The guest hit BSOD and boot up again and again. QE cannot reproduce the issue while using the below 3-CLI (1-CLI + 1 virtio-scsi data disk in new pci),user needed to re-install for new data disk in Device Manager before using it. 3-CLI: /usr/libexec/qemu-kvm -m 6G -smp 4 -cpu cpu64-rhel6,+x2apic,family=0xf -usb -device usb-tablet -drive file=win7-32-scsi.raw,format=raw,if=none,id=ide0,werror=stop,rerror=stop,cache=none -device ide-drive,drive=ide0,id=ide0-0-0,bootindex=1 -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no -device e1000,netdev=hostnet0,mac=00:14:39:43:47:18 -uuid `uuidgen` -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win2k8-blk-scsi,server,nowait -mon chardev=111a,mode=readline -vnc :1 -rtc base=localtime,clock=host,driftfix=slew -chardev socket,id=seabios_debug,path=/tmp/monitor-seabios,server,nowait -device isa-debugcon,iobase=0x402,chardev=seabios_debug -device virtio-scsi-pci,id=scsi1 -drive file=disk1.raw,if=none,format=raw,cache=none,id=drive-virtio-data1,werror=stop,rerror=stop -device scsi-hd,bus=scsi1.0,id=virtio-data1,drive=drive-virtio-data1 -device virtio-scsi-pci,id=scsi2 -drive file=disk2.raw,if=none,cache=none,format=raw,id=drive-virtio-data2,werror=stop,rerror=stop -device scsi-hd,bus=scsi2.0,id=virtio-data2,drive=drive-virtio-data2 -device virtio-scsi-pci,id=scsi3 -drive file=disk3.raw,cache=none,if=none,format=raw,id=drive-virtio-data3,werror=stop,rerror=stop -device scsi-hd,bus=scsi3.0,id=virtio-data3,drive=drive-virtio-data3 -device virtio-scsi-pci,id=scsi4 -drive file=disk4.raw,if=none,format=raw,cache=none,id=drive-virtio-data4,werror=stop,rerror=stop -device scsi-hd,bus=scsi4.0,id=virtio-data4,drive=drive-virtio-data4 -bios /root/bios.bin -device virtio-scsi-pci,id=scsi0 -drive file=disk5.raw,format=raw,if=none,id=drive-virtio0,cache=none,werror=stop,rerror=stop -device scsi-hd,bus=scsi0.0,drive=drive-virtio0,id=virtio-blk-pci0 Expected results: The guest can boot up successfully without BSOD. Additional info: Uploaded bios.bin in the bug.I didn't know if the above scenario was supported or not.So opened the bug for tracing,it can be reproduced on windows 7 and windows 2008.Any issues please let me know,thanks.