Bug 598668 - virt-manager: permission errors trying to use ISO
Summary: virt-manager: permission errors trying to use ISO
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-01 20:03 UTC by Frederik Hertzum
Modified: 2010-08-27 14:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-27 14:36:10 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Frederik Hertzum 2010-06-01 20:03:01 UTC
Description of problem:
Using a Qemu connection virtmanager always hijacks ISO9660 files, giving ownership to the qemu user and group. After having done so the file is reported as being unreadable by qemu and virt-manager is then unable to use it. Using Qemu directly, i.e. not using virt-manager, allows reading the file, as it should be.

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

How reproducible:

Steps to Reproduce:
1. Setup a new virtual machine in virt-manager and configure it to boot from an ISO file.
2. Finish the installation.
3. Sit back and relax.
Actual results:
Virt-manager hijacks the ISO file and then refuses to read the file afterwards -- reporting insufficient rights.

Expected results:
Virt-manager should start the virtual machine and (try to) boot from the file.

Additional info:

Comment 1 Cole Robinson 2010-08-21 21:41:24 UTC
Please provide ~/.virt-manager/virt-manager.log, or the output of a run with virt-manager --debug

It's actually libvirt that is change the permissions of the file, but it does so to allow qemu to run, not break things. Is the ISO stored on NFS or similar? Does doing 'setenforce 0' make things work? Could be an selinux issue at work.

Comment 2 Frederik Hertzum 2010-08-27 14:20:16 UTC
SELinux was disabled already so setenforce wouldn't change anything :-)

The file was on a local, regular, ext4 partition. Anyway, the problem appears to have disappeared.

Comment 3 Cole Robinson 2010-08-27 14:36:10 UTC
Okay, closing as WORKSFORME, but please reopen if the issue reappears.

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