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.
Description of problem:
I have installed the 4.1-12 build and when I install the USBdk for Win7, upon reboot after I install the USBdk, I have NO mouse or keyboard and can do nothing because I can't login. I can use the virt-viewer without issue. This is only when I install the client-side Usb-Dk.
When I press F8 to start in Safe Mode, I can't since the PC opens the Windows Error Recovery screen where I can Launch Startup Repair or Start Windows Normally.
I did the Launch Startup Repair and got back to using Windows, but the UsbDk was not working on the client since I could not redirect the USB from client to guest.
Version-Release number of selected component (if applicable):
Windows 7x64
RHEL 7.3z
rhv-4.1.0-12
virt-viewer 2.0-208
spice-client-msi-x64-4.1-4.el7ev.noarch
How reproducible:
100%
Steps to Reproduce:
1. See above.
2.
3.
Actual results:
Expected results:
Additional info:
Bill could it be the same issue as: https://bugzilla.redhat.com/show_bug.cgi?id=1308634 ?
There is a notice:
To prevent connection failure with local USB devices on a Windows 7 client machine, update the Windows machine with Microsoft Security Update KB3033929 before installing the USB Development Kit Driver (spice-usbdk-win). Failure to apply this update before installing the spice-usbdk-win driver otherwise results in USB connection loss and an error reporting an unsigned driver.
It is necessary to install at least https://technet.microsoft.com/en-us/library/security/3033929
I tried this USBDk version with fully updated Win7 client. USB devices are fully functional before and after client's reboot. It is probably matter of those Windows updates.