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:
Currently, usbdk-enabled virt-viewer can't leverage usbclerk/winusb code path for usb redirection when usbdk driver is not available. It may or may not be worthwhile to fall back to the old code path when that happens.
It may be also worthwhile to CLOSE/WONTFIX this as winusb solution has inferior features to usbdk so it might lead to support cases along the lines of "webcam not redirecting with RHEV $target_release" because people'd be accessing their setup with non-updated virt-viewer and usbdk... This either/or approach would however need usbdk to supersede usbclerk somehow (RPM's "Obsoletes:" equivalent) so it doesn't interfere or event take system resources...
What do you think?
Version-Release number of selected component (if applicable):
usbdk v0.02-1
Actually current version of usbdk-enabled virt-viewer does fall back to winusb in case UsbDk is not installed - this is what we call dynamic backend selection.
This approach is temporary solution in order to have the same binaries for testing and for production. As soon as UsbDk becomes stable enough for production this logic will be dropped altogether with winusb-related code path.
(In reply to Dmitry Fleytman from comment #1)
> Actually current version of usbdk-enabled virt-viewer does fall back to
> winusb in case UsbDk is not installed - this is what we call dynamic backend
> selection.
>
Then this bug means that the fallback doesn't work. :)
> This approach is temporary solution in order to have the same binaries for
> testing and for production. As soon as UsbDk becomes stable enough for
> production this logic will be dropped altogether with winusb-related code
> path.
OK
Created attachment 942687[details]
virt-viewer log
Still doesn't work for me. The machine is recycled 32b win 7:
1. uninstall usbclerk & virt-viewer
2. install usbdk-enabled virt-viewer, restart
3. make sure that usbclerk is up & running
4. connect to a VM, plug some devices
the result is in the log (errors -1 and -12)
Actually, the problem may be in the legacy usb itself. I've seen today some issues with legacy USB in virt-viewer 0.6.0 on a system that has never seen usbdk or related patches to remote-viewer.
Comment 6pgurvich@redhat.com
2014-10-05 09:35:02 UTC
For dynamic choosing of windows backend spice-gtk module should be compiled with enable-winusb=yes
(mingw32-configure --with-gtk=2.0 --enable-vala --enable-winusb=yes)