Red Hat Bugzilla – Bug 919166
Two instances of virt-viewer running at the same time causes USB redir to misbehave.
Last modified: 2015-09-22 09:09 EDT
Description of problem: Two instances of virt-viewer running at the same time causes USB redir to misbehave. If the virt-viewer instance of a VM where USB device is to be redirected is launched as first one (and then another virt-viewer instance to different VM is launched) then an error is printed: USB redirection error: Could not auto-redirect: Kingston Technology Device [0951:162d] at 1-3: Could not open device: Operation not supporyed or unimplemented on this platform [-12] If It's opposite scenarion an error about insufficient permission is displayed. I does work when I close one of the virt-viewer windows. Version-Release number of selected component (if applicable): usbclerk-win-0.1-10 WindowsXP/7 client and Windows 7 guest. How reproducible: always Steps to Reproduce: 1. Open a spice session to a VM using mingw-virt-viewer. 2. Open another one to a different VM. 3. Try to redirect an USB device. Actual results: An error displayed. Expected results: Redirected USB device. Additional info:
Is usb auto-share enabled ? Can this be reproduced when auto-share is disabled ?
(In reply to Uri Lublin from comment #2) > Is usb auto-share enabled ? > Can this be reproduced when auto-share is disabled ? It does not matter autohare is enabled or disabled, I can reproduce on WinXP and Win7 64 bit clients connecting to two different VMs through RHEVM3.2, I am not able to redirect USB device at all unless I close one of the remote-viewer instance.
The problem seems to be on the client side. Moving to mingw-virt-viewer.
patch on the ML & ack: http://lists.freedesktop.org/archives/spice-devel/2013-August/014186.html
This bug is currently attached to errata RHEA-2013:15512. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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. http://rhn.redhat.com/errata/RHBA-2014-0034.html