Fusion 7.1 vmware-tools does not support kernel 3.1.9?

[loren_]

Using Fusion, trying to install vmware-tools, I'm not able to compile the vmhgfs module.  Apparently the headers changed and this is not supported.  I'm seeing numerous patches for this general problem out there:

Re: Linux host - Kernel 3.19 breaks VMware (vmnet)

vmware tools for guest fedora 16

But none of the patches seem to match up with the tools source in Fusion Version 7.1.1. Does vmware have a solution to this problem?

Below is the console output from my install:

Creating a new VMware Tools installer database using the tar4 format.

Installing VMware Tools.

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

[/usr/bin]

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

[/etc/rc.d]

What is the directory that contains the init scripts?

[/etc/rc.d/init.d]

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

[/usr/sbin]

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

[/usr/lib/vmware-tools]

The path "/usr/lib/vmware-tools" does not exist currently. This program is

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

[yes]

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

[/usr/share/doc/vmware-tools]

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

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

want? [yes]

The installation of VMware Tools 9.9.2 build-2496486 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-tools.pl".

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

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

this program to invoke the command for you now? [yes]

Initializing...

Making sure services for VMware Tools are stopped.

Stopping vmware-tools (via systemctl):                     [  OK  ]

Stopping Thinprint services in the virtual machine:

   Stopping Virtual Printing daemon:                                   done

The module vmci has already been installed on this system by another installer

or package and will not be modified by this installer.

The module vsock has already been installed on this system by another installer

or package and will not be modified by this installer.

The module vmxnet3 has already been installed on this system by another

installer or package and will not be modified by this installer.

The module pvscsi has already been installed on this system by another

installer or package and will not be modified by this installer.

The module vmmemctl has already been installed on this system by another

installer or package and will not be modified by this installer.

The VMware Host-Guest Filesystem allows for shared folders between the host OS

and the guest OS in a Fusion or Workstation virtual environment.  Do you wish

to enable this feature? [yes]

Before you can compile modules, you need to have the following installed...

make

gcc

kernel headers of the running kernel

Searching for GCC...

Detected GCC binary at "/bin/gcc".

The path "/bin/gcc" appears to be a valid path to the gcc binary.

Would you like to change it? [no]

Searching for a valid kernel header path...

Detected the kernel headers at

"/lib/modules/3.19.7-200.fc21.x86_64/build/include".

The path "/lib/modules/3.19.7-200.fc21.x86_64/build/include" appears to be a

valid path to the 3.19.7-200.fc21.x86_64 kernel headers.

Would you like to change it? [no]

make: Entering directory '/tmp/modconfig-XykZiy/vmhgfs-only'

Using kernel build system.

/bin/make -C /lib/modules/3.19.7-200.fc21.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

  MODULEBUILDDIR= modules

make[1]: Entering directory '/usr/src/kernels/3.19.7-200.fc21.x86_64'

  CC [M]  /tmp/modconfig-XykZiy/vmhgfs-only/message.o

  CC [M]  /tmp/modconfig-XykZiy/vmhgfs-only/dir.o

/tmp/modconfig-XykZiy/vmhgfs-only/dir.c: In function ‘HgfsPackDirOpenRequest’:

/tmp/modconfig-XykZiy/vmhgfs-only/dir.c:417:26: error: ‘struct file’ has no member named ‘f_dentry’

                      file->f_dentry) < 0) {

                          ^

/tmp/modconfig-XykZiy/vmhgfs-only/dir.c: In function ‘HgfsDirLlseek’:

/tmp/modconfig-XykZiy/vmhgfs-only/dir.c:707:32: error: ‘struct file’ has no member named ‘f_dentry’

    struct dentry *dentry = file->f_dentry;

                                ^

In file included from /tmp/modconfig-XykZiy/vmhgfs-only/dir.c:39:0:

/tmp/modconfig-XykZiy/vmhgfs-only/dir.c: In function ‘HgfsReaddirNextEntry’:

/tmp/modconfig-XykZiy/vmhgfs-only/dir.c:993:31: error: ‘struct file’ has no member named ‘f_dentry’

    si = HGFS_SB_TO_COMMON(file->f_dentry->d_inode->i_sb);

                               ^

/tmp/modconfig-XykZiy/vmhgfs-only/module.h:89:62: note: in definition of macro ‘HGFS_SB_TO_COMMON’

#define HGFS_SB_TO_COMMON(sb)             ((HgfsSuperInfo *)(sb)->s_fs_info)

                                                              ^

/tmp/modconfig-XykZiy/vmhgfs-only/dir.c:1082:26: error: ‘struct file’ has no member named ‘f_dentry’

          *entryIno = file->f_dentry->d_inode->i_ino;

                          ^

In file included from /tmp/modconfig-XykZiy/vmhgfs-only/dir.c:30:0:

/tmp/modconfig-XykZiy/vmhgfs-only/dir.c:1088:44: error: ‘struct file’ has no member named ‘f_dentry’

          *entryIno = compat_parent_ino(file->f_dentry);

                                            ^

/tmp/modconfig-XykZiy/vmhgfs-only/./shared/compat_fs.h:120:46: note: in definition of macro ‘compat_parent_ino’

#define compat_parent_ino(dentry) parent_ino(dentry)

                                              ^

/tmp/modconfig-XykZiy/vmhgfs-only/dir.c:1093:52: error: ‘struct file’ has no member named ‘f_dentry’

      *entryIno = HgfsGetFileInode(&entryAttrs, file->f_dentry->d_inode->i_sb);

                                                    ^

/tmp/modconfig-XykZiy/vmhgfs-only/dir.c: In function ‘HgfsDoReaddir’:

/tmp/modconfig-XykZiy/vmhgfs-only/dir.c:1173:13: error: ‘struct file’ has no member named ‘f_dentry’

       !(file->f_dentry) ||

             ^

/tmp/modconfig-XykZiy/vmhgfs-only/dir.c:1174:13: error: ‘struct file’ has no member named ‘f_dentry’

       !(file->f_dentry->d_inode)) {

             ^

scripts/Makefile.build:257: recipe for target '/tmp/modconfig-XykZiy/vmhgfs-only/dir.o' failed

make[2]: *** [/tmp/modconfig-XykZiy/vmhgfs-only/dir.o] Error 1

Makefile:1386: recipe for target '_module_/tmp/modconfig-XykZiy/vmhgfs-only' failed

make[1]: *** [_module_/tmp/modconfig-XykZiy/vmhgfs-only] Error 2

make[1]: Leaving directory '/usr/src/kernels/3.19.7-200.fc21.x86_64'

Makefile:120: recipe for target 'vmhgfs.ko' failed

make: *** [vmhgfs.ko] Error 2

make: Leaving directory '/tmp/modconfig-XykZiy/vmhgfs-only'

The filesystem driver (vmhgfs module) is used only for the shared folder

feature. The rest of the software provided by VMware Tools is designed to work

independently of this feature.

If you wish to have the shared folders feature, you can install the driver by

running vmware-config-tools.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.

[ Press Enter key to continue ]