Bug 1965159
| Summary: | [viogpudo] Reboot/shutdown/Reset failed and hit black screen after installing viogpudo driver on win2012-64 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | dehanmeng <demeng> |
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> |
| virtio-win sub component: | virtio-win-prewhql | QA Contact: | dehanmeng <demeng> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | juzhang, lijin, mdean, qizhu, vrozenfe, yvugenfi |
| Version: | 9.0 | Keywords: | Triaged |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | 9.0 | ||
| Hardware: | x86_64 | ||
| OS: | Windows | ||
| Whiteboard: | |||
| Fixed In Version: | 218 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-15 10:45:57 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
the fix included into https://github.com/virtio-win/kvm-guest-drivers-windows/pull/586 Please give a try to build 200 https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=37224650 (In reply to Vadim Rozenfeld from comment #2) > Please give a try to build 200 > https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=37224650 Hi Vadim, Thanks for your effort, I've tried 200 build for this issue a lot of times, but this problem still be there. Guest couldn't reboot/shutdown after installing viogpudo driver. Could you please have another shot with it? Thanks Dehan (In reply to dehanmeng from comment #3) > (In reply to Vadim Rozenfeld from comment #2) > > Please give a try to build 200 > > https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=37224650 > > Hi Vadim, > > Thanks for your effort, I've tried 200 build for this issue a lot of times, > but this problem still be there. Guest couldn't reboot/shutdown after > installing viogpudo driver. Could you please have another shot with it? > > Thanks > Dehan Hi Dehan, Since virtio-win drivers are not cross-signed anymore can you please to the following things: 1. Enable test signing on your testing machine ("Bcdedit.exe -set TESTSIGNING ON") 2. Install virogpudo driver with "devcon install" (https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/devcon-install) rather than with Device Manager . Thanks, Vadim. (In reply to Vadim Rozenfeld from comment #4) > (In reply to dehanmeng from comment #3) > > (In reply to Vadim Rozenfeld from comment #2) > > > Please give a try to build 200 > > > https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=37224650 > > > > Hi Vadim, > > > > Thanks for your effort, I've tried 200 build for this issue a lot of times, > > but this problem still be there. Guest couldn't reboot/shutdown after > > installing viogpudo driver. Could you please have another shot with it? > > > > Thanks > > Dehan > > Hi Dehan, > > Since virtio-win drivers are not cross-signed anymore can you please to the > following things: > 1. Enable test signing on your testing machine ("Bcdedit.exe -set > TESTSIGNING ON") > 2. Install virogpudo driver with "devcon install" > (https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/devcon- > install) > rather than with Device Manager > . > > Thanks, > Vadim. As we talked before as mail. this method you suggested I've tried before, but issue still there, so update this situation here. THanks Dehan Add TestBlocker keyword for this bug because I need to use a new system image for testing next other cases if I hit this issue, so set a TestBlocker. Hi Vadim, How's going on this issue? The DTM is 23(2.7), but the bug's status still is assigned. so Do we have any progress of it? or if there are any risk please let me know. thanks. BRs Dehan Meng (In reply to dehanmeng from comment #20) > Hi Vadim, > How's going on this issue? The DTM is 23(2.7), but the bug's status still is > assigned. so Do we have any progress of it? or if there are any risk please > let me know. thanks. > > BRs > Dehan Meng Hi Dehan, I will submit a fix for this bug shortly, Best, Vadim. Reproduce this bug as comment0, can be reproduced successfully. Verify: version: virtio-win-prewhql-218.iso win2012-64/win2012R2-64 Steps as comments Actual result: Reboot/Reset/Shutdown successfully. Expected result: Reboot/Reset/Shutdown successfully. 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 (virtio-win bug fix and enhancement update), 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-2022:8261 |
Description of problem: Win2012-64(q35) guest couldn't reboot/shutdown normally after installing 199 viogpudo driver, the guest will hang for a while and then go to black screen situation. and then I tried to kill its process directly and boot it up again manually. but the guest still was black screen. 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 'win2012-64' \ -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 prewhql199 viogpudo driver via device manager. 3.run cmd "shutdown -r -t 0" Actual results: guest hang for a while and then hit black screen. Expected results: reboot/shutdown successfully like normal operation. Additional info: