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.
Hi Vadim,
I tried win2012R2-pc/q35 five times with the virtio-win-prewhql-200, the steps are same as comment , BSOD is gone, the guest can reboot/shutdown successfully. thanks for your effort.
Thanks
Dehan Meng
(In reply to dehanmeng from comment #5)
> Hi Vadim,
> I tried win2012R2-pc/q35 five times with the virtio-win-prewhql-200, the
> steps are same as comment , BSOD is gone, the guest can reboot/shutdown
> successfully. thanks for your effort.
>
> Thanks
> Dehan Meng
Hi Dehan,
Thank a lot for your feedback.
Best,
Vadim.
Description of problem: After installing viogpudo driver, I tried to use signtool.exe&sigverf to sign viogpudo driver, but guest hit bsod situation directly when I tried to reboot/shutdown it. Version-Release number of selected component (if applicable): RHEL-8.5.0-20210506.n.0 qemu-kvm-6.0.0-16.module+el8.5.0+10848+2dccc46d.x86_64 kernel-4.18.0-305.1.el8.x86_64 seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch virtio-win-prewhql-199.iso How reproducible: 100% Steps to Reproduce: 1.bootup guest with following qemu-cli /usr/libexec/qemu-kvm \ -name 'win2012R2' \ -sandbox on \ -machine q35 \ -device pcie-root-port,id=pcie-root-port-0,multifunction=on,bus=pcie.0,addr=0x1,chassis=1 \ -device pcie-pci-bridge,id=pcie-pci-bridge-0,addr=0x0,bus=pcie-root-port-0 \ -nodefaults \ -device virtio-vga,id=video0 \ -m 4096 \ -smp 10,maxcpus=10,cores=5,threads=1,dies=1,sockets=2 \ -cpu Skylake-Server,hv_stimer,hv_synic,hv_time,hv_vpindex,hv_relaxed,hv_spinlocks=0xfff,hv_vapic,hv_frequencies,hv_runtime,hv_tlbflush,hv_reenlightenment,hv_stimer_direct,hv_ipi \ -device pvpanic,ioport=0x505,id=idAw3tKn \ -device pcie-root-port,id=pcie-root-port-1,port=0x1,addr=0x1.0x1,bus=pcie.0,chassis=2 \ -device qemu-xhci,id=usb1,bus=pcie-root-port-1,addr=0x0 \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -device pcie-root-port,id=pcie-root-port-2,port=0x2,addr=0x1.0x2,bus=pcie.0,chassis=3 \ -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pcie-root-port-2,addr=0x0 \ -blockdev node-name=file_image1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=win2012-64-virtio-scsi.qcow2,cache.direct=on,cache.no-flush=off \ -blockdev node-name=drive_image1,driver=qcow2,read-only=off,cache.direct=on,cache.no-flush=off,file=file_image1 \ -device scsi-hd,id=image1,drive=drive_image1,write-cache=on \ -device pcie-root-port,id=pcie-root-port-3,port=0x3,addr=0x1.0x3,bus=pcie.0,chassis=4 \ -device virtio-net-pci,mac=9a:aa:3c:f4:36:fb,id=iddZeBQu,netdev=idDOmGd4,bus=pcie-root-port-3,addr=0x0 \ -netdev tap,id=idDOmGd4,vhost=on \ -cdrom /home/kvm_autotest_root/iso/windows/virtio-win-prewhql-0.1-199.iso \ -vnc :9 \ -chardev socket,server=on,wait=off,path=/tmp/avocado_wojsvlg0/monitor-qmpmonitor1-20210522-021250-p57eGDBS,id=qmp_id_qmpmonitor1 \ -mon chardev=qmp_id_qmpmonitor1,mode=control \ -rtc base=localtime,clock=host,driftfix=slew \ -boot menu=off,order=cdn,once=c,strict=off \ -enable-kvm \ 2. install driver via device manager 3. sign driver 1). verifier /flags 0x008209BB /driver viogpudo.sys 2). SignTool.exe verify /v /kp /c viogpudo.cat viogpudo.sys 3). SignTool.exe verify /v /kp /c viogpudo.cat viogpudo.inf 4). sigverif --> click "Start" 4. reboot/shutdown guest Actual results: windows bsod. Expected results: VM should be reboot/shutdown successfully. Additional info: