Bug 713390 (spice_usb_filter_editor) - [RFE] Edit USB Filters manually
Summary: [RFE] Edit USB Filters manually
Keywords:
Status: CLOSED WONTFIX
Alias: spice_usb_filter_editor
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: ---
: ---
Assignee: Balakrishnan, Radhesh
QA Contact: Gil Klein
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-15 09:35 UTC by Michal Haško
Modified: 2016-11-29 11:23 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-29 11:23:44 UTC
oVirt Team: Virt
ylavi: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)
lsusb --verbose of the device (6.85 KB, text/plain)
2011-06-15 09:35 UTC, Michal Haško 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Michal Haško 2011-06-15 09:35:12 UTC 
Created attachment 504832 [details]
lsusb --verbose of the device

Description of problem:
If one tries to create a USB Filter for a modern device, there is a great chance it is not present in the Product ID list in the USB Filter Editor.

Therefore it would be very useful if user was allowed to edit the fields (USB Class, Vendor Id, Product Id, Revision) manually.

Example of such device: HP Officejet 6500
USB Class:  0x00
Vendor Id:  0x03f0
Product Id: 0x5512
Revision:   0x0000

Happens in RHEVM 2.2.7
Comment 1 Andrew Cathrow 2011-06-27 17:43:00 UTC 
We need to provide a UI for USB filter editing, that will probably wait for our 3.1 solution with spice based USB redirection
Comment 4 David Blechter 2015-08-21 19:51:44 UTC 
Spiec provides the USB redirection and don't own the Editor. Moving to RFEs for RHEVM PM to define the priority and allocate resources
Comment 5 Moran Goldboim 2016-11-29 11:23:44 UTC 
closing this bug. if relevant from customer perspective please reopen.
Note You need to log in before you can comment on or make changes to this bug.