Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): package located in http://people.redhat.com/pbonzini/virtio-scsi/ virtio-win-prewhql-22 How reproducible: 100% Steps to Reproduce: 1.start guest with virtio scsi CLI:/usr/libexec/qemu-kvm -m 6G -smp 4 -cpu cpu64-rhel6,+x2apic,family=0xf -usb -device usb-tablet -drive file=win2k8-blk-scsi,format=raw,if=none,id=drive-virtio0,cache=none,werror=stop,rerror=stop -device ide-drive,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:52:26:26:66:06 -uuid 646a3d45-afed-44c4-9827-6d6e54e83540 -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win2k8-blk-scsi,server,nowait -mon chardev=111a,mode=readline -vnc :3 -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=scsi -drive file=disk1.raw,if=none,format=raw,id=drive-virtio-data1,werror=stop,rerror=stop -device scsi-hd,id=virtio-data1,drive=drive-virtio-data1 -drive file=disk2.raw,if=none,format=raw,id=drive-virtio-data2,werror=stop,rerror=stop -device scsi-hd,id=virtio-data2,drive=drive-virtio-data2 -drive file=disk3.raw,if=none,format=raw,id=drive-virtio-data3,werror=stop,rerror=stop -device scsi-hd,id=virtio-data3,drive=drive-virtio-data3 -drive file=disk4.raw,if=none,format=raw,id=drive-virtio-data4,werror=stop,rerror=stop -device scsi-hd,id=virtio-data4,drive=drive-virtio-data4 2.install virtio scsi in the guest Actual results: BSOD happened in the guest Expected results: driver should be installed successfully. Additional info:
Hi, Vadim Is this issue fixed in virtio-win-prewhql-23 ? Why status is still post ? BTW Could you supply me a seabios with both virtio-scsi and power management support ? Best Regards, Mike
(In reply to comment #3) > Hi, Vadim > > Is this issue fixed in virtio-win-prewhql-23 ? Hi Mike, Yes, it should. > Why status is still post ? Turning it to ON_QA. > BTW Could you supply me a seabios with both virtio-scsi and power management > support ? Will build it for you shortly. Kind regards, Vadim. > > Best Regards, > Mike
Hi, Vadim Could you add this bug to RHBA-2011:12358-01 ? Thanks, Mike
Created attachment 564781 [details] seabios with virtio-scsi support + S3 enabled bios with virtio-scsi support + S3 enabled Hi Mike, Didn't try it by myself (s3 part), but it should work. Best regards, Vadim.
(In reply to comment #7) > Created attachment 564781 [details] > seabios with virtio-scsi support + S3 enabled > > bios with virtio-scsi support + S3 enabled > > Hi Mike, > Didn't try it by myself (s3 part), but it should work. > > Best regards, > Vadim. Hi, Vadim This one does not work ,it may does not include the patch about boot from scsi disk . Could you re-compile one for me based on seabios located in ttp://people.redhat.com/pbonzini/virtio-scsi/ and support s3/s4 ? Thanks Mike
(In reply to comment #8) > (In reply to comment #7) > > Created attachment 564781 [details] > > seabios with virtio-scsi support + S3 enabled > > > > bios with virtio-scsi support + S3 enabled > > > > Hi Mike, > > Didn't try it by myself (s3 part), but it should work. > > > > Best regards, > > Vadim. > > Hi, Vadim > > This one does not work ,it may does not include the patch about boot from scsi > disk . > Could you re-compile one for me based on seabios located in > ttp://people.redhat.com/pbonzini/virtio-scsi/ and support s3/s4 ? Hi Mike, It's exactly what I did. I will check it on my system and come back to you shortly. Best, Vadim. > > Thanks > Mike
Let's move it to rhel6.4.
verify it on win2k8-32 and win2k8-64 with virtio-win-prewhql-29 steps: 1.start guest with virtio scsi /usr/libexec/qemu-kvm -m 6G -smp 4 -cpu cpu64-rhel6,+x2apic,family=0xf -usb -device usb-tablet -device virtio-scsi-pci,id=scsi1 -drive file=/home/win2k8-32-0608.raw,format=raw,if=none,id=drive-virtio0,cache=none,werror=stop,rerror=stop -device scsi-hd,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:52:16:11:10:aa -uuid fac99c6f-20ef-448c-8f5e-aa7d63724b44 -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win2k8-32-scsi,server,nowait -mon chardev=111a,mode=readline -vnc :3 -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=scsi -drive file=disk5.raw,if=none,format=raw,id=drive-virtio-data1,werror=stop,rerror=stop -device scsi-hd,id=virtio-data1,drive=drive-virtio-data1 -drive file=disk6.raw,if=none,format=raw,id=drive-virtio-data2,werror=stop,rerror=stop -device scsi-hd,id=virtio-data2,drive=drive-virtio-data2 -drive file=disk3.raw,if=none,format=raw,id=drive-virtio-data3,werror=stop,rerror=stop -device scsi-hd,id=virtio-data3,drive=drive-virtio-data3 -drive file=disk4.raw,if=none,format=raw,id=drive-virtio-data4,werror=stop,rerror=stop -device scsi-hd,id=virtio-data4,drive=drive-virtio-data4 2.install virtio scsi driver in the guest. 3.run CrystalDisk tool to check. Actual results: Both of the two guests work well, no BSOD or crash occurs. Base on above,this issue has been fixed.
According to comment #17 ,change status to VERIFIED. Vadim ,Could you grant devel_ack since this bug has already been fixed ? Thanks.
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-0441.html