OpenVZ Forum


Home » General » Support » ovzkernels not booting - where to look first
Re: ovzkernels not booting - where to look first [message #15501 is a reply to message #15495] Thu, 02 August 2007 11:50 Go to previous messageGo to previous message
ugob is currently offline  ugob
Messages: 271
Registered: March 2007
Senior Member
finist wrote on Thu, 02 August 2007 02:49

1) may be the question is a bit late, but still: and what do you want to do globally? Why do you want to upgrade the kernel? Do you want just a kernel which can support more than 4 Gb RAM? If yes, you can safely use the enterprise kernel from 2.6.9 branch (e.g. ovzkernel-enterprise-2.6.9-023stab044.4.i686.rpm). It should work fine.
Or you just want to use the most modern kernel?


I just want to use the most modern kernel. I don't need the PAE, I just need an SMP kernel.
finist wrote on Thu, 02 August 2007 02:49


2) i still think that the problem with 2.6.18 kernels is in initrd.
i just tried to reproduce: took a RHEL4.3 and tried to install 2.6.18 OVZ kernel. The boot failed - unable to find root.
i haven't had a time to get the reason and don't know the exact solution how to fix this - i'll certainly do this but later.

At the moment i've done a workaround - took a CentOS5 node, install there the same OVZ kernel and just copy an initrd to the RHEL4.3 node. It works. You can try the same while i'm looking for the correct solution.

Note: to make sure the initrd created on the CentOS5 node contains all the modules required on your RHEL4 node it's better to recreate initrd manually (on the CentOS5 node):
# mkinitrd -v -f /boot/initrd-2.6.18-8.1.8.el5.028stab039.1PAE.img 2.6.18-8.1.8.el5.028stab039.1PAE --preload=scsi_mod --preload=sd_mod --preload=3w-xxxx


I doubt the problem is initrd, since some kernels hung while trying to start the 9th VE.

finist wrote on Thu, 02 August 2007 02:49


3) if nothing helps please provide me access to the node, i'll try to boot the kernel. Of course the permission to reboot is required. :\ And if my described workaround won't workout, we have to get the ability to collect the logs somehow. Just find a COM-to-COM cable and connect this node with any other (preferably Linux, but not required). We can help you to configure it later.

You can safely send the access through the private messaging. Just one more thing: i'll be unavailable in a few days so please, if you'll send something private, send the copy to Vasily (vaverin), he can help you too.



I can give you access as long as the people at the datacenter are available and I have admin time free (I have 15min per month free), or if I'm at the datacenter.

I'm leaving for a 3-week vacation tomorrow, so I think I'll just stick to the kernel that works (I've configured grub.conf accordingly) and wait until I come back. Now that the machine is running fine, I'm happy. I'll try to help as much as possible when I come back from vacation.


Please read the manual before asking questions:
http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf

Please have a look at the wiki before asking questions:
http://wiki.openvz.org/Main_Page
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: reiser4
Next Topic: Activated NFS and now the ve won't bring up network
Goto Forum:
  


Current Time: Wed Sep 10 09:53:10 GMT 2025

Total time taken to generate the page: 0.08067 seconds