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 wangyu from comment #9)
> win7-64 still hit this issue with build 114
>
> error code 52
could you please share the setupapi.dev.log file?
Thanks,
Vadim.
Reproduced this issue on virtio-win-prewhql-115
Verified this issue on virtio-win-prewhql-116
Verified guest os :
*win7-64
*win2008-64
*win2008R2.
Verified driver
*viorng
*balloon
*vioser
*pvpanic
*netkvm
*viostor
*vioscsi
steps same as comment#0
on build 116,driver can all successfully installed
Above all, bug has been fixed, fix version virtio-win-prewhql-116.
Thanks for your great support!:)
BR
wyu
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-2016-2609.html
Created attachment 1107073 [details] driver_install_error Description of problem: Cannot install vioscsi driver on win7-64&win2008-64&win2008R2 Version-Release number of selected component (if applicable): kernel-3.10.0-335.el7.x86_64 qemu-kvm-rhev-2.3.0-31.el7.x86_64 virtio-win-prewhql-112 How reproducible: 100% Steps to Reproduce: 1./usr/libexec/qemu-kvm -name 112BLKWIN732IVU -enable-kvm -m 2G -smp 2 -uuid 2195975f-db0b-4cee-90d3-ae0399fab204 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/tmp/112BLKWIN732IVU,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=112BLKWIN732IVU,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_7_ultimate_with_sp1_x86_dvd_u_677460.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=112BLKWIN732IVU.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:29:0a:30:f9,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 -object iothread,id=thread0 -drive file=112BLKWIN732IVU_test.raw,if=none,id=drive-virtio-disk0,format=raw,serial=mike_cao,cache=none -device pci-bridge,id=bridge1,chassis_nr=1,bus=pci.0 -device virtio-blk-pci,iothread=thread0,scsi=off,bus=bridge1,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0 -monitor stdio 2.install viostor driver Actual results: occured driver while install Expected results: install succesfully Additional info: After install, the driver shows yellow ! in device manager , then reboot the guest, it will boot the startup repair, cannot boot to the guest anymore