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

[zufi007]

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!

[dijxtra]

I have exactly the same problem : VMWare Workstation complains about a couple of Xlibs that it can not find but are installed.

This is has been described before:

0 64733429

I think something changed in the X packages on fedora9. I also have Oracle EL 4 installed (x86_64) and it does have the package

xorg-x11-libs-6.8.1-23.EL installed. Thing is .. it does not exist on the Fedora 9 CD...

-

---

I tried updating the path etc no luck. I need a fix for this urgently as can't fire up my test machines.

[SVRCFL]

You can find the packages with "yum provides (file name)", and may need to specify the i386 versions to get vmware-config running properly.

You may want to run VMware 6.5, beta 2 if you run into more issues.

[dijxtra]

-

---

# yum provides libX11.so.6

Loaded plugins: refresh-packagekit

fedora | 2.4 kB 00:00

updates | 2.3 kB 00:00

libX11.i386 : X.Org X11 libX11 runtime library

# rpm -qa | grep libX11

libX11-devel-1.1.4-1.fc9.x86_64

libX11-1.1.4-1.fc9.x86_64

# yum install libX11.i386

Loaded plugins: refresh-packagekit

Setting up Install Process

Parsing package install arguments

Resolving Dependencies

......

<output cut> Installed ok.

-

---

<snip>

Before running VMware Workstation for the first time, you need to configure it

by invoking the following command: "/usr/bin/vmware-config.pl". Do you want

this program to invoke the command for you now?

The following libraries could not be found on your system:

libXtst.so.6

libXext.so.6

libXrender.so.1

libz.so.1

You will need to install these manually before you can run VMware Workstation.

</snip>

-

---

# strace -o vmInstall.out vmware-config.pl

The following libraries could not be found on your system:

libXtst.so.6

libXext.so.6

libXrender.so.1

libz.so.1

You will need to install these manually before you can run VMware Workstation.

Press enter to continue.

<killed this later but first copied the vmInstall.out file away>

-

---

From truss:

ioctl(4, SNDCTL_TMR_TIMEBASE or TCGETS, 0x7ffff2c93ca0) = -1 EINVAL (Invalid argument)

lseek(4, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)

