[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] How to make an initrd for xen


  • To: John Fairbairn <webmaster@xxxxxxxxxxxx>
  • From: Shahzad Chohan <shahzad.chohan@xxxxxxxxx>
  • Date: Fri, 1 Jul 2005 14:43:11 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 01 Jul 2005 13:42:04 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kjHlrzG7XunD4T+3RKCZP9ilRcP6r8dRv6nuD+3Qn8+CN8TpPxB0QiKQwQJIvE6wxWwqFM8zeBioUxzOo/3ycz+1LglPb1I5WTuU9DCr+4ogJ8oPTCdzXi1d4FXripUCOk89KK1ZhzArj/Pz2v2IZ803aWp0erMeo+eUJIfUGBc=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi yep,

I've started from scratch again, cos I got fustrated with it.
Basically I'm now trying to run the 2.4 kernel on FC4. I got the
kernel from the xen site i.e 2.06. the problem is that it won't boot.
It keeps crashing saying something like

"Xen will only boot images made for xen 3.0"

Here's what I did

Currently I am running fedora core 4 with kernel 2.6.11-1.1369_FC4xen0

mkinitrd /boot/initrd-2.4.30_xen0.img 2.4.30-xen0

I then added this to /etc/grub.conf
title Xen  (2.4.30-xenU)
        root (hd0,0)
        kernel /xen.gz dom0_mem=150000
        module /vmlinuz-2.4-xen0 ro root=LABEL=/
        module /initrd-2.4.30_xen0.img

and then reboot.

Any idea where the problem is?

Thanks
Shaz


On 7/1/05, John Fairbairn <webmaster@xxxxxxxxxxxx> wrote:
> Just a thought,
> 
> did you make sure to add an extra module line to your grub.conf...
> example dom0 booting from initrd....
> 
> title Xen 2.0 / XenLinux 2.6.11-7
>         kernel /boot/xen.gz dom0_mem=256000 console=vga
>         module /boot/vmlinuz-2.6.11-xen0 root=/dev/hda2 ro console=tty0
>         module /boot/initrd-2.6.11-xen0.img
> 
> without the last module line it wont work :)
> 
> Hope this helps ya.
> John Fairbairn
> 
> 
> > Many Thanks for all your replies.
> >
> > I did this but it sill doesn't boot up rhel 3. I'm kind of new to this
> > initrd area, I thin the issue relates to FC4 running a 2.6 kernel
> > while rhel 3 runs a 2.4 kerenl. Am I right?
> >
> > If this is the case how can I make an initrd for the 2.4 kernel from FC4.
> >
> > Many Thanks
> > Shaz
> >
> > On 6/30/05, Jon Howse <jonny.fahrenheit451@xxxxxxxxxx> wrote:
> >> You need the xenU kernel installed as well as the xen0 kernel and then
> >> you need to do:-
> >>
> >> touch /lib/modules/2.6.11-1.1369_FC4xenU/modules.dep
> >> This creates a file called modules.dep in specified directory. mkinitrd
> >> will complain if this file does not exist!
> >>
> >> then:-
> >>
> >> /sbin/mkinitrd /boot/initrd-2.6.11-1.1369xenU.img 2.6.11-1.1369_FC4xenU
> >>
> >> The filename you specify for the initrd can be anything but notice I've
> >> specified it to be in the /boot directory and descriptive of the kernel
> >> version.
> >>
> >> The last argument is the kernel version you want to make an initrd from.
> >> We want this to be the kernel we will be using in our guest domain(your
> >> EL3 machine).
> >>
> >> This will create an initrd that you can specify in your domain config
> >> file for your EL3 virtual machine.
> >>
> >> I have done this many times under Fedora, you should have no problems
> >> with this technique.
> >>
> >> Jonny
> >>
> >>
> >> _______________________________________________
> >> Xen-users mailing list
> >> Xen-users@xxxxxxxxxxxxxxxxxxx
> >> http://lists.xensource.com/xen-users
> >>
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.