vmware-config.pl fails at cp-f vmnet.ko ./../vmnet.o

scsikid · n00b Joined: 27 Oct 2004 Posts: 10

Can someone help me with this, I have been struggling with it for hours. All of a sudden my VM just froze on me today and when I rebooted my machine, vmware advised me to run the vmware-config which gave the following message.

Building for VMware Workstation 4.5.2 or VMware GSX Server 3.1.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config3/vmmon-only'
make -C /lib/modules/2.6.13-gentoo-r3/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.13-gentoo-r3'
CC [M] /tmp/vmware-config3/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config3/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config3/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config3/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config3/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config3/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config3/vmmon-only/common/task.o
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wdeclaration-after-statement" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-ffreestanding" is valid for C/ObjC but not for C++
CC [M] /tmp/vmware-config3/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config3/vmmon-only/vmcore/compat.o
CC [M] /tmp/vmware-config3/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config3/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config3/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config3/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-2.6.13-gentoo-r3'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config3/vmmon-only'
The module loads perfectly in the running kernel.

Extracting the sources of the vmnet module.

Building the vmnet module.

Building for VMware Workstation 4.5.2 or VMware GSX Server 3.1.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config3/vmnet-only'
make -C /lib/modules/2.6.13-gentoo-r3/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.13-gentoo-r3'
CC [M] /tmp/vmware-config3/vmnet-only/driver.o
CC [M] /tmp/vmware-config3/vmnet-only/hub.o
CC [M] /tmp/vmware-config3/vmnet-only/userif.o
CC [M] /tmp/vmware-config3/vmnet-only/netif.o
CC [M] /tmp/vmware-config3/vmnet-only/bridge.o
CC [M] /tmp/vmware-config3/vmnet-only/procfs.o
LD [M] /tmp/vmware-config3/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config3/vmnet-only/vmnet.mod.o
LD [M] /tmp/vmware-config3/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-2.6.13-gentoo-r3'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config3/vmnet-only'
Unable to make a vmnet module that can be loaded in the running kernel:

I would presume the problem is shown on the last line of cp-f .... etc?

I have been trying to trouble shoot this for about 10hrs now with no luck. I have searched high and low on google. Nothing helps. I have tried various any-any updates up to 94. nothing works. Also tried installing a new version of vmware. Does anyone have any idea what could be going on here?

Help is appreciated by all.

scsikid · n00b Joined: 27 Oct 2004 Posts: 10

is there a better category to put this in? i am not sure if its amd64 specific.

scsikid · n00b Joined: 27 Oct 2004 Posts: 10

[/bug]is it possible to insert pre-built vmnet modules instead of letting the vmware-config.pl build them, will they still work?

if so where can i get the modules?

scsikid · n00b Joined: 27 Oct 2004 Posts: 10

okay im understanding things a bit more.

vmware-config2 # insmod vmnet.o
insmod: error inserting 'vmnet.o': -1 Unknown symbol in module

looks like it didnt build right against my kernel. however i just dont know why.....

i know no one is responding to this except me! but maybe one day when this is all sorted out someone will benefit from it.

c4 · Guru Joined: 21 Feb 2004 Posts: 312 Location: Sweden

I'm sure you could use a premade module for vmware.. problem is that it would have to be build for your kernel. Also things like whatever USE-flags you have used might have an affect on the result.

Are you emerging the vmware-workstation software or are you building it manually? Also an other important thing to check is if your /usr/src/linux symlink is pointing to the kernel you are runnng.

When using the ebuild in portage an init-script is created durring the emerge.. ths makes it easy to start vmware ( /etc/init.d/vmware start ) without the need of manually loading the modules first. In fact I would actually recommend to use portage and the apropriate ebuild and after vwmare-workstation has started provide your serialkey. Works great here, I'm running vmware-workstation 5.0 from portage.
_________________
AMD64 Gentoo Hardened server
AMD64 Xubuntu Desktop
X86 Dreamlinux Vaio laptop

scsikid · n00b Joined: 27 Oct 2004 Posts: 10

yea i was running 5.0 built from portage flawlessly till the other day when vmware crashed my system and ran into this problem after rebooting.

i have been very happy running gentoo for the past 2.5 years and running vmware-workstation on it for my windows apps that i need to use. this one glitch is killing me.

yep /usr/src/linux is pointing to my kernel, and the init script is fine too. however that is meaningless at this point as i cant even configure it with vmware-config.pl

it looks like its building all necessary modules against kernel properly but fails at insmod vmnet.o

if anyone is running 2.6.13-r3 please hook me up with vmnet.o file

nix95@hotmail.com

thanks

dweigert · Posted: Fri Oct 21, 2005 11:09 am Post subject:

Ok.. kernel modules all are .ko files. Definitely not .o

When I get back from vacation, I can give it a try, as I have a VMware license, but haven't installed it on my 64 bit box.

Dan
_________________
"Always remember to mount a scratch monkey..."

scsikid · n00b Joined: 27 Oct 2004 Posts: 10

i got fed up and formatted my system, reinstalled everything from scratch, everything works now.

i tried upgrading my kernel to r4 instead of r3 and no difference. still had the same error. i read somewhere that you need the buslogic driver installed in order to have vmware compile its vmnet driver. i have it enabled in my kernel, but i will try eventually try and remove it and see if it make a difference.

to save people some time. do not run vmware 5.5 beta, i just tried it, its very buggy. stick with 5.0, it seems to work flawless on my computer. all usb devices are working perfectly.

thanks for attempting to help dwigert.