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 BZ1745298#c22 the comment states:
>all drivers are NOT installed on win2012 guest after installer execution finishes, reboot does not work neither.
What does "reboot does not work neither" mean? What happens when you try to reboot the system?
(In reply to Jeff Nelson from comment #1)
> In BZ1745298#c22 the comment states:
> >all drivers are NOT installed on win2012 guest after installer execution finishes, reboot does not work neither.
>
> What does "reboot does not work neither" mean? What happens when you try to
> reboot the system?
reboot operation succeed, I mean after reboot, driver are still not installed.
I did reboot just because sometimes it only take effect after system reboot.
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/RHEA-2020:0351
Created attachment 1646058 [details] win2012 screen shot after installer finishes Description of problem: Version-Release number of selected component (if applicable): virtio-win-1.9.10-2.el8/virtio-win-installer-1.9.10-1 How reproducible: 100% Steps to Reproduce: 1.boot up win2012 guest and attach virtio devices: /usr/libexec/qemu-kvm \ -name 'avocado-vt-vm1' \ -sandbox on \ -machine pc \ -nodefaults \ -m 8192 \ -vga std \ -smp 8 \ -cpu 'EPYC',hv_stimer,hv_synic,hv_vpindex,hv_reset,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv-tlbflush,+kvm_pv_unhalt \ -device pvpanic,ioport=0x505,id=idDcIXCy \ -device qemu-xhci,id=usb1,bus=pci.0,addr=0x3 \ -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x4 \ -drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=/home/kvm_autotest_root/images/win2012-64-virtio-scsi.qcow2 \ -device ide-drive,id=image1,drive=drive_image1,serial=SYSTEM_DISK0 \ -drive id=drive_image2,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=/home/scsi.qcow2 \ -device scsi-hd,id=image2,drive=drive_image2,serial=SYSTEM_DISK1 \ -drive id=drive_image3,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=/home/blk.qcow2 \ -device virtio-blk-pci,id=image3,drive=drive_image3,serial=SYSTEM_DISK2 \ -device virtio-net-pci,mac=9a:0e:45:5b:cd:04,id=idi5kxSq,netdev=idNGuJpX \ -netdev tap,id=idNGuJpX,vhost=on,script=/etc/qemu-ifup \ -drive id=drive_unattended,if=none,snapshot=off,aio=threads,cache=none,media=cdrom,file=/home/kvm_autotest_root/iso/windows/virtio-win-1.9.10-2.el8.iso \ -device ide-cd,id=unattended,drive=drive_unattended,bus=ide.1,unit=1 \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -rtc base=localtime,clock=host,driftfix=slew \ -boot menu=off,order=cdn,once=d,strict=off \ -device virtio-balloon-pci,id=balloon0 \ -device virtio-rng-pci,id=rng0 \ -device virtio-serial-pci,id=serial0 \ -device virtio-keyboard-pci,id=kbd0 \ -device virtio-mouse-pci,id=mouse0 \ -device virtio-tablet-pci,id=tablet0 \ -monitor stdio \ -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 \ -device virtserialport,bus=serial0.0,chardev=qga0,name=org.qemu.guest_agent.0 \ -enable-kvm \ -vnc :0 \ -chardev socket,path=/tmp/133QSRW10S64TGQ_serial0,server,nowait,id=serial0 -device pci-serial,chardev=serial0,id=pciserial0 2.run virtio-win-gt-x86.msi in guest and click "install" 3.check drivers installation status in device manager Actual results: all drivers are not installed, nothing changes after installation. Expected results: drivers can be installed correctly Additional info: