Bug 1415176 - USB (interruption) problem using KVM-Switch
Summary: USB (interruption) problem using KVM-Switch
Keywords:
Status: NEW
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virt-viewer
Version: unspecified
Hardware: x86_64
OS: Windows
unspecified
medium
Target Milestone: ---
Assignee: Daniel Berrangé
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-20 13:12 UTC by dimi.vitric
Modified: 2018-07-18 15:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description dimi.vitric 2017-01-20 13:12:46 UTC
Description of problem:
While the guest window (remote-viewer) has focus (doesn't matter if mousepointer is catched or not), at least one USB-port (mouse from the KVM-switch) will get locked after switching between computers with a hardware KVM-switch.
Keyboard remains accessible within the VM, but not so the mouse. If the VM is being shutdown and viewer window gets closed, one more switching will make the mouse work again. This was not an issue in Version 3.1.
Switching back several times while the guest window has focus, will lock ALL USB-ports (controller?) within the originating system (you won't hear Windows sounds anymore for (re-)attaching devices, whatever port you will use)!

Version-Release number of selected component (if applicable):
v5.0-256 (x64), On windows 10 Pro 64bit

How reproducible:
Every time

Steps to Reproduce:
1. Connect to guest using remote-viewer
2. Focus guest window
3. Switching forth and back computers with a USB-KVM-Switch

Actual results:
The mouse remains not usable anymore after switching the first time.
No more USB ports will be accessible after switching at least one or two more times.

Expected results:
If Windows looses connection to (USB) mouse/keyboard, the remote-viewer / guest should get noticed about this to detach mouse/keyboard properly? USB-ports should work in any way.

Additional info:


Note You need to log in before you can comment on or make changes to this bug.