Bug 1370170

Summary: SELinux policy denies access when starting domain
Product: [Fedora] Fedora Reporter: Michael Lipp <mnl>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: agedosier, berrange, clalancette, crobinso, itamar, laine, libvirt-maint, mnl, veillard, virt-maint
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-25 13:28:27 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:

Description Michael Lipp 2016-08-25 12:44:58 UTC
Description of problem:

After my update to Fedora 24, I can no longer start a domain.

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

libvirt (etc.) 1.3.3.2-1

How reproducible:

Always. 

Steps to Reproduce:
1. Click in Start or enter "virsh start domain"

Actual results:

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 88, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 124, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 83, in newfn
    ret = fn(self, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1404, in startup
    self._backend.create()
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1035, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: SELinux policy denies access.

Expected results:

Domain starts

Additional info:

"setenforce 0" can be used as a workaround.

Comment 1 Cole Robinson 2016-08-25 13:28:27 UTC

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