OpenVZ Forum


Home » General » Support » GRUB Bootmanager
GRUB Bootmanager [message #31991] Wed, 16 July 2008 21:43 Go to next message
elturco is currently offline  elturco
Messages: 12
Registered: July 2008
Junior Member
Hii,

I want to make some changes to start Ubuntu with OpenVz kernel. I am a newbie and want to be sure that is right what i want to do.

I will change in the menu.lst the default entry from 0 to 5, because the openvz kernel is on place 5. Started to count the kernels from 0. And then I want to change the root entry to (hd0,5).

title Ubuntu 7.10, kernel 2.6.18-12-fza-686-bigmem
root (hd0,5)
kernel /boot/vmlinuz-2.6.18-12-fza-686-bigmem root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f ro quiet splash
initrd /boot/initrd.img-2.6.18-12-fza-686-bigmem
quiet

Is it right want I want to do ? Can anyone help me...
Re: GRUB Bootmanager [message #32002 is a reply to message #31991] Thu, 17 July 2008 07:51 Go to previous messageGo to next message
maratrus is currently offline  maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
Senior Member
Hi,

Quote:


I want to make some changes



Quote:


Is it right want I want to do ?



Smile.

Quote:


I will change in the menu.lst the default entry from 0 to 5, because the openvz kernel is on place 5.



It was not necessary to do. During the boot time you are able to chose appropriate kernel to boot via the boot menu interface. timeout - is an option that sets interval (in seconds) before bootloader tries to load the kernel which number corresponds the default option.


Quote:


And then I want to change the root entry to (hd0,5).



This action allows you to chose GRUB root file system, i.e. where GRUB can take vmlinuz and initrd files. (GRUB root file system is not the Linux root file system).
The common Linux root filesystem you want to use bootloadet obtains from this line
kernel /boot/vmlinuz-2.6.18-12-fza-686-bigmem [CODE]root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f[/CODE] ro quiet splash

Pay your attention to this
root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f


This string tells to bootloader that your common (Linux) root file system locates on the disk with appropriate UUID.

If you have any other questions don't hesitate to ask them.
Hope this helps you.

Re: GRUB Bootmanager [message #32005 is a reply to message #32002] Thu, 17 July 2008 08:37 Go to previous messageGo to next message
elturco is currently offline  elturco
Messages: 12
Registered: July 2008
Junior Member
Thank you very much..

Sorry I'm a newbie, the questions are maybe strange for you..

Did I understand you correctly, should I give this here
Quote:

kernel /boot/vmlinuz-2.6.18-12-fza-686-bigmem


as command, or do you mean that I should edit my Menu.lst with this parameters:
Quote:

kernel /boot/vmlinuz-2.6.18-12-fza-686-bigmem
root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f
ro quiet splash


Could you recommend to use the startupmanager ?

Thank you very very much again...

greetings,
Re: GRUB Bootmanager [message #32007 is a reply to message #32005] Thu, 17 July 2008 08:54 Go to previous messageGo to next message
maratrus is currently offline  maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
Senior Member
Hi,

I mean the following:

1. Most probably, you shouldn't change "root (hd0,5)" string in menu.lst file. Put it the same as the rest kernel have.

2. That's all. You shouldn't do anything else. Just reboot your node.

Quote:


Could you recommend to use the startupmanager ?


It's up to you I've never used it.

Re: GRUB Bootmanager [message #32011 is a reply to message #32007] Thu, 17 July 2008 09:37 Go to previous messageGo to next message
elturco is currently offline  elturco
Messages: 12
Registered: July 2008
Junior Member
I tried what you have mentioned before, but the openvz kernel that I have installed will not be loaded.

Here are the kernel on my machine:
title		Ubuntu 7.10, kernel 2.6.22-15-generic
root		(hd0,0)
kernel		/boot/vmlinuz-2.6.22-15-generic root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f ro quiet splash
initrd		/boot/initrd.img-2.6.22-15-generic
quiet

title		Ubuntu 7.10, kernel 2.6.22-15-generic (recovery mode)
root		(hd0,0)
kernel		/boot/vmlinuz-2.6.22-15-generic root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f ro single
initrd		/boot/initrd.img-2.6.22-15-generic

title		Ubuntu 7.10, kernel 2.6.22-14-generic
root		(hd0,0)
kernel		/boot/vmlinuz-2.6.22-14-generic root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f ro quiet splash
initrd		/boot/initrd.img-2.6.22-14-generic
quiet

title		Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root		(hd0,0)
kernel		/boot/vmlinuz-2.6.22-14-generic root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f ro single
initrd		/boot/initrd.img-2.6.22-14-generic

title		Ubuntu 7.10, kernel 2.6.18-12-fza-686-bigmem
root		(hd0,0)
kernel		/boot/vmlinuz-2.6.18-12-fza-686-bigmem root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f ro quiet splash
initrd		/boot/initrd.img-2.6.18-12-fza-686-bigmem
quiet

title		Ubuntu 7.10, kernel 2.6.18-12-fza-686-bigmem (recovery mode)
root		(hd0,0)
kernel		/boot/vmlinuz-2.6.18-12-fza-686-bigmem root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f ro single
initrd		/boot/initrd.img-2.6.18-12-fza-686-bigmem

title		Ubuntu 7.10, kernel 2.6.18-12-fza-686
root		(hd0,0)
kernel		/boot/vmlinuz-2.6.18-12-fza-686 root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f ro quiet splash
initrd		/boot/initrd.img-2.6.18-12-fza-686
quiet

title		Ubuntu 7.10, kernel 2.6.18-12-fza-686 (recovery mode)
root		(hd0,0)
kernel		/boot/vmlinuz-2.6.18-12-fza-686 root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f ro single
initrd		/boot/initrd.img-2.6.18-12-fza-686

title		Ubuntu 7.10, kernel 2.6.18-12-fza-486
root		(hd0,0)
kernel		/boot/vmlinuz-2.6.18-12-fza-486 root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f ro quiet splash
initrd		/boot/initrd.img-2.6.18-12-fza-486
quiet

title		Ubuntu 7.10, kernel 2.6.18-12-fza-486 (recovery mode)
root		(hd0,0)
kernel		/boot/vmlinuz-2.6.18-12-fza-486 root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f ro single
initrd		/boot/initrd.img-2.6.18-12-fza-486

title		Ubuntu 7.10, memtest86+
root		(hd0,0)
kernel		/boot/memtest86+.bin
quiet


My problem is, I dont how to say my bootmanager to load the openvz kernel.. Do you know what I mean ?
Re: GRUB Bootmanager [message #32013 is a reply to message #32011] Thu, 17 July 2008 10:24 Go to previous messageGo to next message
maratrus is currently offline  maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
Senior Member
Hi,

Quote:


I tried what you have mentioned before, but the openvz kernel that I have installed will not be loaded.



What does it mean?
You have rebooted the system, chosen OpenVZ kernel and what's happened after that?


Quote:


/boot/vmlinuz-2.6.18-12-fza-686-bigmem root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f ro single



why do you want to boot in single-mode?

P.S. try
/boot/vmlinuz-2.6.18-12-fza-686-bigmem root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f ro quiet splash
Re: GRUB Bootmanager [message #32014 is a reply to message #32013] Thu, 17 July 2008 11:00 Go to previous messageGo to next message
elturco is currently offline  elturco
Messages: 12
Registered: July 2008
Junior Member
Marartus the point ist, I dont know how to choose the OpenVz Kernel. Should I do it with command line or by editing the menu.lst file.

This is my question.


Is it right, that Ubuntu normally will always load the Kernel with the higher Version number ?
Re: GRUB Bootmanager [message #32016 is a reply to message #32014] Thu, 17 July 2008 11:15 Go to previous messageGo to next message
maratrus is currently offline  maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
Senior Member
Hi,

1. what kind of access to your computer do you have?
Is it a common computer with common display, or you only have a ssh connection, or there is some kind of processor manager that allows you to control the remote machine?

2. If it is a common computer please put additional "timeout=15" string to menu.lst file (for example after default field):
default=5
timeout=15


then reboot your system.

You must have a chance to chose the kernel you want to boot into.
If you are not able to boot into OpenVZ kernel, please describe what do you see on your display.
Re: GRUB Bootmanager [message #32017 is a reply to message #32016] Thu, 17 July 2008 12:05 Go to previous messageGo to next message
elturco is currently offline  elturco
Messages: 12
Registered: July 2008
Junior Member
its a common computer with common display

now, I can not reboot anymore, Im getting the error message unknown interrupt or fault..

What should I do now ?
Re: GRUB Bootmanager [message #32018 is a reply to message #32017] Thu, 17 July 2008 12:14 Go to previous messageGo to next message
elturco is currently offline  elturco
Messages: 12
Registered: July 2008
Junior Member
Maratrus, thank you very much...

Now I can reboot my desired kernel.. If I let the time count down I getting the error message, that I mentioned before..

But after pressing the ESC button I can choose the kernel. Can you say me which of the kernels should I take to make simulations in OpenVz.

I Can choose between this kernels here:

-2.6.18-12-fza-686-bigmem
-2.6.18-12-fza-686
-2.6.18-12-fza-486

Thank you very much again...
Re: GRUB Bootmanager [message #32019 is a reply to message #32018] Thu, 17 July 2008 12:26 Go to previous messageGo to next message
maratrus is currently offline  maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
Senior Member
Hi,

in our situation it doesn't matter which kernel do we chose.
Try -2.6.18-12-fza-686.

Please show here the exact error message you'll see on the display!
(if you want you can make a picture).

What architecture does your computer have?
Re: GRUB Bootmanager [message #32020 is a reply to message #32019] Thu, 17 July 2008 12:39 Go to previous messageGo to next message
elturco is currently offline  elturco
Messages: 12
Registered: July 2008
Junior Member
I am running Ubuntu on a virtuell Machine,
my Architecture is i86.
I have send a picture about the error message.
Re: GRUB Bootmanager [message #32021 is a reply to message #32020] Thu, 17 July 2008 13:05 Go to previous messageGo to next message
maratrus is currently offline  maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
Senior Member
What kernel did you chose?
Try -2.6.18-12-fza-686.
If it doesn't boot
try to change menu.lst

try this one and boot into -2.6.18-12-fza-686 kernel
/boot/vmlinuz-2.6.18-12-fza-686 root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f ro quiet splash


then if it doesn't work try this one,

/boot/vmlinuz-2.6.18-12-fza-686 root=UUID=19eab690-e5bf-4663-81b2-b74d7fcab58f ro quiet splash noapic
Re: GRUB Bootmanager [message #32022 is a reply to message #32021] Thu, 17 July 2008 13:15 Go to previous messageGo to next message
elturco is currently offline  elturco
Messages: 12
Registered: July 2008
Junior Member
I can load the desired Kernel marartus. But as I mentioned before, if I let the timeout count down to 0, Im getting the error message..

But If I press the ESC button during the timeout, I can choose from a list which kernel I want to load..

Thank you, you helped me very much.. but is it common to get an error message when the timeout is over ?
Re: GRUB Bootmanager [message #32025 is a reply to message #32022] Thu, 17 July 2008 13:35 Go to previous messageGo to next message
maratrus is currently offline  maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
Senior Member
Hi,

please change default value in menu.lst to 7. And everything should be ok.

Please, show the output "cat /proc/cpuinfo" after you will boot into OpenVZ kernel.
Re: GRUB Bootmanager [message #32026 is a reply to message #32025] Thu, 17 July 2008 13:59 Go to previous message
elturco is currently offline  elturco
Messages: 12
Registered: July 2008
Junior Member
Marartus, do you have experience by building a real test setup for olsr or batman routing protocols ??

Previous Topic: Network Suggestion Please
Next Topic: Invalid kernel, or some kernel modules are not loaded!! help!!
Goto Forum:
  


Current Time: Sat Aug 31 11:10:55 GMT 2024

Total time taken to generate the page: 0.04971 seconds