On Sun, 17 Dec 2006 20:22:04 -0700
Richard Fish wrote:

> On 12/17/06, David Relson <[EMAIL PROTECTED]> wrote:
> > 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?
> 
> ~ > uname -r
> 2.6.19-gentoo-r1
> 
> ~ > find /lib/modules/ | grep -e vmmon -e vmnet
> /lib/modules/2.6.19-gentoo-r1/misc/vmmon.ko
> /lib/modules/2.6.19-gentoo-r1/misc/vmnet.ko
> 
> ~ > grep -e vmmon -e vmnet /lib/modules/`uname -r`/*
> /lib/modules/2.6.19-gentoo-r1/modules.dep:/lib/modules/2.6.19-gentoo-r1/misc/vmnet.ko:
> /lib/modules/2.6.19-gentoo-r1/modules.dep:/lib/modules/2.6.19-gentoo-r1/misc/vmmon.ko:
> /lib/modules/2.6.19-gentoo-r1/modules.symbols:alias
> symbol:VMX86_RegisterMonitor vmmon
> 
> Try insmod'ing the drivers manually:
> 
> insmod /lib/modules/`uname -r`/misc/vmmon.ko
> 
> Also, the output of dmesg might hold some clue.
> 
> -Richard

Good info!  "uname" and "find" show you and I are running the same
kernel and have the modules in the same places.

Running insmod for vmmon and vmnet gets them installed and output
from "/etc/init.d/vmware start" indicated success.  However
running ".../vmware status" immediately afterwards says vmware
has stopped.  Looking at dmesg I suspect the following is
the key:

vmware-start: Bridged networking on /dev/vmnet0 failed

Since .config contains "# CONFIG_BRIDGE is not set" I do believe I know
the cause of _this_ problem.  Just to be sure, my next (newbie)
question is "Is bridged networking the the right option to choose?"

Thanks.

David



To ask a question of ignorance, does 
-- 
gentoo-user@gentoo.org mailing list

Reply via email to