Re: [Xen-users] install Fodera 6 on Xen - stop copying files during the installation

[jez <jez@xxxxxxxxxx>]

On Wed, Mar 07, 2007 at 06:03:14PM -0800, xin wrote:
> 
> Hi, I changed the selinux = disable in /etc/sysconfig/selinux file and reboot
> system, then creat a new domain guest fc6 system again. I got the same
> problem, the installation stops at:
>                             
> ------------------------------------------------
>                                         Install Starting
>                                 Starting install process.  This may
>                                 take several minutes...
>                             
> -------------------------------------------------
> 

... or hours, days. Maybe even years. 

See, problem solved - it was just an output error. :-)


> nothing in /var/log/message and /var/log/xend-debug, I found something in
> /var/log/xend as below:
> 
> [2007-03-08 19:47:32 xend 2466] DEBUG (balloon:127) Balloon: 310204 KiB
> free; need 262144; done.
> [2007-03-08 19:47:32 xend 2466] INFO (image:136) buildDomain os=linux dom=1
> vcpus=1
<snip/>

I can't see anything strange in these logs. It looks to me like the
problem is with Fedora's tools rather than with xen. 

> 
> I was trying to access the image file to see if there are some logs during
> the installation in that image file. however,
> lomount -t ext3 -diskimage /var/lib/xen/images/imageStimpy -partition 2
> /mnt/xenstimpy
>  lomount says bad filesystem type. ?! 

If LVM is being used by Fedora then your not going to be able to mount
your filesystem like that. To see how Fedora paritioned your image
you can do: 

    fdisk -l /var/lib/xen/images/imageStimpy

Anyway, from what you've said so far, I really doubt that there will be 
any clues in your fs image to explain the problem you've been having.

> But I can mount partition 1, and there is only one directory in there which
> is "lost+found".......
> 

This is most likely supposed to be your /boot parition. There's nothing
strange about the "lost+found" directory - all ext2 and ext3 partitions
have one. The fact that you can access this parition just suggests that
Fedora managed to paritition the image, but froze before it put any
files in there. Which is exactly what you thought happened anyway.

Sounds like a problem with Fedora's Installer. You might have some 
luck getting help on the Fedora-xen mailling list: 

    http://www.redhat.com/mailman/listinfo/fedora-xen

It's worth a try!


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users