[Fedora-xen] W2K CD installation error on guest

[Jimison, Ed]

Bingo! SELinux was set to Enforcing. That resolved the issue. Now the
next roadblock is that the guest mouse appears hung when I get to the
point in the install where I need to click Next on the "Regional and
Language Options" dialog box. Have you ever seen this one?

-----Original Message-----
From: Chris Lalancette [mailto:clalance at redhat.com] 
Sent: Monday, December 04, 2006 11:03 AM
To: Jimison, Ed
Cc: Andrew Cathrow; fedora-xen at redhat.com
Subject: Re: [Fedora-xen] W2K CD installation error on guest

Jimison, Ed wrote:
> Unfortunately it's the same error as below. The file is definitely
there.
> 
>       Error: Disk image does not exist: /home/w2k3.iso
> 
>  
> 
>
------------------------------------------------------------------------
> 
> *From:* Andrew Cathrow [mailto:acathrow at redhat.com]
> *Sent:* Monday, December 04, 2006 10:33 AM
> *To:* Jimison, Ed
> *Cc:* fedora-xen at redhat.com
> *Subject:* RE: [Fedora-xen] W2K CD installation error on guest
> 
>  
> 
> The dd command is the issue,it's not going to produce a valid image.
> Youlre seeking 4096k and reading one block.
> Just do dd if=/dev/cdrom of=myimage.iso
> 
> 
> On Mon, 2006-12-04 at 10:12 -0800, Jimison, Ed wrote:
> 
> Thanks, Andrew. I've been going this direction with no success. Here's
> what I've done so far:
> 
>  
> 
>    1. Copy CD ISO to Fedora system
> 
> 
>       dd if=/dev/cdrom of=/home/w2k3.iso bs=1024 seek=4096k count=1
> 
>  
> 
>    1. Edit config file /etc/xen/w2k3virt1
> 
> 
>       disk = [ 'file:/xen/w2k3virt1,hda,w',
> 'file:/home/w2k3.iso,hdc:cdrom,r', ]
> 
>    1. xm create -c w2k3virt1
> 
> 
>       Error: Disk image does not exist: /home/w2k3.iso
> 

<snip>

Besides the problem with the dd (which it seems like you remedied now),
this smells like an SELinux issue.  Do you have SELinux enabled (i.e.
run "getenforce")?  Are there any messages in /var/log/audit/audit.log
or /var/log/messages saying that the read was denied?  If SELinux is
indeed enabled, as a test try disabling it by running "setenforce 0",
and then starting the install again.

Chris Lalancette