*SOLVED* development kernel can not boot [message #3838] |
Wed, 21 June 2006 07:15 ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
attackghost
Messages: 6 Registered: June 2006 Location: China xjtu
|
Junior Member |
|
|
I have installed the development kernel 2.6.16-026test014.4 to experience the live Migration Feature. But it can not boot . And the stable kernel 2.6.8-022stab077.1 works well on the same machine.
I'm very interested in live Migration and expect to make a experiment.
Thanks!
[Updated on: Thu, 29 June 2006 10:26] by Moderator Report message to a moderator
|
|
|
|
|
|
|
|
Re: development kernel can not boot [message #3892 is a reply to message #3858] |
Fri, 23 June 2006 01:54 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
attackghost
Messages: 6 Registered: June 2006 Location: China xjtu
|
Junior Member |
|
|
Command "lcpci -n" not found. Is it "lspci -n"?
Thanks.
[root@node8 ~]# lspci
00:00.0 Host bridge: ServerWorks GCNB-LE Host Bridge (rev 32)
00:00.1 Host bridge: ServerWorks GCNB-LE Host Bridge
00:08.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
00:0f.0 ISA bridge: ServerWorks CSB6 South Bridge (rev a0)
00:0f.1 IDE interface: ServerWorks CSB6 RAID/IDE Controller (rev a0)
00:0f.2 USB Controller: ServerWorks CSB6 OHCI USB Controller (rev 05)
00:0f.3 Host bridge: ServerWorks GCLE-2 Host Bridge
00:10.0 Host bridge: ServerWorks CIOB-X2 PCI-X I/O Bridge (rev 05)
00:10.2 Host bridge: ServerWorks CIOB-X2 PCI-X I/O Bridge (rev 05)
01:02.0 PCI bridge: Mellanox Technologies MT23108 PCI Bridge (rev a1)
02:00.0 InfiniBand: Mellanox Technologies MT23108 InfiniHost (rev a1)
03:04.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07)
03:05.0 Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller (rev 02)
[root@node8 ~]# lcpci -n
-bash: lcpci: command not found
[root@node8 ~]# lspci -n
00:00.0 Class 0600: 1166:0017 (rev 32)
00:00.1 Class 0600: 1166:0017
00:08.0 Class 0300: 1002:4752 (rev 27)
00:0f.0 Class 0601: 1166:0203 (rev a0)
00:0f.1 Class 0101: 1166:0213 (rev a0)
00:0f.2 Class 0c03: 1166:0221 (rev 05)
00:0f.3 Class 0600: 1166:0227
00:10.0 Class 0600: 1166:0101 (rev 05)
00:10.2 Class 0600: 1166:0101 (rev 05)
01:02.0 Class 0604: 15b3:5a46 (rev a1)
02:00.0 Class 0c06: 15b3:5a44 (rev a1)
03:04.0 Class 0100: 1000:0030 (rev 07)
03:05.0 Class 0200: 8086:100e (rev 02)
[Updated on: Fri, 23 June 2006 13:36] Report message to a moderator
|
|
|
|
|
Re: development kernel can not boot [message #4037 is a reply to message #3911] |
Tue, 27 June 2006 10:52 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
Vasily Tarasov
Messages: 1345 Registered: January 2006
|
Senior Member |
|
|
Hello, sorry for delay.
I've investigated your initrd images.
This is from init script from initrd-2.6.16-026test014.4-smp.img:
/sbin/udevstart
echo -n "/sbin/hotplug" > /proc/sys/kernel/hotplug
echo "Loading mptbase.ko module"
insmod /lib/mptbase.ko
echo "Loading mptscsih.ko module"
insmod /lib/mptscsih.ko
/sbin/udevstart
There is these files on image:
$ ls -l image/lib/mptbase.ko
-rw-r--r-- 1 vass users 57248 Jun 27 13:27 ./lib/mptbase.ko
vass@dhcp0-138 $ ls -l image/lib/mptscsih.ko
-rw-r--r-- 1 vass users 39856 Jun 27 13:27 ./lib/mptscsih.ko
vass@dhcp0-138 $
But sizes are differrent from those modules, that go with openvz :
$ ls -l /lib/modules/2.6.16-026test014.4/kernel/drivers/message/fusion/mptbase.ko
-rwxr--r-- 1 vass users 56392 Jun 7 17:18 ./lib/modules/2.6.16-026test014.4/kernel/drivers/message/fusion/mptbase.ko
$ ls -l /lib/modules/2.6.16-026test014.4/kernel/drivers/message/fusion/mptscsih.ko
-rwxr--r-- 1 vass users 38808 Jun 7 17:18 ./lib/modules/2.6.16-026test014.4/kernel/drivers/message/fusion/mptscsih.ko
Thus there are wrong modules on initrd!
Also support of your device resides in module: mptspi.ko. But there is no this module on initrd image and in init script.
Conclusion: initrd image is created by mkinitrd script of your distribution. And it works not properly with our kernel.
Solution: You can create your initrd image manually.
Please, tell me your distribution? I'll try to check it and may be it's OpenVZ bug.
[Updated on: Wed, 28 June 2006 06:54] Report message to a moderator
|
|
|
|
|
|
|
|
|
Re: development kernel can not boot [message #4134 is a reply to message #4087] |
Thu, 29 June 2006 10:08 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) |
niggo
Messages: 1 Registered: June 2006 Location: Weiterstadt, Germany
|
Junior Member |
|
|
Hi,
I'm Stef's co-worker, and we just succeeded in booting the dev-kernel on our node.
Thanks, vass, the wiki-article pointed us into the right direction.
We had to modify the parameters of the cpio-command, as our node has more than 65536 inodes (-H newc).
Finally I compiled the required modules directly into the kernel and removed the mpt*-modules from the initrd-image.
Regards from Germany,
niggo
[Updated on: Thu, 29 June 2006 10:26] by Moderator Report message to a moderator
|
|
|