Description of problem: Let's drop Legacy USB altogether: * it was by no means reliable nor secure * it was superseded by UsbDk that was already shipped in 3.6 * its vendor support expired years ago * its both components had limited OS support and those OSs are ageing and falling out of use * it depends on browser plug-ins that are being phased out There are three places with Legacy USB(-related) code: * engine (drop Legacy option of USB redirection and associated code) * windows guest tools (drop USB driver) * client (menu over socket/named pipe) Version-Release number of selected component (if applicable): 3.6 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
hide in UI (change USB policy to USB enabled/disabled) then remove obsolete code later on. existing VMs still using Legacy should be converted to Native. It should be ok to change all the VMs as 3.6 already supports UsbDk
(In reply to Michal Skrivanek from comment #1) > hide in UI (change USB policy to USB enabled/disabled) then remove obsolete > code later on. > existing VMs still using Legacy should be converted to Native. It should be > ok to change all the VMs as 3.6 already supports UsbDk under the same RFE I suggest to drop the usb-clerk support, and remove it from windows client RPM.
found that 1328916 is the dupl. for dropping usb-clerk support
out of time for 4.0 we will just declare it as deprecated in 4.0 and remove in next release
verified on : Red Hat Virtualization Manager Version: 4.1.1.4-0.1.el7 verification steps: 1. make sure USB policy to changed to enabled/disabled 2. verify our test cases support it. (test cases are attached)