VMware Communities
zufi007
Contributor
Contributor

VMWare Workstation 6.0.3-80004.x86_64 installation errors on Fedora 9 kernel 2.6.25.3-18.fc9

Hi,

I just installed Fedora 9 64 bit (Sulphur) on my laptop and was trying to setup VMWare Workstation on it. After installing the RPM version of the downloaded VMWare Workstatio, I tried running the vmware-config.pl which first of all complained about libXtst.so.6 not being installed on the system (although I checked and it is installed) and afterwards I got numerous module compilation errors as follows:

Building the vmblock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmblock-only'
make -C /lib/modules/2.6.25.3-18.fc9.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.25.3-18.fc9.x86_64'
CC /tmp/vmware-config0/vmblock-only/linux/block.o
CC /tmp/vmware-config0/vmblock-only/linux/control.o
CC /tmp/vmware-config0/vmblock-only/linux/dbllnklst.o
CC /tmp/vmware-config0/vmblock-only/linux/dentry.o
/tmp/vmware-config0/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:
/tmp/vmware-config0/vmblock-only/linux/dentry.c:101: error: ‘struct nameidata’ has no member named ‘dentry’
/tmp/vmware-config0/vmblock-only/linux/dentry.c:101: error: ‘struct nameidata’ has no member named ‘dentry’
/tmp/vmware-config0/vmblock-only/linux/dentry.c:102: error: implicit declaration of function ‘path_release’
make[2]: *** Error 1
make[1]: *** Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.25.3-18.fc9.x86_64'
make: *** http://vmblock.ko Error 2
make: Leaving directory `/tmp/vmware-config0/vmblock-only'
Unable to build the vmblock module.

Same happened while building the vmnet module as follows:

Building the vmnet module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmnet-only'
make -C /lib/modules/2.6.25.3-18.fc9.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.25.3-18.fc9.x86_64'
CC /tmp/vmware-config1/vmnet-only/driver.o
CC /tmp/vmware-config1/vmnet-only/hub.o
CC /tmp/vmware-config1/vmnet-only/userif.o
CC /tmp/vmware-config1/vmnet-only/netif.o
CC /tmp/vmware-config1/vmnet-only/bridge.o
/tmp/vmware-config1/vmnet-only/bridge.c: In function ‘VNetBridgeUp’:
/tmp/vmware-config1/vmnet-only/bridge.c:947: error: implicit declaration of function ‘sock_valbool_flag’
make[2]: *** Error 1
make[1]: *** Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.25.3-18.fc9.x86_64'
make: *** http://vmnet.ko Error 2
make: Leaving directory `/tmp/vmware-config1/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.

As you can see, I am not able to successfully install it.

Please help!

0 Kudos
30 Replies
dijxtra
Contributor
Contributor

This is just a FYI.

I 'solved' all previous problems by moving back to the Oracle version of RHL. Free available on

http://edelivery.oracle.com/linux

0 Kudos
whitneyp
Contributor
Contributor

I am trying to remember where I got the any-any-117-very-alpha patch. But, anyhow, the patch files and script were suposed to be copied to

/usr/lib/vmware/modules/source

From within there, you run the script:

vmware-2.6.25.sh

Hope this helps.

Paul M. Whitney

Paul M. Whitney
0 Kudos
waltc
Contributor
Contributor

That helps alot Paul, thanks!

I don't remember seeing any such instructions but it was clearly an anyany117. And there was no vmware-2.6.25.sh script. That may explain why it works fine for some and not at all for others. Odd but now there is something to differentiate versions of anyany117 with.

Thanks!

Walt

0 Kudos
whitneyp
Contributor
Contributor

So, did it compile for you?

Also, note that the version I used was really called

any-any-117-very-ALPHA.

Paul

Paul M. Whitney
0 Kudos
whitneyp
Contributor
Contributor

Walt,

If you want I can send the any-any update I used to you.

Paul

Paul M. Whitney
0 Kudos
waltc
Contributor
Contributor

That would be great, thanks Paul. Also, I see alot of references to people having to modify code, did you have to do anything other than run the any-any-117 whatever script?

Walt

0 Kudos
whitneyp
Contributor
Contributor

No I did not. Just the script.

What is the best way to get it to you or am I able to post on the forum?

P

Paul M. Whitney
0 Kudos
dpbjinc
Contributor
Contributor

The problems with X are probably because Fedora 9 uses a prerelease version of the X server, allegedly because it starts up faster. This has broken a lot of applications.

0 Kudos
SVRCFL
Contributor
Contributor

VMware Workstation 6.0.4 will compile fine, except for vmblock.

The 'easy' solution is to extract a previous vmware-any-any tarball, grab ONLY the vmblock code, and replace the vmblock.tar file (rpm -qil VMwareWorkstation). Then just run vmware-config.pl and it'll compile fine.

I believe patch level 115/116 will suffice.

0 Kudos
jonb
Contributor
Contributor

Hi,

I have the same problem, but with VMplayer on FC9 (x86_64) - I tried your suggestion of taking vmblock.tar from vmware-any-any-116 and replacing the one from vmplayer 2.0.4 in /usr/lib/vmware/modules/source, but when I try to recompile (with vmware-config.pl) I get exactly the same error message with vmblock compilation failing as per usual. Am I doing something stupid here? Should I even expect the VM workstation instructions to work for VMplayer?

Hope someone can help.

Cheers, Jon

0 Kudos
whitneyp
Contributor
Contributor

Jon,

If you are running VMplayer then is it safe to assume you are running VMworkstation? Also, I want to say I used vmware-any-any-117 alpha. I will have to check when I get home. But if I am correct, I can provide you with what I used and see if that helps. Did you read the README on where you need to place files and patch?

Paul M. Whitney
0 Kudos