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.
Can we please confirm that it is still the case? Does it happen on Windows Server 2008 Service Pack 2 only, because I cannot reproduce it on WS2012/WS2016 with the latest drivers installed.
Thanks,
Vadim.
(In reply to Vadim Rozenfeld from comment #3)
> Can we please confirm that it is still the case? Does it happen on Windows
> Server 2008 Service Pack 2 only, because I cannot reproduce it on
> WS2012/WS2016 with the latest drivers installed.
>
> Thanks,
> Vadim.
Yes, it only happened on win2008sp2, at least it happened on win2008-32. I can still reproduce this issue with 7.5 release build on win8.1-32, win2008-32 and win2012-64
And my /dev/sg4 backend is iscsi.
I attached my crystal tool, you can try with it.(version is CrystalDiskMark 3.0.3)
Thanks
Yu Wang
(In reply to Yu Wang from comment #5)
> Created attachment 1456647[details]
> crystaldiskmark_tool
thanks a lot.
will give it a try soon.
Meanwhile moving it to 7.7
Vadim.
The fact that the problem is not reproducible with scsi-hd/block as mentioned in the bug description
means that the problem is not related to the driver itself. Closing this issuse as WONTFIX.
Created attachment 1277311 [details] crystal-error Description of problem: CrystalDiskMark occurred error (4K QD32) when boot with scsi-generic device Version-Release number of selected component (if applicable): qemu-kvm-rhev-2.9.0-2.el7.x86_64 kernel-3.10.0-661.el7.x86_64 seabios-1.10.2-2.el7.x86_64 virtio-win-prewhql-136 How reproducible: 100% Steps to Reproduce: 1. boot with scsi-generic /usr/libexec/qemu-kvm -name 136BLK20083237D -enable-kvm -m 4G -smp 4,cores=4 -uuid 33e65720-5ae8-42d2-8f46-f3e0b9796741 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/tmp/136BLK20083237D,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -boot order=cd,menu=on -device piix3-usb-uhci,id=usb -drive file=136SCS20083237D.vfd,if=floppy,id=drive-fdc0-0-0,format=raw,cache=none -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=00:52:07:58:6c:53 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=isa_serial0 -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -qmp tcp:0:4444,server,nowait -vga std -M pc -monitor stdio -device virtio-scsi-pci,id=scsi0,bus=pci.0,num_queues=4 -drive file=136BLK20083237D,if=none,id=drive-scsi-disk0,format=raw,serial=abcdefghijklmnopqrstabcdefghijklmnopqrstabcdefghijklmnopqrstuvwxyzabcdefg,cache=none -device scsi-hd,bus=scsi0.0,drive=drive-scsi-disk0,id=scsi-disk0 -device virtio-scsi-pci,id=scsi1 \ -device virtio-scsi-pci,id=scsi3,bus=pci.0,num_queues=4 -drive file=/dev/sg4,if=none,id=drive-scsi-disk3,format=raw,serial=mike_cao,cache=writethrough -device scsi-generic,bus=scsi3.0,drive=drive-scsi-disk3,id=scsi-disk3 2.run crystaldiskmark 3. Actual results: error occurred when running 4K QD32,"Reak Error 0x0000000:The operation completed successfully" Expected results: run without error Additional info: 1 it cannot reproduce with scsi-hd/block -drive file=/dev/sde (/dev/sde and /dev/sg4 are the same disk) 2 can reproduce with 7.3 release driver.