VMware Communities: Failed to build vmmon.o on Fedora 9 x86

Up to Discussions in VMware Server 1

This Question is Possibly Answered

1 "correct" answer available (10 pts) 1 "helpful" answer available (6 pts)

1 2 Previous Next

20 Replies Last post: Mar 21, 2009 5:54 PM by rath

Failed to build vmmon.o on Fedora 9 x86

May 6, 2008 8:45 AM

greno 46 posts since
May 31, 2004

I found the message about Fedora 8 and building vmmon required the any-any patch v116. So I downloaded and ran that patch. But still I cannot get the modules compiled on Fedora 9.

Extracting the sources of the vmmon module.

Building the vmmon module.

Building for VMware Server 1.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /usr/src/kernels/2.6.25-14.fc9.i686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.25-14.fc9.i686'
CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config1/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-config1/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config1/vmmon-only/common/comport.o
CC [M] /tmp/vmware-config1/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config1/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config1/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config1/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config1/vmmon-only/common/task.o
cc1plus: warning: command line option "-Werror-implicit-function-declaration" 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 "-Wno-pointer-sign" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++
In file included from /tmp/vmware-config1/vmmon-only/common/hostKernel.h:56,
from /tmp/vmware-config1/vmmon-only/common/task.c:30:
include/asm/page.h: In function ‘pte_t native_make_pte(pteval_t)’:
include/asm/page.h:128: error: expected primary-expression before ‘)’ token
include/asm/page.h:128: error: expected ‘;’ before ‘{’ token
include/asm/page.h:128: error: expected primary-expression before ‘.’ token
include/asm/page.h:128: error: expected `;' before ‘}’ token
In file included from include/asm/page.h:140,
from /tmp/vmware-config1/vmmon-only/common/hostKernel.h:56,
from /tmp/vmware-config1/vmmon-only/common/task.c:30:
include/asm/paravirt.h: In function ‘pte_t __pte(pteval_t)’:
include/asm/paravirt.h:955: error: expected primary-expression before ‘)’ token
include/asm/paravirt.h:955: error: expected ‘;’ before ‘{’ token
include/asm/paravirt.h:955: error: expected primary-expression before ‘.’ token
include/asm/paravirt.h:955: error: expected `;' before ‘}’ token
In file included from /tmp/vmware-config1/vmmon-only/common/task.c:1194:
/tmp/vmware-config1/vmmon-only/common/task_compat.h: At global scope:
/tmp/vmware-config1/vmmon-only/common/task_compat.h:9: warning: ‘typedef’ was ignored in this declaration
make[2]: *** [/tmp/vmware-config1/vmmon-only/common/task.o] Error 1
make[1]: *** --_module_/tmp/vmware-config1/vmmon-only-- Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.25-14.fc9.i686'
make: *** http://vmmon.ko Error 2
make: Leaving directory `/tmp/vmware-config1/vmmon-only'
Unable to build the vmmon module.

For more information on how to troubleshoot module-related problems, please
visit our Web site at "http://www.vmware.com/download/modules/modules.html" and
"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".

Execution aborted.

Reply Re: Failed to build vmmon.o on Fedora 9 x86 May 6, 2008 12:28 PM

greno 46 posts since
May 31, 2004

Anybody have VMware Server running on Fedora 9? How did you do it?

Regards,
Gerry

Reply Re: Failed to build vmmon.o on Fedora 9 x86 May 7, 2008 11:21 AM

in response to: greno

greno 46 posts since
May 31, 2004

Here is what I did to get to where I see the error:

Downloaded Fedora 9 DVD iso.
Installed F9
Downloaded VMware Server 1.0.5 RPM and installed it.
In terminal:
$ su -

yum upgrade # this bring the RC kernel
yum list kernel

kernel.i686 2.6.25-14.fc9 installed

yum install kernel-devel
/usr/bin/vmware-config.pl #here is where the error occurs when the config is trying to build vmmon.o for the installed kernel.

so I try to get an any-any patch:

cd /tmp
wget http://blog.devhen.com/files/vmware-any-any-update-116.tgz
tar xzvf vmware-any-any-update-116.tgz
cd vmware-any-any-update116
./runme.pl #here is where the runme calls the config again and again it fails with the errors in my first post.

So I guess there needs to be a new any-any-patch made for F9 specifically.

Regards,
Gerry

Reply Re: Failed to build vmmon.o on Fedora 9 x86 May 7, 2008 11:29 AM

in response to: greno

Daniel.D. 249 posts since
Feb 1, 2008

greno wrote:
Here is what I did to get to where I see the error:

Downloaded Fedora 9 DVD iso.
Installed F9
Downloaded VMware Server 1.0.5 RPM and installed it.
In terminal:
$ su -

yum upgrade # this bring the RC kernel

Shouldn't you had upgraded to 2.6.25 and stayed on 2.6.24, you surely would have compiled successfully with any-any116.

So I guess there needs to be a new any-any-patch made for F9 specifically.

Yes, work on any-any117 is underway.
There is discussion here and here.
And this is the (apparently still not working for Fedora) preliminary any-any-update117

Reply Re: Failed to build vmmon.o on Fedora 9 x86 May 14, 2008 8:01 AM

Astute Systems 2 posts since
May 14, 2008

greno wrote:
I found the message about Fedora 8 and building vmmon required the any-any patch v116. So I downloaded and ran that patch. But still I cannot get the modules compiled on Fedora 9.

Hi Greno,

I had exactly the same problem, and then reading this post I saw Daniel D's answer and tried that. - Although the compilation got a little further, it still failed:

root@widebit vmware-any-any-update115# ./runme.pl
......
Building for VMware Server 1.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config6/vmmon-only'
make -C /lib/modules/2.6.25-14.fc9.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.25-14.fc9.x86_64'
CC [M] /tmp/vmware-config6/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config6/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-config6/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config6/vmmon-only/common/comport.o
CC [M] /tmp/vmware-config6/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config6/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config6/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config6/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config6/vmmon-only/common/task.o
cc1plus: warning: command line option "-Werror-implicit-function-declaration" 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 "-Wno-pointer-sign" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++
In file included from /tmp/vmware-config6/vmmon-only/common/task.c:1195:
/tmp/vmware-config6/vmmon-only/common/task_compat.h:9: warning: ‘typedef’ was ignored in this declaration
/tmp/vmware-config6/vmmon-only/common/task_compat.h: In function ‘void Task_Switch_V45(VMDriver, Vcpuid)’:*
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this function
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this function
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciContext.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciDatagram.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciDriver.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciDs.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciGroup.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciHashtable.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciProcess.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciResource.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciSharedMem.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config6/vmmon-only/vmcore/compat.o
CC [M] /tmp/vmware-config6/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config6/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config6/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config6/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.25-14.fc9.x86_64'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config6/vmmon-only'
The module loads perfectly in the running kernel.
.......
Building the vmnet module.
Building for VMware Server 1.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config6/vmnet-only'
make -C /lib/modules/2.6.25-14.fc9.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.25-14.fc9.x86_64'
CC [M] /tmp/vmware-config6/vmnet-only/driver.o
CC [M] /tmp/vmware-config6/vmnet-only/hub.o
CC [M] /tmp/vmware-config6/vmnet-only/userif.o
CC [M] /tmp/vmware-config6/vmnet-only/netif.o
CC [M] /tmp/vmware-config6/vmnet-only/bridge.o
/tmp/vmware-config6/vmnet-only/bridge.c: In function ‘VNetBridgeUp’:
/tmp/vmware-config6/vmnet-only/bridge.c:949: error: implicit declaration of function ‘sock_valbool_flag’
*make[2]: *** [/tmp/vmware-config6/vmnet-only/bridge.o] Error 1*
*make[1]: *** --_module_/tmp/vmware-config6/vmnet-only-- Error 2*
make[1]: Leaving directory `/usr/src/kernels/2.6.25-14.fc9.x86_64'
*make: *** http://vmnet.ko Error 2*
make: Leaving directory `/tmp/vmware-config6/vmnet-only'
Unable to build the vmnet module.
For more information on how to troubleshoot module-related problems, please
visit our Web site at "http://www.vmware.com/download/modules/modules.html" and
"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".
Execution aborted.
root@widebit vmware-any-any-update115#

Google showed me a japanese site at http://myn.meganecco.org/ which has a link to http://download.rsbac.org/tmp/vmware-any-any-update117.tar.gz.

Running the runme.pl within the vmware-any-any-update117 resulted in a successful compile under Fedora 9 kernel-2.6.25-14.fc9.x86_64 so I think there's a good chance this will work for you too.

I have attached the file to this message.

The following is a transcript of the compile. - I hope it helps.

Cheers.

--root@widebit vmware-any-any-update117--# ./runme.pl
Updating /usr/bin/vmware-config.pl ... already patched
Updating /usr/bin/vmware ... No patch needed/available
Updating /usr/bin/vmnet-bridge ... No patch needed/available
Updating /usr/lib/vmware/bin/vmware-vmx ... No patch needed/available
Updating /usr/lib/vmware/bin-debug/vmware-vmx ... No patch needed/available
VMware modules in "/usr/lib/vmware/modules/source" has been updated.
Before running VMware for the first time after update, you need to configure it
for your running kernel by invoking the following command:
"/usr/bin/vmware-config.pl". Do you want this script to invoke the command for
you now? yes
Making sure services for VMware Server are stopped.
Stopping VMware services:
Virtual machine monitor OK
Bridged networking on /dev/vmnet0 OK
DHCP server on /dev/vmnet8 OK
NAT service on /dev/vmnet8 OK
Host-only networking on /dev/vmnet8 OK
Virtual ethernet OK
Configuring fallback GTK+ 2.4 libraries.
In which directory do you want to install the mime type icons?
[/usr/share/icons]
What directory contains your desktop menu entry files? These files have a
.desktop file extension. [/usr/share/applications]
In which directory do you want to install the application's icon?
[/usr/share/pixmaps]
/usr/share/applications/vmware-server.desktop: warning: value "vmware-server.png" for key "Icon" in group "Desktop Entry" is an icon name with an extension, but there should be no extension as described in the Icon Theme Specification if the value is not an absolute path
/usr/share/applications/vmware-console-uri-handler.desktop: warning: value "vmware-server.png" for key "Icon" in group "Desktop Entry" is an icon name with an extension, but there should be no extension as described in the Icon Theme Specification if the value is not an absolute path
Trying to find a suitable vmmon module for your running kernel.
None of the pre-built vmmon modules for VMware Server is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? yes
Using compiler "/usr/bin/gcc". Use environment variable CC to override.
What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.25-14.fc9.x86_64/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Building for VMware Server 1.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config7/vmmon-only'
make -C /lib/modules/2.6.25-14.fc9.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.25-14.fc9.x86_64'
CC [M] /tmp/vmware-config7/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config7/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-config7/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config7/vmmon-only/common/comport.o
CC [M] /tmp/vmware-config7/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config7/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config7/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config7/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config7/vmmon-only/common/task.o
cc1plus: warning: command line option "-Werror-implicit-function-declaration" 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 "-Wno-pointer-sign" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++
In file included from /tmp/vmware-config7/vmmon-only/common/task.c:1194:
/tmp/vmware-config7/vmmon-only/common/task_compat.h:9: warning: ‘typedef’ was ignored in this declaration
/tmp/vmware-config7/vmmon-only/common/task_compat.h: In function ‘void Task_Switch_V45(VMDriver, Vcpuid)’:*
/tmp/vmware-config7/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config7/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config7/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this function
/tmp/vmware-config7/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this function
CC [M] /tmp/vmware-config7/vmmon-only/common/vmciContext.o
CC [M] /tmp/vmware-config7/vmmon-only/common/vmciDatagram.o
CC [M] /tmp/vmware-config7/vmmon-only/common/vmciDriver.o
CC [M] /tmp/vmware-config7/vmmon-only/common/vmciDs.o
CC [M] /tmp/vmware-config7/vmmon-only/common/vmciGroup.o
CC [M] /tmp/vmware-config7/vmmon-only/common/vmciHashtable.o
CC [M] /tmp/vmware-config7/vmmon-only/common/vmciProcess.o
CC [M] /tmp/vmware-config7/vmmon-only/common/vmciResource.o
CC [M] /tmp/vmware-config7/vmmon-only/common/vmciSharedMem.o
CC [M] /tmp/vmware-config7/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config7/vmmon-only/vmcore/compat.o
CC [M] /tmp/vmware-config7/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config7/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config7/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config7/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.25-14.fc9.x86_64'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config7/vmmon-only'
The module loads perfectly in the running kernel.
This program previously created the file /dev/vmmon, and was about to remove
it. Somebody else apparently did it already.
You have already setup networking.
Would you like to skip networking setup and keep your old settings as they are?
(yes/no) no May 15 00:22:58 widebit gnome-keyring-daemon3402: couldn't read 4 bytes from client:
yes
Extracting the sources of the vmnet module.
Building the vmnet module.
Building for VMware Server 1.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config7/vmnet-only'
make -C /lib/modules/2.6.25-14.fc9.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.25-14.fc9.x86_64'
CC [M] /tmp/vmware-config7/vmnet-only/driver.o
CC [M] /tmp/vmware-config7/vmnet-only/hub.o
CC [M] /tmp/vmware-config7/vmnet-only/userif.o
CC [M] /tmp/vmware-config7/vmnet-only/netif.o
CC [M] /tmp/vmware-config7/vmnet-only/bridge.o
CC [M] /tmp/vmware-config7/vmnet-only/filter.o
CC [M] /tmp/vmware-config7/vmnet-only/procfs.o
CC [M] /tmp/vmware-config7/vmnet-only/smac_compat.o
CC [M] /tmp/vmware-config7/vmnet-only/smac_linux.x86_64.o
LD [M] /tmp/vmware-config7/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config7/vmnet-only/vmnet.mod.o
LD [M] /tmp/vmware-config7/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.25-14.fc9.x86_64'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config7/vmnet-only'
The module loads perfectly in the running kernel.
Please specify a port for remote console connections to use 902
Stopping xinetd: OK
Starting xinetd: OK
Configuring the VMware VmPerl Scripting API.
Building the VMware VmPerl Scripting API.
Using compiler "/usr/bin/gcc". Use environment variable CC to override.
Installing the VMware VmPerl Scripting API.
The installation of the VMware VmPerl Scripting API succeeded.
Do you want this program to set up permissions for your registered virtual
machines? This will be done by setting new permissions on all files found in
the "/etc/vmware/vm-list" file. no
Generating SSL Server Certificate
In which directory do you want to keep your virtual machine files?
[/var/lib/vmware/Virtual Machines]
Do you want to enter a serial number now? (yes/no/help) no
Starting VMware services:
Virtual machine monitor OK
Virtual ethernet OK
Bridged networking on /dev/vmnet0 OK
Host-only networking on /dev/vmnet8 (background) OK
NAT service on /dev/vmnet8 OK
Starting VMware virtual machines... OK
The configuration of VMware Server 1.0.5 build-80187 for Linux for this running
kernel completed successfully.
root@widebit vmware-any-any-update117#
root@widebit vmware-any-any-update117#
root@widebit vmware-any-any-update117#

Attachments:

vmware-any-any-update117.tgz (480.5 K)

Reply Re: Failed to build vmmon.o on Fedora 9 x86 May 14, 2008 8:12 AM

in response to: Astute Systems

neophytal 6 posts since
May 14, 2008

astute- that worked to fix my problem. thanks so much.

Reply Re: Failed to build vmmon.o on Fedora 9 x86 May 14, 2008 8:18 AM

in response to: neophytal

Astute Systems 2 posts since
May 14, 2008

neophytal wrote:
astute- that worked to fix my problem. thanks so much.

Cool Neophytal, I'm glad it worked for you - Wow, a 5 minute turn-around on postings in here huh?

By the way, there seems to be some good stuff in both files that were referenced in this posting, and it may be that some things are fixed in one and some in the other. - Does anyone want to try and merge them?

Reply Re: Failed to build vmmon.o on Fedora 9 x86 May 14, 2008 8:26 AM

in response to: Astute Systems

neophytal 6 posts since
May 14, 2008

funny enough, I have been trying to fix it all morning so I can do some work. haha. it is very much appreciated, I had tried a different any-any-117 update from somewhere else and it didn't work.

thanks again.

Reply Re: Failed to build vmmon.o on Fedora 9 x86 May 15, 2008 9:10 AM

in response to: Astute Systems

snoopy26 1 posts since
May 15, 2008

Hi,

the vmware-any-any-update117 worked for me ...

VMwareWorkstation-6.0.3-80004.x86_64
kernel 2.6.25.3-18.fc9.x86_64

... but only halfway.

runme.pl ends successfully

But, starting vmware and trying to resume a suspended guest
runs on Error
---snip---
Version mismatch with vmmon module: expecting 167.0, got 137.0.
You have an incorrect version of the `vmmon' kernel module.
Try reinstalling VMware Workstation.
---snip--- <OK>
Failed to initialize monitor device.
---snip--- <OK>
Unable to change virtual machine power state: Cannot find a valid peer process to connect to.
---snip--- <OK>
Failed to reply to the dialog: Pipe: Read failed
---snip--- <OK>

Any ideas, hints, ... ?

Regards

Reply Re: Failed to build vmmon.o on Fedora 9 x86 May 16, 2008 8:07 AM

in response to: snoopy26

grgodkin 2 posts since
Dec 11, 2007

Failed for me:

~~root@Fedora9 vmware-any-any-update117~~# uname -a
Linux Fedora9 2.6.25.3-18.fc9.i686 #1 SMP Tue May 13 05:38:53 EDT 2008 i686 athlon i386 GNU/Linux
~~root@Fedora9 vmware-any-any-update117~~# ./runme.pl
Unable to open the installer database /etc/vmware/locations in read-mode.

Execution aborted.

Reply Re: Failed to build vmmon.o on Fedora 9 x86 May 16, 2008 8:13 AM

in response to: grgodkin

neophytal 6 posts since
May 14, 2008

dumb question, but are you running as root?

Linux illustrious 2.6.25-14.fc9.x86_64 #1 SMP Thu May 1 06:06:21 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux

--tk@illustrious:/etc/vmware--$ ls -al locations
-rw-r--r-- 1 root root 29838 2008-05-14 12:13 locations

I'd check that file, location, permissions, etc.

Reply Re: Failed to build vmmon.o on Fedora 9 x86 May 16, 2008 8:18 AM

in response to: neophytal

grgodkin 2 posts since
Dec 11, 2007

Yes, I do run as a root. That location does not exist.

Reply Re: Failed to build vmmon.o on Fedora 9 x86 May 16, 2008 8:28 AM

in response to: grgodkin

neophytal 6 posts since
May 14, 2008

its an actual file, not directory, just to let you know.

--~~tk@illustrious:/etc/vmware~~$ ls -al--
~~total 192~~
--drwxr-xr-x 6 root root 4096 2008-05-14 11:09 .--
--drwxr-xr-x 113 root root 12288 2008-05-16 10:31 ..--
---rw-r--r-- 1 root root 563 2008-05-14 11:09 config--
---rw-r--r-- 1 root root 483 2008-05-14 10:05 config.old.0--
---r-xr-xr-x 1 root root 39605 2008-03-04 16:43 installer.sh--
---rw-r--r-- 1 root root 375 2008-05-14 11:09 license.vs.1.0-00--
---rw-r--r-- 1 root root 29838 2008-05-14 12:13 locations--
---rw-rw-r-- 1 root root 86 2008-03-31 13:06 netmap.conf--
--drwxr-xr-x 2 root root 4096 2008-05-14 10:08 pam.d--
---r--r--r-- 1 root root 182 2008-03-04 16:43 signing-key.pub--
--drwxr-xr-x 2 root root 4096 2008-05-14 11:09 ssl--
---rw-rw-r-- 1 root root 317 2008-05-14 12:04 vm-list--
---rw-rw-r-- 1 root root 157 2008-05-14 12:04 vm-list-private--
--drwxr-xr-x 3 root root 4096 2008-05-14 10:17 vmnet1--
--drwxr-xr-x 4 root root 4096 2008-05-14 10:16 vmnet8--

Reply Re: Failed to build vmmon.o on Fedora 9 x86 May 21, 2008 8:34 AM

in response to: neophytal

IgorZ 14 posts since
Feb 6, 2007

I'm getting the same error.

~~root@fedora9 vmware-any-any-update117~~# ./runme.pl
Unable to open the installer database /etc/vmware/locations in read-mode.

Execution aborted.

I don't have a locations file, nor do I have a vmware folder in my /etc dir, the only vmware related folder in /etc on my Fedora 9 (x86) install is /etc/vmware-tools

Reply Re: Failed to build vmmon.o on Fedora 9 x86 May 22, 2008 2:14 AM

in response to: IgorZ

Daniel.D. 249 posts since
Feb 1, 2008

IgorZ wrote:

I don't have a locations file, nor do I have a vmware folder in my /etc dir, the only vmware related folder in /etc on my Fedora 9 (x86) install is /etc/vmware-tools

So what you are saying there is that you are trying to patch the VMware Tools in your guest.

As far as I know, the vmware-any-any-update117 seems to have been hacked from a prior version just to compile the modules in the host.
It does not work in a guest like the previous versions made by the original any-any patch developer, because it is hardcoded to actively look for files and file locations present only in the host installation of VMware Server.
You'll have to endure your guest Fedora 9 install without the extra ethernet / screen / mouse features, at least until someone can adapt the patch script to correctly patch the VMware Tools package.

1 2 Previous Next

Actions

View as PDF

Up to Discussions in VMware Server 1