On Sun, 17 Dec 2006 18:43:52 -0700
Richard Fish wrote:
> On 12/17/06, David Relson <[EMAIL PROTECTED]> wrote:
> > Looking in /lib/modules/2.6.19-gentoo-r1 directory misc has newly
> > built modules vmmon.ko and vmnet.ko
>
> You need to make sure that /usr/src/linux points to the configured
> sources of your currently running kernel. Otherwise vmmon and vmnet
> will be built for the wrong kernel version (or wrong kernel config)
> and fail to load.
>
> >
> > It would seem that modprobe is looking in the wrong directory.
> > Running "strace modprobe vmmon" shows a read of
> > "/lib/modules/2.6.19-gentoo-r1/ke"..., which is (unfortunately) an
> > incomplete path.
>
> Use the -s option to increase the length of the strings that strace
> prints before truncating them...fex: "strace -s256 ..."
>
> -Richard
Hi Richard,
Feedback appreciated!
/usr/src/linux is a symlink to the currently running kernel. The
dates/times of the relevant files, i.e.
/usr/src/linux/.config
/etc/kernels/kernel-config-x86-2.6.19-gentoo-r1
/boot/initramfs-genkernel-x86-2.6.19-gentoo-r1
/boot/System.map-genkernel-x86-2.6.19-gentoo-r1
/boot/kernel-genkernel-x86-2.6.19-gentoo-r1
all match up.
Using "strace -s4096 modprobe vmmon" show that file
/lib/modules/2.6.19-gentoo-r1/modules.alias is being read
just before the "FATAL: Module vmmon not found." message is
displayed.
It sounds like you have a working vmware-server environment. If so,
where are your copies of vmmon.ko and vmnet.ko located and are they
referenced in modules.alias? Also, any additional thoughts on what I
should be looking at/for to solve the modprobe issue?
Thanks.
David
--
[email protected] mailing list
