Mailing List Archive

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@lists.xensource.com
http://lists.xensource.com/xen-users

Should be as simple as...

mkinitrd /boot/nameofmy.img 2.6.11-1.1369_FC4xen0

Hope this helps.
John Fairbairn

> Hi
>
> How do I make an initrd for xen.
>
> I'm trying to boot rhel3 in fc4, and it keeps getting stuck at
>
> Freeing unused kernel memory.
>
> I've created the device files, but it still doesn't boot up. I'm
> pretty sure that the solution lies in makeing an initrd file.
> Currently my xenU kernel is 2.6.11-1.1369_FC4xen0. Can someone please
> tell me how to do this?
>
> Many Thanks
> Shaz
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>



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

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@virgin.net> 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@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

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@virgin.net> 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@lists.xensource.com
>> http://lists.xensource.com/xen-users
>>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>



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

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@proteus2.com> 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@virgin.net> 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@lists.xensource.com
> >> http://lists.xensource.com/xen-users
> >>
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

> 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 2.0 is one compatibility series, Xen 3.0 is another. FC4's Xen (and Xen
tools) is part of the 3.0 series, so you can't run a Xen 2.0 guest kernel on
it.

What you need is to grab the Xen source code for a Xen 3.0 2.4 guest kernel.
Try downloading the unstable binary tarball, boot 2.4 and see if that works.

Cheers,
Mark

> "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@proteus2.com> 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@virgin.net> 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@lists.xensource.com
> > >> http://lists.xensource.com/xen-users
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@lists.xensource.com
> > > http://lists.xensource.com/xen-users
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

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

Hi Mark,

Thanks for the reply.

I downloaded it. I guess I need to compile it. Is there any simple
document available that describes how to compile and install this?

I don't mind using the 2.06 version. Is there a way to get this
working under FC4?

Many Thanks
Shaz

On 7/1/05, Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote:
> > 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 2.0 is one compatibility series, Xen 3.0 is another. FC4's Xen (and Xen
> tools) is part of the 3.0 series, so you can't run a Xen 2.0 guest kernel on
> it.
>
> What you need is to grab the Xen source code for a Xen 3.0 2.4 guest kernel.
> Try downloading the unstable binary tarball, boot 2.4 and see if that works.
>
> Cheers,
> Mark
>
> > "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@proteus2.com> 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@virgin.net> 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@lists.xensource.com
> > > >> http://lists.xensource.com/xen-users
> > > >
> > > > _______________________________________________
> > > > Xen-users mailing list
> > > > Xen-users@lists.xensource.com
> > > > http://lists.xensource.com/xen-users
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@lists.xensource.com
> > > http://lists.xensource.com/xen-users
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
>

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

Hi

Just to add to my previous post. I did download the binary version but
all thats available in the /boot directory is the 2.6 kernel. The 2.4
kernel isn't there.

Any ideas how to get the 2.4 kernel binary?

Thanks
Shaz

On 7/1/05, Shahzad Chohan <shahzad.chohan@gmail.com> wrote:
> Hi Mark,
>
> Thanks for the reply.
>
> I downloaded it. I guess I need to compile it. Is there any simple
> document available that describes how to compile and install this?
>
> I don't mind using the 2.06 version. Is there a way to get this
> working under FC4?
>
> Many Thanks
> Shaz
>
> On 7/1/05, Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote:
> > > 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 2.0 is one compatibility series, Xen 3.0 is another. FC4's Xen (and Xen
> > tools) is part of the 3.0 series, so you can't run a Xen 2.0 guest kernel on
> > it.
> >
> > What you need is to grab the Xen source code for a Xen 3.0 2.4 guest kernel.
> > Try downloading the unstable binary tarball, boot 2.4 and see if that works.
> >
> > Cheers,
> > Mark
> >
> > > "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@proteus2.com> 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@virgin.net> 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@lists.xensource.com
> > > > >> http://lists.xensource.com/xen-users
> > > > >
> > > > > _______________________________________________
> > > > > Xen-users mailing list
> > > > > Xen-users@lists.xensource.com
> > > > > http://lists.xensource.com/xen-users
> > > >
> > > > _______________________________________________
> > > > Xen-users mailing list
> > > > Xen-users@lists.xensource.com
> > > > http://lists.xensource.com/xen-users
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@lists.xensource.com
> > > http://lists.xensource.com/xen-users
> >
>

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

Hi

Just repeating my help regarding if any one can help with finding the
2.4 kernel for xen 3.0?

The unstable binary version only has the 2.6 kernel?

Thanks
Shaz

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