Bug 221837 - Error using .iso file for new domain creation
Summary: Error using .iso file for new domain creation
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 6
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Daniel Berrangé
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-01-08 14:28 UTC by Adam Huffman
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-09-27 21:06:28 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
xend log showing error with new domain creation (3.91 KB, application/octet-stream)
2007-04-19 17:22 UTC, Adam Huffman 		no flags Details
View All

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....
Note You need to log in before you can comment on or make changes to this bug.