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.
(In reply to Vadim Rozenfeld from comment #4)
> Can you please share the hckx file?
>
> Thanks,
> Vadim.
the hckx file is already attached，please check the attachment “win8-32-blk-105 hck log“ :)
anything else please let me know.
(In reply to lijin from comment #6)
> win10-32/64/win2016 also hit this issue with build105
Yes, it's a common problem. Should be fixed in next build.
Vadim.
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.
https://rhn.redhat.com/errata/RHBA-2015-2513.html
Created attachment 1035796 [details] win8-32-blk-105 hck log Description of problem: job "Flush Test" failed on all guests with build 105 Version-Release number of selected component (if applicable): qemu-kvm-rhev-2.3.0-2.el7.x86_64 kernel-3.10.0-258.el7.x86_64 seabios-1.7.5-9.el7.x86_64 virtio-win-prewhql-105 How reproducible: 100% Steps to Reproduce: 1.boot guest with: /usr/libexec/qemu-kvm -name 105BLKWIN8322FO -enable-kvm -m 6G -smp 4 -uuid 5fb68d1c-e1d0-4c74-8c1b-ecbd1f441ce6 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/tmp/105BLKWIN8322FO,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,bus=pci.0,addr=0x1.0x2 -drive file=105BLKWIN8322FO,if=none,id=drive-ide0-0-0,format=raw,serial=mike_cao,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=en_windows_8_enterprise_x86_dvd_917587.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=105BLKWIN8322FO.vfd,if=none,id=drive-fdc0-0-0,format=raw,cache=none -global isa-fdc.driveA=drive-fdc0-0-0 -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:52:58:5d:8b:9c,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=isa_serial0 -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -vga cirrus -drive file=105BLKWIN8322FO_test.raw,if=none,id=drive-virtio-disk0,format=raw,serial=mike_cao,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0 2.submit job "Flush Test" in HCK Actual results: job failed when run child job "StorIO Library (SuddenReboot)" of "Flush Scenario Set - 256MB seq seq seq seq" Expected results: job can pass Additional info: we did NOT hit this issue with build 86/90,so this is regression bug