Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1044413

Summary: virt-manager can't boot from ISO on readonly NFS - unable to set security context
Product: Red Hat Enterprise Linux 7 Reporter: Martin <mholec>
Component: virt-managerAssignee: virt-mgr-maint
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.0CC: gscrivan, tpelka
Target Milestone: rc   
Target Release: 7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-18 12:06:55 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:
Embargoed:

Description Martin 2013-12-18 09:31:53 UTC 
Description of problem:
virt-manager can't boot from ISO on readonly NFS
Unable to complete install: 'unable to set security context 'system_u:object_r:virt_content_t:s0'

Version-Release number of selected component (if applicable):
virt-manager-0.10.0-7.el7.noarch
selinux-policy-3.12.1-103.el7.noarch
selinux-policy-targeted-3.12.1-103.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. Create a new VM, select local media install.
2. Add ISO on read-only NFS as installation source.
3. Finish VM setup.

Actual results:
Unable to complete install: 'unable to set security context 'system_u:object_r:virt_content_t:s0' on '/mnt/globalsync/fedora/linux/releases/19/Fedora/x86_64/iso/Fedora-19-x86_64-DVD.iso': Read-only file system'

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 100, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/create.py", line 1920, in do_install
    guest.start_install(False, meter=meter)
  File "/usr/share/virt-manager/virtinst/Guest.py", line 1143, in start_install
    noboot)
  File "/usr/share/virt-manager/virtinst/Guest.py", line 1211, in _create_guest
    dom = self.conn.createLinux(start_xml or final_xml, 0)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2892, in createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: unable to set security context 'system_u:object_r:virt_content_t:s0' on '/mnt/globalsync/fedora/linux/releases/19/Fedora/x86_64/iso/Fedora-19-x86_64-DVD.iso': Read-only file system
Comment 1 Giuseppe Scrivano 2013-12-18 12:06:55 UTC 

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