Michael Weiner wrote:
> On 3/19/07, Steve Brueckner <steve@xxxxxxxxxxxxxx> wrote:
>
> Michael Weiner wrote:
> > On 3/19/07, Steve Brueckner <steve@xxxxxxxxxxxxxx> wrote:
> >
> > Daniel P. Berrange wrote:
> > > On Mon, Mar 19, 2007 at 11:16:48AM -0400, Michael Weiner
> wrote: > >> Xen readers -
> > >>
> > >> Been trying to get xen working on FC6 for some time now,
> and i am > not >> sure what i am doing wrong - last time i
> played with xen it > was v2 >> and didnt seem to be this
> difficult to get working. > >
> > > You've not provided any initrd.
> >
> > Yes, initrd's can be a pain with Fedora.
> >
> > >> pretty generic, and when i go to fire it up with 'xen
> create > >> debian-3.1.cfg-c' it starts up and runs for a few
> moments then > dies, >> leaving the following in the log file:
> > >
> > > The system logs generally don't contain any useful
> information > > relating to Xen. You should instead look at
> the Xen logs - > > /var/log/xen/*
> >
> > You can also get more information to debug problems by
> launching with
> > a console (#xm create -c <domname>). This will show you the
> VM > booting, and you'll be able to see errors such as module
> failures > due to a lack of an initrd.
> >
> >
> > Thanks Steve, any possible pointers or URLs?
> >
> > Thanks
> > Michael
>
> Well here is how I built my initrd's for an older kernel
> (for what its worth):
>
> #mkinitrd -v -f -with=aacraid --with=sd_mod --with=scsi_mod \
> initrd-2.6.16.13-xen.img 2.6.16.13-xen
>
> #cp initrd-2.6.16.13-xen.img /boot
>
> Note that this isn't a Xen thing so much as a general Linux thing.
> Googling for initrd should help you out.
>
>
> Steve -
>
> Thanks for the information, I realize thats a linux thing, not a xen
> thing, as i used to have to create one in order to boot an old 440GX
> MB sometime ago. i DO however see these initrd's in /boot:
>
> initrd-2.6.19-1.2911.6.5.fc6xen.img
> initrd-2.6.19-1.2911.fc6xen.img
>
> so they are there. This may sound like a stupid question but where
> exactly am i using these? They are already called out in dom0's
> grub.conf. Sorry, i am a little confused here....
> Michael
Xen and intrd's confuse me as well. In the old days of Xen I used to
put this line into my domU config files:
ramdisk="/boot/initrd-2.6.16.13-xen.img"
However, I think Xen now detects the initrd automatically if it's in the
boot directory. Did you install Xen from source or using Fedora's rpms?
I always used to install from source since Fedora's rpms were broken more
often than not. So if your initrd's came via the rpm install you might
want to try remaking them yourself.
It's also possible that the initrd isn't the problem. If you boot using
a console as I suggested, you'll see where the VM bombs out, and you can
start tracking down the problem based on the error messages you see in
the console.
Steve Brueckner, ATC-NY
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home