Bug 1265189 - Can not start VM after updating selinux-policy
Summary: Can not start VM after updating selinux-policy
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 22
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-22 10:58 UTC by Tomáš Hozza
Modified: 2015-09-25 07:55 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-25 07:55:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tomáš Hozza 2015-09-22 10:58:30 UTC
Description of problem:
I can not start VM after updating selinux-policy

Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-128.13.fc22.noarch
virt-manager-1.2.1-2.fc22.noarch

How reproducible:
always

Steps to Reproduce:
1. start VM in virt-manager

Actual results:
Error from virt-manager

Error starting domain: SELinux policy denies access.

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, 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 1423, in startup
    self._backend.create()
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1007, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: SELinux policy denies access.

Expected results:
no error

Comment 1 Daniel Walsh 2015-09-22 13:02:36 UTC
Any AVC messages?

ausearch -m avc, user_avc -ts recent

Comment 2 Miroslav Grepl 2015-09-23 16:07:12 UTC
Could you also try to reload libvirtd?

Comment 3 Tomáš Hozza 2015-09-24 07:12:03 UTC
Unfortunately after rebooting everything works also in Enforcing mode. Therefore I can not provide further information. Feel free to close this Bug. I'll reopen if I have some useful information.

Thank you.

Comment 4 Miroslav Grepl 2015-09-25 07:55:17 UTC
I believe it releates with SELinux class changes and SELinux aware apps. Reboot fix it and we have fixes in the latest f22 update.


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