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
OpenVZ Forum
Members
Search
Help
Register
Login
Home
