Bug 1309634
Summary: | "usb-filter" field of vv-file is ignored | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Uri Lublin <uril> | |
Component: | virt-viewer | Assignee: | Virt Viewer Maint <virt-viewer-maint> | |
Status: | CLOSED ERRATA | QA Contact: | SPICE QE bug list <spice-qe-bugs> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 7.3 | CC: | dblechte, fidencio, juzhou, mxie, mzhan, pgrunt, rbalakri, tpelka, tzheng, xiaodwan | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | virt-viewer-2.0-7.el7 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1327525 (view as bug list) | Environment: | ||
Last Closed: | 2016-11-04 01:14:29 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1327525 |
Description
Uri Lublin
2016-02-18 10:59:57 UTC
Just for the record, the commit that solves the issue is: 7a54b96dbebfeb44f73a3e48e11f32006763a3b6 I can reproduce it with virt-viewer-2.0-6.el7.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=5901 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: The usb device pops up in the guest. Then updated to latest virt-viewer-2.0-7.el7.x86_64 and retested it again. The usb device cannot pop up. Set the usb-filter to "usb-filter=-1,-1,-1,-1,1" and replug the usb device, it can pop up successfully. So it is fixed and move it from ON_QA to VERIFIED. 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-2016-2229.html |