Bug 221837

Summary: Error using .iso file for new domain creation
Product: [Fedora] Fedora Reporter: Adam Huffman <bloch>
Component: virt-managerAssignee: Daniel Berrangé <berrange>
Status: CLOSED NOTABUG QA Contact: Martin Jenner <mjenner>
Severity: medium Docs Contact:
Priority: medium    
Version: 6CC: xen-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-09-27 21:06:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
xend log showing error with new domain creation none

Description Adam Huffman 2007-01-08 14:28:48 UTC 
Description of problem:
When using virt-manager to create a new para-virtualized domain, virt-manager
stops with an error at the final step, relating to the .iso file used for
installation:

ERROR: virDomainCreateLinux() failed POST operation failed: (xend.err 'Error
creating domain: Disk image does not exist: /opt/xen/xpincsp2.iso')

Version-Release number of selected component (if applicable):
0.2.6-3.fc6

How reproducible:
Every time

Steps to Reproduce:
1. run virt-manager
2. begin new domain creation
3.
  
Actual results:
New domain creation stops with an error

Expected results:
New domain creation proceeds normally

Additional info:
Comment 1 Adam Huffman 2007-04-19 17:21:20 UTC 
Just encountered this bug again - xend log file excerpt attached.
Comment 2 Adam Huffman 2007-04-19 17:22:20 UTC 
Created attachment 153029 [details]
xend log showing error with new domain creation
Comment 3 Red Hat Bugzilla 2007-07-25 02:07:18 UTC 
change QA contact
Comment 4 Daniel Berrangé 2007-09-27 21:06:28 UTC 
Most likely reason for this failure is that SELinux was active. WHen SELinux is
active, ISO images have to be under /var/lib/xen/images/ to be accessible, so
/opt would likely give an access violation. Re-open this ticket if SELinux
wasn't the problem....