Bug 574501

Summary: Error starting domain: unable to set security context after adding USB device to host
Product: [Fedora] Fedora Reporter: Orion Poplawski <orion>
Component: libvirtAssignee: Daniel Veillard <veillard>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 13CC: berrange, clalance, crobinso, itamar, jforbes, veillard, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-17 14:13:51 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Orion Poplawski 2010-03-17 13:04:36 EDT
Description of problem:

Added "Physical Host Device" -> USB -> Device 001:003 OEM Camera.  Listed as USB 046d:09b2 in hardware list.  Now when I try to start I get:

Error starting domain: unable to set security context 'system_u:object_r:svirt_image_t:s0:c436,c506' on '/dev/bus/usb/000/000': No such file or directory

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 589, in run_domain
  File "/usr/share/virt-manager/virtManager/domain.py", line 1208, in startup
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 317, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: unable to set security context 'system_u:object_r:svirt_image_t:s0:c436,c506' on '/dev/bus/usb/000/000': No such file or directory

Version-Release number of selected component (if applicable):

# ls -1 /dev/bus/usb/*/*

T:  Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#=  3 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=046d ProdID=09b2 Rev= 0.06
S:  Product=OEM Camera
Comment 1 Cole Robinson 2010-03-17 14:13:51 EDT

*** This bug has been marked as a duplicate of bug 574136 ***