fstat(4, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0

read(4, "\tlinux-gate.so.1 => (0x0012e000"..., 4096) = 34

read(4, "\tlibm.so.6 => /lib/libm.so.6 (0x"..., 4096) = 42

read(4, "\tlibdl.so.2 => /lib/libdl.so.2 ("..., 4096) = 44

read(4, "\tlibpthread.so.0 => /lib/libpthr"..., 4096) = 54

read(4, "\tlibc.so.6 => /lib/libc.so.6 (0x"..., 4096) = 42

read(4, "\t/lib/ld-linux.so.2 (0x00110000)"..., 4096) = 33

read(4, "\tlibX11.so.6 => /usr/lib/libX11."..., 4096) = 50

read(4, "\tlibXtst.so.6 => not found\n", 4096) = 27

read(4, "\tlibXext.so.6 => not found\n", 4096) = 27

read(4, "\tlibXrender.so.1 => not found\n", 4096) = 30

read(4, "\tlibz.so.1 => not found\n", 4096) = 24

read(4, "\tlibxcb-xlib.so.0 => /usr/lib/li"..., 4096) = 60

read(4, "\tlibxcb.so.1 => /usr/lib/libxcb."..., 4096) = 50

read(4, "\tlibXau.so.6 => /usr/lib/libXau."..., 4096) = 50

read(4, "\tlibXdmcp.so.6 => /usr/lib/libXd"..., 4096) = 54

read(4, "", 4096) = 0

fstat(4, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0

close(4) = 0

rt_sigaction(SIGHUP, , , 😎 = 0

rt_sigaction(SIGINT, , , 😎 = 0

rt_sigaction(SIGQUIT, , , 😎 = 0

wait4(3128, , 0, NULL) = 3128

--- SIGCHLD (Child exited) @ 0 (0) ---

rt_sigaction(SIGHUP, , NULL, 😎 = 0 rt_sigaction(SIGINT, , NULL, 😎 = 0

rt_sigaction(SIGQUIT, , NULL, 😎 = 0

write(1, "The following libraries could no"..., 59) = 59

write(1, "libXtst.so.6\nlibXext.so.6\nlibXre"..., 42) = 42

write(1, "libz.so.1\n\n", 11) = 11

write(1, "You will need to install these m"..., 80) = 80

write(1, "Press enter to continue. ", 25) = 25

-

---

So I have a broad hint here (..) however I would like VMWare/Fedora on what would be the best way to fix it!

Sounds like another "ln -s link-it party" but I'm still not sure.

I hope VMWare support /eng will make the efford ; install fedora9 etc. thanks.

[O_o]

I'm not sure what you did or didn't try yet ... But it's just as previous poster mentioned.

You need to install the missing libs manualy ... for example: yum install libXtst.so.6

[zufi007]

I did try it in the beginning and like my first post mentioned I do have libXtst.so.6 installed (only 64 bit version). But after doing some more googling and debugging tips from dijxtra using strace I was able to figure out that even the VMWare 64 bit version requires a 32 bit version of libXtst.so.6!

So, all I had to do to fix this dependency was to install the 32 bit version:

#yum install libXtst.i386

That fixed one bit but the next ones are most critical. The vmblock module dentry.o and vmnet-only module bridge.o still fail to compile as mentioned in my first posting.

VMWare, please fix this!!!!

[dijxtra]

I finall got passed the 32 bit stuff (that is to say the installer does not complain).

Building vmblock & vmnet fails.

zufi007: are you using RPM ? If not then pls post your install to.

-

---

/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

-

---

/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'

-

---

Installing VMware Workstation.

In which directory do you want to install the binary files?

What is the directory that contains the init directories (rc0.d/ to rc6.d/)?

What is the directory that contains the init scripts?

In which directory do you want to install the daemon files?

In which directory do you want to install the library files?

The path "/usr/lib/vmware" does not exist currently. This program is going to

create it, including needed parent directories. Is this what you want?

In which directory do you want to install the manual files?

In which directory do you want to install the documentation files?

The path "/usr/share/doc/vmware" does not exist currently. This program is

going to create it, including needed parent directories. Is this what you want?

The installation of VMware Workstation 6.0.3 build-80004 for Linux completed

successfully. You can decide to remove this software from your system at any

time by invoking the following command: "/usr/bin/vmware-uninstall.pl".

Before running VMware Workstation for the first time, you need to configure it

by invoking the following command: "/usr/bin/vmware-config.pl". Do you want

this program to invoke the command for you now?

Making sure services for VMware Workstation are stopped.

Stopping VMware services:

Virtual machine monitor

Configuring fallback GTK+ 2.4 libraries.

In which directory do you want to install the theme icons?

What directory contains your desktop menu entry files? These files have a

.desktop file extension.

In which directory do you want to install the application's icon?

Trying to find a suitable vmmon module for your running kernel.

None of the pre-built vmmon modules for VMware Workstation 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)?

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?

Extracting the sources of the vmmon module.

Building the vmmon module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config0/vmmon-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/vmmon-only/linux/driver.o

CC /tmp/vmware-config0/vmmon-only/linux/hostif.o

CC /tmp/vmware-config0/vmmon-only/common/comport.o

CC /tmp/vmware-config0/vmmon-only/common/cpuid.o

CC /tmp/vmware-config0/vmmon-only/common/hash.o

CC /tmp/vmware-config0/vmmon-only/common/memtrack.o

CC /tmp/vmware-config0/vmmon-only/common/phystrack.o

CC /tmp/vmware-config0/vmmon-only/common/task.o

CC /tmp/vmware-config0/vmmon-only/common/vmciContext.o

CC /tmp/vmware-config0/vmmon-only/common/vmciDatagram.o

CC /tmp/vmware-config0/vmmon-only/common/vmciDriver.o

CC /tmp/vmware-config0/vmmon-only/common/vmciDs.o

CC /tmp/vmware-config0/vmmon-only/common/vmciGroup.o

CC /tmp/vmware-config0/vmmon-only/common/vmciHashtable.o

CC /tmp/vmware-config0/vmmon-only/common/vmciProcess.o

CC /tmp/vmware-config0/vmmon-only/common/vmciResource.o

CC /tmp/vmware-config0/vmmon-only/common/vmciSharedMem.o

CC /tmp/vmware-config0/vmmon-only/common/vmx86.o

CC /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o

LD /tmp/vmware-config0/vmmon-only/vmmon.o

Building modules, stage 2.

MODPOST 1 modules

CC /tmp/vmware-config0/vmmon-only/vmmon.mod.o

LD /tmp/vmware-config0/vmmon-only/vmmon.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.25.3-18.fc9.x86_64'

cp -f vmmon.ko ./../vmmon.o

make: Leaving directory `/tmp/vmware-config0/vmmon-only'

The module loads perfectly in the running kernel.

/dev is dynamic:

Trying to find a suitable vmblock module for your running kernel.

None of the pre-built vmblock modules for VMware Workstation is suitable for

your running kernel. Do you want this program to try to build the vmblock

module for your system (you need to have a C compiler installed on your

system)?

Extracting the sources of the vmblock module.

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.

The vmblock module enables dragging or copying files from within a guest and

dropping or pasting them onto your host (guest to host drag and drop and file

copy/paste). The rest of the software provided by VMware Workstation is

designed to work independently of this feature (including host to guest drag

and drop and file copy/paste).

If you would like the guest to host drag and drop and file copy/paste features,

you can install the driver by running vmware-config.pl again after making sure

that gcc, binutils, make and the kernel sources for your running kernel are

installed on your machine. These packages are available on your distribution's

installation CD.

/dev is dynamic:

Do you want networking for your virtual machines? (yes/no/help)

Configuring a bridged network for vmnet0.

Your computer has multiple ethernet network interfaces available: eth0, eth1,

eth2. Which one do you want to bridge to vmnet0?

The following bridged networks have been defined:

. vmnet0 is bridged to eth0

Do you wish to configure another bridged network? (yes/no) y

Configuring a bridged network for vmnet2.

Your computer has multiple ethernet network interfaces available: eth1, eth2.

Which one do you want to bridge to vmnet2? eth1

The following bridged networks have been defined:

. vmnet0 is bridged to eth0

. vmnet2 is bridged to eth1

Do you wish to configure another bridged network? (yes/no) yes

Configuring a bridged network for vmnet3.

The following bridged networks have been defined:

. vmnet0 is bridged to eth0

. vmnet2 is bridged to eth1

. vmnet3 is bridged to eth2

All your ethernet interfaces are already bridged.

Do you want to be able to use NAT networking in your virtual machines? (yes/no)

no

Do you want to be able to use host-only networking in your virtual machines?

no

Trying to find a suitable vmnet module for your running kernel.

None of the pre-built vmnet modules for VMware Workstation is suitable for your

running kernel. Do you want this program to try to build the vmnet module for

your system (you need to have a C compiler installed on your system)?

Extracting the sources of the vmnet module.

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.

#

-

---

[zufi007]

I am using the RPM distribution dijxtra. But the problem is not with the RPM or the TAR distribution itself in my opinion, rather with the vmblock and vmnet modules themselves. I am trying a few things out and will keep you posted with the updates.

You might wanna have a look at http://groups.google.com/group/vmkernelnewbies/browse_thread/thread/63ee12437c4f165e

[SVRCFL]

FWIW, observed tests of 6.0.3 (x86_64) on Fedora 9 (2.6.25.3-18.fc9) haven't been all that great (same results as yours). 6.5 Beta 2 is fine and even though it's in debugging mode, appears to run decently on a dual core system.

Unless there's a newer vmware-any-any-update patch released, if you're bent on running Fedora 9 with VMware Workstation 6.0.3, you might want to just install the last Fedora 8 2.6.24 kernel until either a patch or 6.5 is released.

[dijxtra]

zufi007j thanks.

SVRCFL I think I may take your advise and try beta.

I have a look at the new kernel (again tried couple a days ago but I know a bit more now).

The only reason for fedora 9 is hardware;

Oracle Unbreakable Linux 5.1 is what I intended to run but it will not install (some other pain) so I thought to be cleaver and " just take fedora 9" ..

[AllBlack]

I have the same problem on a 32-bit fc9 install. Fresh OS install, 2.6.25.3-18 kernel.

VM workstation 6.0.0 build-45731, any-any patch 117

Keep getting this error

Version mismatch with vmmon module: expecting 161.0, got 167.0.

You have an incorrect version of the `vmmon' kernel module.

Try reinstalling VMware Workstation.

Very frustrating

[O_o]

I'm running the latest Fedora Core 9 with kernel 2.6.25.x ... with vmware workstation 6.0.3 without a problem now ...

What I did to get it working:

Downloaded the latest Workstation (6.0.3), unpacked it, and ran the installer (./vmware-install) ... I stopped the install when it wanted to run the ./vmware-config ... Then I ran the any-any-patch-116, but again stopped it when it wanted to run the ./vmware-config.

After this, I ran the any-any-patch-117-very-ALPHA found here: http://blog.creonfx.com/linux/how-to-install-vmware-player-workstation-on-2625-kernel

Low and behold, vmware workstation got installed without a problem.

Hope this helps someone !

[zufi007]

Are you running the 32 bit version of Fedora or the 64 bit one 0_o ? Because the vmblock is still causing problems and insmod caused segmentation fault in the kernel..... setup aborted. So, it is not working for me with the same kernel as you have....

[O_o]

I'm running the x64 bit kernel ... 2.6.25.3-18.fc9.x86_64 to be precise ... I can't say more then what I did before ... only thing you'll need to do though, is change the paths of the patches if you're running x64, instead of lib, it should be lib64 and so on ...

[waltc]

I downloaded the anyany17 and ran the ./runme.pl in the anyany subdir and everything compiled correctly and ended with the "Enjoy!" from the VMWare developers, or whatever that signature is. Problem is every time I try to start a vm I get a cryptic message "Unable to change virtual machine power state: Failed to connect to peer process." when started from the GUI. When started from cmd line nothing happens. Since I actually bought this puppy I am highly expectant the fine folks at VMWare will be more motivated to provide a solution. This is 64 bit version. Funny thing is I was running the trial version of Workestation 6.03 on Ubuntu 8.04 with no problems. I saw anecdotal entries to install the ia32 package, which yum doesn't appear to know about and to add user to vmware group, which doesn't even exist. What's odd is, to my knowledge, Fedora 9 is essentially RHEL5 in that Fedora, Ubuntu and RHEL5 are all using the same kernel. I couldn't get VMServer to compile at all. Hey, ya gets what ya pay for. What I fear is, strictly speaking, they could claim F9 is not supported as a host.

Has anyone gotten this to work and start vm's using F9-64 as the host? I don't even know what that message means and there are no logs or other bread crumbs as to what is actually going on. If KVM supported sound and could access external window shares this wouldn't be an issue, but I digress. I don't believe when you pay for something you are paying for the right or obligation to hack scripts, tarballs, and/or install packages in order to get it to work. I am not real happy with VMWare right now.

[Corsac]

On 2.6.25-2-md64 (debian sid), using the just released workstation 6.0.4, vmnet and vmmon build fine, while vmblock still fails to build with the same errors:

/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’

[whitneyp]

This is exactly what I needed. Worked like a champ for me following the procedures for the any-any-patch-117-very-ALPHA. I was a little concerned with the script generating Hunk errors. But nevertheless, when I ran the vmware-config.pl script, everything compiled perfectly.

Thank you!

Paul M. Whitney

[waltc]

When you said, "this is just what I needed", were you referring to the recently released 6.04 WITH the anyany117 patch? I have had virtually no success with 6.03 under F9. I did get it to compile cleanly with anyany117 but have seen many crashes/ fatal errors in vm's during execution. It's very fragile in my estimation. What concerns me is some anecdotal comments seem to indicate other have it working reliably. I am very confused on this issue. ANy help would be appreciated.

Walt

[whitneyp]

Walt,

I got VMware 6.04 with anyany117 patch working. All I did was install 6.04, download anyany117 and follow procedures for extracting and running the script. When running the script, I got output indicating items patched with Hunk errors.

After it was patched, I launched VMware and successfully started RHEL 4 and RHEL 5.

VMware 6.03 I believe is not meant for F9. Save yourself grief, get 6.04, get anyany117 and patch. It should work fine.

Paul M. Whitney

[waltc]

I can not tell you how badly I want this to work. I downloaded the rpm version of 6.04 and ran package installer against it. I had downloaded the anyany117 tarball some time back so it's in its own subdir off my home dir. I don't recall seeing or reading any installation notes simply there was a runme.pl, update (binary) and some tar files for vmmon, vmblock, and vmnet.

So I ran the runme.pl and it,again, failed when compiling dentry.c. Here is the output:

Extracting the sources of the vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config21/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-config21/vmblock-only/linux/block.o

CC /tmp/vmware-config21/vmblock-only/linux/control.o

CC /tmp/vmware-config21/vmblock-only/linux/dbllnklst.o

CC /tmp/vmware-config21/vmblock-only/linux/dentry.o

/tmp/vmware-config21/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:

/tmp/vmware-config21/vmblock-only/linux/dentry.c:115: error: ‘struct nameidata’ has no member named ‘dentry’

/tmp/vmware-config21/vmblock-only/linux/dentry.c:115: error: ‘struct nameidata’ has no member named ‘dentry’

/tmp/vmware-config21/vmblock-only/linux/dentry.c:116: 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-config21/vmblock-only'

Unable to build the vmblock module.

And you no longer have this problem? I am very confused now. Any help would be appreciated.

Walt