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.
Created attachment 1271086[details]
windows 2016 dump collecting status
Description of problem:
Version-Release number of selected component (if applicable):
OVMF-20170228-3.gitc325e41585e3.el7.noarch
kernel-3.10.0-640.el7.x86_64
qemu-kvm-rhev-2.8.0-6.el7.x86_64
virtio-win-prewhql-135
seabios-1.10.2-2.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.boot windows 2016 with virtio-blk-pci device on amd host under q35&ovmf
/usr/libexec/qemu-kvm -name SVVP_RHEL7u4_AMD_BIG -M q35 -device ioh3420,bus=pcie.0,id=root1.0,slot=1 -device ioh3420,bus=pcie.0,id=root2.0,slot=2 -drive file=OVMF_CODE.secboot.fd-amd,if=pflash,format=raw,unit=0,readonly=on -drive file=OVMF_VARS.fd-amd,if=pflash,format=raw,unit=1 -drive file=UefiShell.iso-amd,if=none,cache=none,snapshot=off,aio=native,media=cdrom,id=cdrom1 -device ide-cd,drive=cdrom1,id=ide-cd1 \
-cpu Opteron_G5 -enable-kvm -m 2G -smp 1 -uuid 7a04aabb-fe44-4fa0-923d-fb8849693f58 -smbios type=1,manufacturer='Red Hat,product=RHEL OpenStack Platform Version 7.4 & RHEV Version 7.4,version=7Server-7.4.0.0.el7',serial='14F00000-BF99-11E1-BAC6-80 C16 BB53 B38,uuid=051af2b9-a8d9-4dbe-acee-1157e45636f5' -nodefconfig -rtc base=localtime,driftfix=slew -drive file=virtio-win-prewhql-135.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -object iothread,id=thread0 -drive file=win2016-sut-amd.raw,if=none,format=raw,cache=none,werror=stop,rerror=stop,id=drive-virtio-disk0,aio=native -device virtio-blk-pci,scsi=off,iothread=thread0,bus=root1.0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,downscript=/etc/qemu-ifdown1,script=/etc/qemu-ifup1,id=hostnet0,vhost=on,queues=48 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=ef:52:00:46:f0:ee,mq=on,vectors=98,bus=root2.0 -device piix3-usb-uhci,id=usb -device usb-tablet,id=tablet0 \
-vnc 0.0.0.0:0 -k en-us -vga std -monitor stdio -qmp tcp:0:4446,server,nowait -boot menu=on \
-cdrom en_windows_server_2016_x64_dvd_9327751.iso \
2.in guest,uncheck the automatically restart after system failure
3.trigger guest bsod with nmi
(qemu) nmi
3.after a few minutes,reboot guest:
(qemu) system_reset
4.after guest reboot,check the dump file in c:\windows\
Actual results:
after step3,guest bsod,but dump collecting status keep at 0%(as the attachment shows)
after step4,no dump file can be found in c:\windows
Expected results:
dump file can be generated
Additional info:
with build 126:
on both intel and amd:bsod dump collect percentage can reach 100%,and can generate dump correctly;
with build135:
intel:bsod dump collect status keep at 0%,but after reboot,the dump file is actually generated;
amd:bsod dump collect status keep at 0% and no dump file can be found in c:\windows
I also try with q35&seabios,still can reproduce this issue.
This bisects to:
commit 22b16fa580df278798b7eba7d6dfad5be3f896da
Author: Vadim Rozenfeld <vrozenfe>
Date: Fri Dec 2 19:54:48 2016 +1100
first mq working code
There are two bugs:
1) The page area and pool area in the storport uncached extension may overlap which leads to memory corruption.
2) The list_head field was removed from ADAPTER_EXTENSION but we still try to remove items from it in several places.
RemoveEntryList(&vbr->list_entry);
1) was copied from vioscsi so it will need to be fixed also. Fixes coming!
It looks like 2) was already fixed in
commit 7cb2e3abec1cb39d05c9a3ad15b6b02314a897aa
Author: Vadim Rozenfeld <vrozenfe>
Date: Wed Dec 14 21:08:20 2016 +1100
. simplify SRB processing path
Posted https://github.com/virtio-win/kvm-guest-drivers-windows/pull/127 with the fix for 1).
verify this issue with build 136 on win2016
(both with vioscsi and viostor)
on both intel and amd:
bsod dump collect percentage can reach 100%,and can generate dump correctly
Above all, this issue has been fixed. change status to verified.
Thanks
Yu Wang
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://access.redhat.com/errata/RHBA-2017:2341
Created attachment 1271086 [details] windows 2016 dump collecting status Description of problem: Version-Release number of selected component (if applicable): OVMF-20170228-3.gitc325e41585e3.el7.noarch kernel-3.10.0-640.el7.x86_64 qemu-kvm-rhev-2.8.0-6.el7.x86_64 virtio-win-prewhql-135 seabios-1.10.2-2.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.boot windows 2016 with virtio-blk-pci device on amd host under q35&ovmf /usr/libexec/qemu-kvm -name SVVP_RHEL7u4_AMD_BIG -M q35 -device ioh3420,bus=pcie.0,id=root1.0,slot=1 -device ioh3420,bus=pcie.0,id=root2.0,slot=2 -drive file=OVMF_CODE.secboot.fd-amd,if=pflash,format=raw,unit=0,readonly=on -drive file=OVMF_VARS.fd-amd,if=pflash,format=raw,unit=1 -drive file=UefiShell.iso-amd,if=none,cache=none,snapshot=off,aio=native,media=cdrom,id=cdrom1 -device ide-cd,drive=cdrom1,id=ide-cd1 \ -cpu Opteron_G5 -enable-kvm -m 2G -smp 1 -uuid 7a04aabb-fe44-4fa0-923d-fb8849693f58 -smbios type=1,manufacturer='Red Hat,product=RHEL OpenStack Platform Version 7.4 & RHEV Version 7.4,version=7Server-7.4.0.0.el7',serial='14F00000-BF99-11E1-BAC6-80 C16 BB53 B38,uuid=051af2b9-a8d9-4dbe-acee-1157e45636f5' -nodefconfig -rtc base=localtime,driftfix=slew -drive file=virtio-win-prewhql-135.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -object iothread,id=thread0 -drive file=win2016-sut-amd.raw,if=none,format=raw,cache=none,werror=stop,rerror=stop,id=drive-virtio-disk0,aio=native -device virtio-blk-pci,scsi=off,iothread=thread0,bus=root1.0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,downscript=/etc/qemu-ifdown1,script=/etc/qemu-ifup1,id=hostnet0,vhost=on,queues=48 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=ef:52:00:46:f0:ee,mq=on,vectors=98,bus=root2.0 -device piix3-usb-uhci,id=usb -device usb-tablet,id=tablet0 \ -vnc 0.0.0.0:0 -k en-us -vga std -monitor stdio -qmp tcp:0:4446,server,nowait -boot menu=on \ -cdrom en_windows_server_2016_x64_dvd_9327751.iso \ 2.in guest,uncheck the automatically restart after system failure 3.trigger guest bsod with nmi (qemu) nmi 3.after a few minutes,reboot guest: (qemu) system_reset 4.after guest reboot,check the dump file in c:\windows\ Actual results: after step3,guest bsod,but dump collecting status keep at 0%(as the attachment shows) after step4,no dump file can be found in c:\windows Expected results: dump file can be generated Additional info: with build 126: on both intel and amd:bsod dump collect percentage can reach 100%,and can generate dump correctly; with build135: intel:bsod dump collect status keep at 0%,but after reboot,the dump file is actually generated; amd:bsod dump collect status keep at 0% and no dump file can be found in c:\windows I also try with q35&seabios,still can reproduce this issue.