Bug 1327525 - "usb-filter" field of vv-file is ignored
Summary: "usb-filter" field of vv-file is ignored
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-viewer
Version: 6.8
Hardware: x86_64
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: Eduardo Lima (Etrunko)
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1309634
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-15 10:02 UTC by Xiaodai Wang
Modified: 2017-03-21 09:18 UTC (History)
15 users (show)

Fixed In Version: virt-viewer-2.0-15.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 1309634
Environment:
Last Closed: 2017-03-21 09:18:43 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0587 0 normal SHIPPED_LIVE libgovirt, rest, spice-gtk, and virt-viewer bug fix and enhancement update 2017-03-21 12:24:45 UTC

Comment 6 Xiaodai Wang 2016-12-07 07:51:15 UTC
I verified it with virt-viewer-2.0-17.el6.x86_64.

Steps:
1. Prepare a guest and a ini file and set the "usb-filter=-1,-1,-1,-1,0" to forbid any usb device.

# cat b.ini
[virt-viewer]
type=spice
host=localhost
port=5900
enable-usbredir=1
enable-usb-autoshare=1
usb-filter=-1,-1,-1,-1,0

2. Run "remote-viewer b.ini" to connect to the guest.
3. Plug a usb device into the host device.

Acutal Result:
No usb device pops up in the guest.

then modifiy usb-fileter to "usb-filter=-1,-1,-1,-1,1", open the guest and plug a usb device again.
The usb device can pop up successfully.

So it is fixed and move it from ON_QA to VERIFIED.

Comment 8 errata-xmlrpc 2017-03-21 09:18:43 UTC
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.

https://rhn.redhat.com/errata/RHBA-2017-0587.html


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