udev starten: kernel too old for this udev version [FEHLGESCHLAGEN]

[shatter]

Hi *,

I have troubles starting a container.
It is a physical to container clone of a Centos 5.4 system.

Starting it I get the messages:

INIT LOG    Online
starting init logger
Welcome toCentOS release 5.4 (Final)
Press 'I' to enter interactive startup.
Es wurde keine Zugriffsart gefunden, mit der auf die Hardwareuhr zugegriffen werden konnte.
Benutzen Sie die „--debug“-Option um die versuchten Zugriffsarten anzuzeigen.
Stelle Uhr (utc) auf: Fr 8. Jan 18:23:24 CET 2010 [ OK ]
udev starten: kernel too old for this udev version [FEHLGESCHLAGEN]
Standardmäßige Tastaturbelegung laden (de-latin1-nodeadkeys):/etc/rc.d/rc.sysinit: line 396: /dev/tty0: Datei oder Verzeichnis nicht gefunden
[FEHLGESCHLAGEN]
Rechnername dhsrv199vz einstellen: [ OK ]
raidautorun: failed to open /dev/md0: Permission denied
awk: Kommandozeile:1: Fatal: Kann Datei '/proc/misc' nicht zum Lesen öffnen (Datei oder Verzeichnis nicht gefunden).
Lokale Dateisysteme einhängen: [ OK ]
Lokale Dateisystemkontigente aktivieren: [ OK ]
Swap-Bereiche in /etc/fstab aktivieren: [ OK ]

Please wait...

I cant log in, neither via VNC no Putty.
Any help appreciated.

dhvz2:/vz/private/199/lib/udev# uname -a
Linux dhvz2 2.6.24-9-pve #1 SMP PREEMPT Tue Nov 17 09:34:41 CET 2009 x86_64 GNU/Linux

dhvz2:/vz/private/199/lib/udev# pveversion
pve-manager/1.4/4403

Joachim

 

[dietmar]

I cant log in, neither via VNC no Putty.
Any help appreciated.

You can't start udev or any other hardware related services (raidautorun, hwclock) inside a container - please disable that first.

So you need to make sure that you have all devices in /dev/ (because they are no longer auto-created by udev). Use MAKEDEV to create them (especially tty/pty devices).

Also, do you start the sshd - i can't see that in the init log?

 

[shatter]

Next error message from the log:

>FATAL: Could not load /lib/modules/2.6.24-9-pve/modules.dep

I upgraded the kernel a few days ago ...

Now I find:

dhvz2:/vz/private/199/lib/modules# ls -l
total 8
drwxr-xr-x 6 root root 4096 Jan  8 12:57 2.6.18-164.9.1.el5
drwxr-xr-x 6 root root 4096 Jan  8 12:25 2.6.18-164.el5
dhvz2:/vz/private/199/lib/modules#

How do I get the "2.6.24-9-pve" directory?
Do I need it at all?
Can I simply link 2.6.18-164.9.1.el5 to 2.6.24-9-pve ?

btw: is there a "clone physical" howto beyond Howtoforge and Openvz ... ?

Thanx,

Joachim

 

[tom]

Next error message from the log:

>FATAL: Could not load /lib/modules/2.6.24-9-pve/modules.dep

I upgraded the kernel a few days ago ...

Now I find:

dhvz2:/vz/private/199/lib/modules# ls -l
total 8
drwxr-xr-x 6 root root 4096 Jan  8 12:57 2.6.18-164.9.1.el5
drwxr-xr-x 6 root root 4096 Jan  8 12:25 2.6.18-164.el5
dhvz2:/vz/private/199/lib/modules#

How do I get the "2.6.24-9-pve" directory?
Do I need it at all?
Can I simply link 2.6.18-164.9.1.el5 to 2.6.24-9-pve ?

btw: is there a "clone physical" howto beyond Howtoforge and Openvz ... ?

Thanx,

Joachim

you cannot load kernel modules inside a container as there is no kernel in the container - behavior by design.

 

[shatter]

Thanx Tom,

... how do I prevent the loading attempt?
What else do I have to prevent / shut off beyond that mentioned in the OpenVZ doc?

Joachim

 

[tom]

Thanx Tom,

... how do I prevent the loading attempt?
What else do I have to prevent / shut off beyond that mentioned in the OpenVZ doc?

Joachim

I suggest you just ignore the message.