Bug 444137 - libvirtd/qemu prevented from accessing images in /var/lib/libvirt/image
libvirtd/qemu prevented from accessing images in /var/lib/libvirt/image
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-04-25 07:43 EDT by Alexander Boström
Modified: 2008-04-25 08:56 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-04-25 08:56:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alexander Boström 2008-04-25 07:43:37 EDT
Description of problem:
When creating a qemu/KVM machine using virt-manager and creating a new disk
image in /var/lib/libvirt/image, qemu can't access the new image and SELinux
logs this:

SELinux is preventing qemu-system-x86 (virtd_t) "getattr" to
/var/lib/libvirt/images/test.img (virt_image_t). 

Labelling looks correct:

-rwxrwxr-x  root root unconfined_u:object_r:virt_image_t:s0
/var/lib/libvirt/images/test.img

Version-Release number of selected component (if applicable):
libvirt-0.4.2-1.fc9.x86_64
qemu-0.9.1-5.fc9.x86_64
virt-manager-0.5.4-3.fc9.x86_64
selinux-policy-targeted-3.3.1-35.fc9.noarch
selinux-policy-3.3.1-35.fc9.noarch

How reproducible:
Always.

Steps to Reproduce:
1. Install F9 preview, yum update.
2. Log in, start virt-manager.
3. Create a new virtual machine with disk image in /var/lib/libvirt/image

Additional info:
When trying to use a LVM volume I have the same problem, even though the block
device /dev/mapper/VolGroup01-LogVolSomething is labelled
system_u:object_r:virt_image_t:s0.
Comment 1 Daniel Walsh 2008-04-25 08:56:52 EDT
Fixed in selinux-policy-3.3.1-42.fc9

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