Open-vm-tools/official vmware tools not installing.

I'm trying to install the latest offical vmware tools (16/9/2013) and open-vm-tools but both seem to always fail. I tried some of the patches listed on the wiki, but nothing got me anywhere. The big thing I'm trying to accomplish is to be able to use vmhgfs but, I'd like to have all the tools if possible. Here is what I did.
Open Vm Tools
#[root@localhost] - [14-01-01 18:09:33] - [/home/toxicarrow/Documents/firewall] - [R:0]
pacman -S open-vm-tools open-vm-tools-dkms
resolving dependencies...
looking for inter-conflicts...
Packages (2): open-vm-tools-5:2013.09.16-5 open-vm-tools-dkms-5:2013.09.16-5
Total Installed Size: 8.21 MiB
:: Proceed with installation? [Y/n]
(2/2) checking keys in keyring [#####################################################################################################################] 100%
(2/2) checking package integrity [#####################################################################################################################] 100%
(2/2) loading package files [#####################################################################################################################] 100%
(2/2) checking for file conflicts [#####################################################################################################################] 100%
(2/2) checking available disk space [#####################################################################################################################] 100%
(1/2) installing open-vm-tools [#####################################################################################################################] 100%
>>>
>>> You can mount VMware Shared Folders via:
>>> mount -t vmhgfs .host:/ /mnt/hgfs
>>>
>>> or by adding this line to /etc/fstab:
>>> .host:/ /mnt/hgfs vmhgfs defaults 0 0
>>>
Optional dependencies for open-vm-tools
gtkmm [installed]
libnotify [installed]
libxtst [installed]
fuse [installed]
libsm [installed]
open-vm-tools-modules: for linux kernel
open-vm-tools-dkms: for linux-lts and other kernels [pending]
netctl: suspend-resume network state [installed]
networkmanager: suspend-resume network state
(2/2) installing open-vm-tools-dkms [#####################################################################################################################] 100%
>>> Enable building of open-vm-tools modules:
>>> $ dkms add open-vm-tools/2013.09.16
>>>
>>> Enabling vmxnet driver in /usr/lib/modprobe.d/open-vm-tools-modules.conf
>>> (this will disable pcnet32 driver)
>>>
>>> If vmxnet driver doesn't handle your NIC, you have to manually
>>> disable loading of pcnet32 driver
>>>
#[root@localhost] - [14-01-01 18:09:47] - [/home/toxicarrow/Documents/firewall] - [R:0]
pacman -S open-vm-tools-modules
warning: open-vm-tools-dkms-5:2013.09.16-5 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Packages (1): open-vm-tools-dkms-5:2013.09.16-5
Total Installed Size: 5.57 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [#####################################################################################################################] 100%
(1/1) checking package integrity [#####################################################################################################################] 100%
(1/1) loading package files [#####################################################################################################################] 100%
(1/1) checking for file conflicts [#####################################################################################################################] 100%
(1/1) checking available disk space [#####################################################################################################################] 100%
(1/1) reinstalling open-vm-tools-dkms [#####################################################################################################################] 100%
>>> Enable building of open-vm-tools modules:
>>> $ dkms add open-vm-tools/2013.09.16
>>>
#[root@localhost] - [14-01-01 18:10:14] - [/home/toxicarrow/Documents/firewall] - [R:0]
dkms install -m open-vm-tools -v 2013.04.16 -k $(uname -r)
Error! Could not find module source directory.
Directory: /usr/src/open-vm-tools-2013.04.16 does not exist.
#[root@localhost] - [14-01-01 18:13:14] - [/home/toxicarrow/Documents/firewall] - [R:2]
dkms install -m open-vm-tools -v 2013.09.16 -k $(uname -r)
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area....
make KERNELRELEASE=3.12.6-1-ARCH VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmblock; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmci; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmhgfs; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmsync; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmxnet; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vsock........
Error! Build of vmblock.ko failed for: 3.12.6-1-ARCH (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/open-vm-tools/2013.09.16/build/ for more information.
#[root@localhost] - [14-01-01 18:13:45] - [/home/toxicarrow/Documents/firewall] - [R:7]
Official Tools
Before patches
#[root@localhost] - [14-01-02 2:40:49] - [/home/toxicarrow/vmware/vmware-tools-distrib] - [R:32]
./vmware-install.pl
A previous installation of VMware Tools has been detected.
The previous installation was made by the tar installer (version 4).
Keeping the tar4 installer database format.
You have a version of VMware Tools installed. Continuing this install will
first uninstall the currently installed version. Do you wish to continue?
(yes/no) [yes]
Uninstalling the tar installation of VMware Tools.
Stopping services for VMware Tools
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
VM communication interface socket family: done
VM communication interface: done
Stopping Thinprint services in the virtual machine:
Stopping Virtual Printing daemon: done
The removal of VMware Tools 9.6.1 build-1378637 for Linux completed
successfully.
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/init.d]
What is the directory that contains the init scripts?
[/etc/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.6.1 build-1378637 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 services in the virtual machine:
Guest operating system daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
VM communication interface socket family: done
VM communication interface: done
Stopping Thinprint services in the virtual machine:
Stopping Virtual Printing daemon: done
sh: : command not found
sh: : command not found
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.12.6-1-ARCH/build/include".
The path "/lib/modules/3.12.6-1-ARCH/build/include" appears to be a valid path
to the 3.12.6-1-ARCH kernel headers.
Would you like to change it? [no]
make: Entering directory '/tmp/modconfig-lyoMIO/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-lyoMIO/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/driverLog.o
LD [M] /tmp/modconfig-lyoMIO/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-lyoMIO/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-lyoMIO/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-lyoMIO/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-lyoMIO/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-lyoMIO/vmci-only'
make: Entering directory '/tmp/modconfig-VlEWPD/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-VlEWPD/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/driverLog.o
LD [M] /tmp/modconfig-VlEWPD/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-VlEWPD/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-VlEWPD/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-VlEWPD/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-VlEWPD/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-VlEWPD/vmci-only'
make: Entering directory '/tmp/modconfig-VlEWPD/vsock-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/af_vsock.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/vsockAddr.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/notifyQState.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/util.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/stats.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/notify.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/driverLog.o
LD [M] /tmp/modconfig-VlEWPD/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-VlEWPD/vsock-only/vsock.mod.o
LD [M] /tmp/modconfig-VlEWPD/vsock-only/vsock.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-VlEWPD/vsock-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-VlEWPD/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory '/tmp/modconfig-VlEWPD/vsock-only'
The module vmxnet3 from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module pvscsi from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module vmmemctl from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
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]
make: Entering directory '/tmp/modconfig-C1YUSD/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-C1YUSD/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/driverLog.o
LD [M] /tmp/modconfig-C1YUSD/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-C1YUSD/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-C1YUSD/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-C1YUSD/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-C1YUSD/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-C1YUSD/vmci-only'
make: Entering directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/message.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/rpcout.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/cpName.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/request.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/stubs.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/link.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/bdhandler.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/transport.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/module.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/file.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/super.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/vmci.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/dir.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/fsutil.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/hgfsBd.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/filesystem.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/page.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/backdoorGcc64.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/backdoor.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/hgfsEscape.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/inode.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/dentry.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/cpNameLite.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/kernelStubsLinux.o
LD [M] /tmp/modconfig-C1YUSD/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-C1YUSD/vmhgfs-only/vmhgfs.mod.o
LD [M] /tmp/modconfig-C1YUSD/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
The vmxnet driver is no longer supported on kernels 3.3 and greater. Please
upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)
The vmblock enables dragging or copying files between host and guest in a
Fusion or Workstation virtual environment. Do you wish to enable this feature?
[yes]
NOTICE: It appears your system does not have the required fuse packages
installed. The VMware blocking filesystem requires the fuse packages and its
libraries to function properly. Please install the fuse or fuse-utils package
using your systems package management utility and re-run this script in order
to enable the VMware blocking filesystem.
VMware automatic kernel modules enables automatic building and installation of
VMware kernel modules at boot that are not already present. This feature can be
enabled/disabled by re-running vmware-config-tools.pl.
Would you like to enable VMware automatic kernel modules?
[no]
Detected X server version 1.14.5
Distribution provided drivers for Xorg X server are used.
Skipping X configuration because X drivers are not included.
Warning: This script could not find mkinitrd or update-initramfs and cannot
remake the initrd file!
Checking acpi hot plug done
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
VM communication interface: done
VM communication interface socket family: failed
Guest filesystem driver: failed
Mounting HGFS shares: failed
VMware User Agent: done
Guest operating system daemon: done
Unable to start services for VMware Tools
Execution aborted.
After patches
#[root@localhost] - [14-01-02 2:44:39] - [/home/toxicarrow/vmware] - [R:0]
git clone https://github.com/rasa/vmware-tools-patches.git
Cloning into 'vmware-tools-patches'...
remote: Reusing existing pack: 134, done.
remote: Total 134 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (134/134), 22.06 KiB | 0 bytes/s, done.
Resolving deltas: 100% (74/74), done.
Checking connectivity... done.
#[root@localhost] - [14-01-02 2:44:55] - [/home/toxicarrow/vmware] - [R:0]
ls
= VMwareTools-9.6.1-1378637.tar.gz manifest.txt* run_upgrader.sh vmware-tools-distrib/ vmware-tools-patches/ vmware-tools-upgrader-32* vmware-tools-upgrader-64*
#[root@localhost] - [14-01-02 2:44:57] - [/home/toxicarrow/vmware] - [R:0]
cp VMwareTools-9.6.1-1378637.tar.gz vmware-tools-patches
#[root@localhost] - [14-01-02 2:45:13] - [/home/toxicarrow/vmware] - [R:0]
cd vmware-tools-patches
#[root@localhost] - [14-01-02 2:45:17] - [/home/toxicarrow/vmware/vmware-tools-patches] - [R:0]
ls
LICENSE VMwareTools-9.6.1-1378637.tar.gz patch-module.sh* patches/ untar-and-patch-and-compile.sh*
README.md download-patches.sh* patch-modules.sh* untar-all-and-patch.sh* untar-and-patch.sh*
#[root@localhost] - [14-01-02 2:45:18] - [/home/toxicarrow/vmware/vmware-tools-patches] - [R:0]
./untar-and-patch-and-compile.sh
=== Patching ./VMwareTools-9.6.1-1378637.tar.gz ...
--- Applying vmci/vmware9.k3.8rc4.patch ...
patching file linux/driver.c
Hunk #1 FAILED at 124.
Hunk #2 FAILED at 1750.
Hunk #3 FAILED at 1978.
3 out of 3 hunks FAILED -- saving rejects to file linux/driver.c.rej
--- Applying vmhgfs/vmhgfs-uid-gid-kernel-3.12-tools-9.6.1.patch ...
patching file file.c
patching file filesystem.c
patching file fsutil.c
patching file inode.c
Hunk #1 succeeded at 514 (offset -3 lines).
Hunk #2 succeeded at 617 (offset -3 lines).
Hunk #3 succeeded at 1216 (offset -3 lines).
patching file shared/compat_cred.h
--- Applying vmhgfs/vmhgfs-d_count-kernel-3.11-tools-9.6.0.patch ...
patching file inode.c
Hunk #1 succeeded at 31 with fuzz 1.
Hunk #2 FAILED at 1893.
Hunk #3 FAILED at 1946.
2 out of 3 hunks FAILED -- saving rejects to file inode.c.rej
--- Applying vmhgfs/vmware9.compat_mm.patch ...
patching file shared/compat_mm.h
Hunk #1 FAILED at 91.
Hunk #2 FAILED at 100.
2 out of 2 hunks FAILED -- saving rejects to file shared/compat_mm.h.rej
--- Applying vmhgfs/patch_inode.c.patch ...
patching file inode.c
Hunk #1 FAILED at 1798.
Hunk #2 FAILED at 1818.
2 out of 2 hunks FAILED -- saving rejects to file inode.c.rej
--- Applying vmblock/vmblock.3.11.patch ...
patching file linux/file.c
--- Applying vmblock/vmblock.3.10.patch ...
patching file linux/control.c
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/init.d]
What is the directory that contains the init scripts?
[/etc/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.6.1 build-1378637 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 services in the virtual machine:
Guest operating system daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
Stopping Thinprint services in the virtual machine:
Stopping Virtual Printing daemon: done
sh: : command not found
sh: : command not found
make: Entering directory '/tmp/modconfig-HrsGw6/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-HrsGw6/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/driverLog.o
LD [M] /tmp/modconfig-HrsGw6/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-HrsGw6/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-HrsGw6/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-HrsGw6/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-HrsGw6/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-HrsGw6/vmci-only'
make: Entering directory '/tmp/modconfig-pVUBEq/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-pVUBEq/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/driverLog.o
LD [M] /tmp/modconfig-pVUBEq/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-pVUBEq/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-pVUBEq/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-pVUBEq/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-pVUBEq/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-pVUBEq/vmci-only'
make: Entering directory '/tmp/modconfig-pVUBEq/vsock-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/af_vsock.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/vsockAddr.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/notifyQState.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/util.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/stats.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/notify.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/driverLog.o
LD [M] /tmp/modconfig-pVUBEq/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-pVUBEq/vsock-only/vsock.mod.o
LD [M] /tmp/modconfig-pVUBEq/vsock-only/vsock.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-pVUBEq/vsock-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-pVUBEq/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory '/tmp/modconfig-pVUBEq/vsock-only'
The module vmxnet3 from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module pvscsi from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module vmmemctl from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
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]
make: Entering directory '/tmp/modconfig-ukgHfB/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-ukgHfB/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/driverLog.o
LD [M] /tmp/modconfig-ukgHfB/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-ukgHfB/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-ukgHfB/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-ukgHfB/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-ukgHfB/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-ukgHfB/vmci-only'
make: Entering directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/backdoorGcc64.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/message.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/request.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/filesystem.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/cpName.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/dentry.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/rpcout.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/stubs.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/hgfsEscape.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/link.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/transport.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/module.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/file.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/super.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/vmci.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/bdhandler.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/dir.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/fsutil.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/hgfsBd.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/page.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/backdoor.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/inode.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/cpNameLite.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/kernelStubsLinux.o
LD [M] /tmp/modconfig-ukgHfB/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-ukgHfB/vmhgfs-only/vmhgfs.mod.o
LD [M] /tmp/modconfig-ukgHfB/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
The vmxnet driver is no longer supported on kernels 3.3 and greater. Please
upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)
The vmblock enables dragging or copying files between host and guest in a
Fusion or Workstation virtual environment. Do you wish to enable this feature?
[yes]
NOTICE: It appears your system does not have the required fuse packages
installed. The VMware blocking filesystem requires the fuse packages and its
libraries to function properly. Please install the fuse or fuse-utils package
using your systems package management utility and re-run this script in order
to enable the VMware blocking filesystem.
VMware automatic kernel modules enables automatic building and installation of
VMware kernel modules at boot that are not already present. This feature can be
enabled/disabled by re-running vmware-config-tools.pl.
Would you like to enable VMware automatic kernel modules?
[no]
Detected X server version 1.14.5
Distribution provided drivers for Xorg X server are used.
Skipping X configuration because X drivers are not included.
Warning: This script could not find mkinitrd or update-initramfs and cannot
remake the initrd file!
Checking acpi hot plug done
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
VM communication interface: done
VM communication interface socket family: failed
Guest filesystem driver: failed
Mounting HGFS shares: failed
Guest operating system daemon: done
Unable to start services for VMware Tools
Execution aborted.
#[root@localhost] - [14-01-02 2:46:53] - [/home/toxicarrow/vmware/vmware-tools-patches] - [R:0]
Any idea what I should be doing?

I have the same problem on ESXI 5.5 for over a month now, tried the patches, tried the LTS kernel which others say results in an immediate result without patches, nothing seems to work and nobody seems to be able to offer a solution.
Did you make any progress ??
Error! Build of vmblock.ko failed for: 3.10.25-1-lts (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/open-vm-tools/2013.09.16/build/ for more information.
make[2]: *** No rule to make target '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/linux/inode', needed by '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/vmblock.o'. Stop.
Makefile:1224: recipe for target '_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock' failed
make[1]: *** [_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock] Error 2
make[1]: Leaving directory '/usr/src/linux-3.10.25-1-lts'
Makefile:120: recipe for target 'vmblock.ko' failed
Last edited by crankshaft (2014-01-10 11:32:32)

Similar Messages

  • My itunes has gotten error 7 (windows error 14001) itunes wont even open it just says itunes was not installed correctly. someone help please

    my itunes has gotten error 7 (windows error 14001) itunes wont even open it just says itunes was not installed correctly. someone help please

    For general advice see Troubleshooting issues with iTunes for Windows updates.
    The steps in the second box are a guide to removing everything related to iTunes and then rebuilding it which is often a good starting point unless the symptoms indicate a more specific approach. Review the other boxes and the list of support documents further down the page in case one of them applies.
    The further information area has direct links to the current and recent builds in case you have problems downloading, need to revert to an older version or want to try the iTunes for Windows (64-bit - for older video cards) (not for XP) release as a workaround for installation or performance issues, or compatibility with QuickTime or third party software.
    Your library should be unaffected by these steps but there are also links to backup and recovery advice should it be needed.
    tt2

  • Server Administration tools 10.4.11 not installing properly on 10.4.11

    I have a 10.4.11 PPC OS X Server on an XServe, as reported by About this Mac, but the Server Admin tools are not at that version level. I want to upgrade them to the latest version. The Server Admin is at 10.4.7 and the Workgroup Manager is at 10.4.4. I downloaded the 10.4.11 toolset from Apple and attempted an upgrade, but there was no change in the tools' version numbers! I installed them on a different "clean" 10.4.11 and the toolset installed perfectly.
    Thinking there was an object conflict, I copied /Applications/Server to /Applications/ServerOriginal and cleaned out the original /Server folder, then reran the installation. Still no change!
    Is there some kind of configuration file, plist, or something that's preventing the update? Any ideas appreciated. Thanks.

    Greetings,
    Thanks for posting this I was so frustrated but now because of your post I wont have to go half way across the building with a monitor mouse and keyboard just to add a user.
    Thanks so much.
    Sincerely,
    Jake.

  • Office 2010 Proofing Tools - Language appears as not installed

    Hi everyone,
    let me start by saying that I have searched throughout Google and especially these forums and still haven't found a solution to my problem. We have purchased (at work) 7 new PCs with Windows 7 (64-bit) Office 2010 AND Proofing Tools already installed. To
    cut a long story short, I've gone through the Control Panel->Add/Remove Programs and added the Greek Language (Run From my Computer). After that completes successfully, when I go in the Office 2010 Language Preferences the Greek Language Proofing Tools
    still show up as Not Installed. 
    I've tried all the suggestions in the forum (Registry tweaks, Control Panel) but nothing works. I have seen other users with this issue in various forums and I would really appreciate if anyone can provide any suggestions on it.
    Thank you very much for your time.

    Same problem here. I've just upgraded from Windows 7 to Windows 8.1, so I had to reinstall all of my software, including Office 2010 English language with added Italian proofing tools. Of course, when I reistalled, my Italian proofing tools were gone. I
    clicked on the link found under the options\language menu ("not installed") and downloaded "Italian Proofing Tools 2013", which installed correctly (they show up in my Installed Programs). Unfortunately, Word still won't recognise the Italian
    proofing tools, even though I've followed all of the previous instructions (keyboard layout enabled etc.). Can you kindly provide help? It worked perfectly under Windows 7. I'd like to clarify that I don't need the whole Language Pack, just the Proofing Tools.
    Thanks in advance.

  • I was updating iTunes to 10.5.2 and after it says it was succeccfully installed, when it tries to open iTunes, it says iTunes was not installed correctly.  Please reinstall iTunes.  Error 7 (Windows error 127).  I have windows Vista...

    I tried to update iTunes to version 10.5.2 and now I can't open it.  After it said it was successfully downloaded, it tried to open iTunes and it said iTunes was not installed correctly.  Please reinstall iTunes.  Error 7 (Windows error 127).  I unsitalled iTunes and tried again, and nothing works.  Help.

    Doublechecking first:
    I unsitalled iTunes and tried again, and nothing works
    Where you using the following document as a guide for that? (The 7 can be produced by damage to the related software components, so the Verify iTunes and related components are uninstalled step is quite important.)
    Removing and reinstalling iTunes, QuickTime, and other software components for Windows Vista or Windows 7

  • HT1923 The last update caused a problem that will not allow I tunes to open. It says MSVCR80.dll not installed. Then shows Error 7(Windows error 126). I have tryed to fix it but it will not fix problem.

    The last upgrade for I Tunes on my Windows 7 PC was almost done when it showed error. I atempted to redownload and then when trying to reopen I Tunes it shows that the MSVCR80.dlll is missing and then a second message that states Error 7 (Windows error 126). It has told me to reinstall I tunes, which I have done many times with no sucess. All previous versions have never been a problem.

    Hey Barry229!
    I have an article for you that will help you troubleshoot this issue:
    iTunes 11.1.4 for Windows: Unable to install or open
    http://support.apple.com/kb/TS5376
    Thanks for coming to the Apple Support Communities!
    Cheers,
    Braden

  • Networking on Ubuntu VM stopped functioning after latest VMWare tools upgrade

    when configuring the latest VMWare tools, I receive the following error:
    "The vmxnet driver is no longer supported on kernels 3.3 and greater. Please  upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)"
    I have followed instructions on a few different posts to try to fix this, and none have worked.
    I have tried running the vmware tools configuration script with --clobber-kernel-modules=vmxnet - that didn't help.
    I tried changing ethernet0.virtualDev = "vmxnet" to "vmxnet3" in the .vmx file - that didn't help either.
    Running Ubuntu 14.04 on VMWare Player 6.0.6 build-2700073 on Windows 7. The VM image in question is Ubuntu 14.04 on Linux kernel 1.13.0-43.
    This is for bridged mode (which I need) - running in NAT mode works fine.
    $ uname -a
    Linux ubuntu 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
    dust@ubuntu:~/Desktop/vmware-tools-distrib
    $ sudo ./vmware-install.pl --clobber-kernel-modules=vmxnet
    The previous installation was made by the tar installer (version 4).
    Keeping the tar4 installer database format.
    You have a version of VMware Tools installed.  Continuing this install will
    first uninstall the currently installed version.  Do you wish to continue?
    (yes/no) [yes]
    Uninstalling the tar installation of VMware Tools.
    Stopping services for vmware-tools
    vmware-tools stop/waiting
    Stopping services for vmware-tools-thinprint
    vmware-tools-thinprint stop/waiting
    File /etc/pulse/default.pa is backed up to /etc/pulse/default.pa.old.8.
    update-initramfs: Generating /boot/initrd.img-3.13.0-43-generic
    update-initramfs: Generating /boot/initrd.img-3.13.0-39-generic
    The removal of VMware Tools 9.6.5 build-2700074 for Linux completed
    successfully.
    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]
    What is the directory that contains the init scripts?
    [/etc/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.6.5 build-2700074 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.
    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 "/usr/bin/gcc".
    The path "/usr/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.13.0-43-generic/build/include".
    The path "/lib/modules/3.13.0-43-generic/build/include" appears to be a valid
    path to the 3.13.0-43-generic kernel headers.
    Would you like to change it? [no]
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/modconfig-OyHNrF/vmhgfs-only'
    /usr/bin/make -C /lib/modules/3.13.0-43-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-headers-3.13.0-43-generic'
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/backdoor.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/backdoorGcc64.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/bdhandler.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/cpName.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/cpNameLinux.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/cpNameLite.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/dentry.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/dir.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/file.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/filesystem.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/fsutil.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/hgfsBd.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/hgfsEscape.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/hgfsUtil.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/inode.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/link.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/message.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/module.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/page.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/request.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/rpcout.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/stubs.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/super.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/transport.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/vmci.o
      CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/kernelStubsLinux.o
      LD [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/vmhgfs.o
      Building modules, stage 2.
      MODPOST 1 modules
      CC      /tmp/modconfig-OyHNrF/vmhgfs-only/vmhgfs.mod.o
      LD [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/vmhgfs.ko
    make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-43-generic'
    /usr/bin/make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
    make[1]: Entering directory `/tmp/modconfig-OyHNrF/vmhgfs-only'
    make[1]: `postbuild' is up to date.
    make[1]: Leaving directory `/tmp/modconfig-OyHNrF/vmhgfs-only'
    cp -f vmhgfs.ko ./../vmhgfs.o
    make: Leaving directory `/tmp/modconfig-OyHNrF/vmhgfs-only'
    The vmxnet driver is no longer supported on kernels 3.3 and greater. Please
    upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)
    The vmblock enables dragging or copying files between host and guest in a
    Fusion or Workstation virtual environment.  Do you wish to enable this feature?
    [yes]
    VMware automatic kernel modules enables automatic building and installation of
    VMware kernel modules at boot that are not already present. This feature can be
    enabled/disabled by re-running vmware-config-tools.pl.
    Would you like to enable VMware automatic kernel modules?
    [yes]
    Thinprint provides driver-free printing. Do you wish to enable this feature?
    [yes]
    Disabling timer-based audio scheduling in pulseaudio.
    Detected X server version 1.15.1
    Distribution provided drivers for Xorg X server are used.
    Skipping X configuration because X drivers are not included.
    Creating a new initrd boot image for the kernel.
    update-initramfs: Generating /boot/initrd.img-3.13.0-43-generic
    vmware-tools-thinprint start/running
    vmware-tools start/running
    The configuration of VMware Tools 9.6.5 build-2700074 for Linux for this
    running kernel completed successfully.
    You must restart your X session before any mouse or graphics changes take
    effect.
    You can now run VMware Tools by invoking "/usr/bin/vmware-toolbox-cmd" from the
    command line.
    To enable advanced X features (e.g., guest resolution fit, drag and drop, and
    file and text copy/paste), you will need to do one (or more) of the following:
    1. Manually start /usr/bin/vmware-user
    2. Log out and log back into your desktop session; and,
    3. Restart your X session.
    Enjoy,
    --the VMware team
    $ ~

    one of the links i tried (as mentioned above):  Notes of a Programmer: VMWare Tools Failed to Load on Ubuntu 13.10 (Saucy)   - it did not help.

  • CUCM 9.1.2.12901-3 VMWare Tools Upgrade Never Ends

    Hi,
    I recently upgraded to 9.1.2.12901-3 and after, when I attempted to upgrade VMware Tools, the VMware Tools upgrade never ended and fails.
    Is there some documentation on this out there somewhere?
    Thanks,
    Joey

    Hi Joey.
    You are probably falling into this bug CSCus40939 
    The only workaround suggested is to reboot the VM or upgrade CUCM to a later release.
    HTH
    Regards
    Carlo

  • I get "itunes not installed correctly error 7 windows error 193?

    tried to open itunes today and got "itunes not installed correctly reinstall error 7 windows 193" ?  I did nothing to my system just wanted to open itunes.  I had no problem other times before. If I reinstall will I lose my songs.  I can still get  their listing but no play them

    Try the following user tip:
    Troubleshooting issues with iTunes for Windows updates

  • Itunes 8 - won't run - a required i Tunes component is not installed

    I upgraded to iTunes 8 last night and following the install when trying to open open i receive the following error.
    *"The itunes application could not be opened. a required iTunes component is not installed. Please repair or reenstall Quicktime (-42404)"*
    I have re-installed both applications, uninstalled and re-installed, attempted to repair quick time still not working.
    quicktime works ok, click on the icon and it oipens up and plays fine.
    Please help. I just purchase my iphone yesterday also, an i am unable to activate it as i can't get i tunes to work.
    thanks in advance

    To begin with, i tunes just quit working one day. it wouldn't open anything read any cds and ever time i tired to open it, it just popped up and error that it needed to be debugged or such. I had someone come look at it and they kinda sorta fixed it. i can now open it and listen to music. but i have to convert everything myself and add all my album work and it still wont rip cds or connect to my ipods. it says i need to have a 7.6 version or later. i went to download the new 8.0 verison and when it got to the end of installtion a box popped up that acess was denied and that it encoutered a error i always went and tired to reinstall quicktime and i tunes and deleting everything from it, and then when i tired to reinstall everything it still wouldn't install, its begginning to become very annoying and no one else knnows what to do.and i really need someones help... pLZ!!!!!!!!!!

  • JVM not Installed.

    Hi guys,
                        I have installed sap BO 4.0 64 bit SP6 server on my machine.Everything is fine, but when i try to open Webi it is showing JVM not installed. We have already installed JVM in the machine and we have given path also.
    Error:Cannot Launch Java Report Panel, please make sure you have installed a java virtual machine.
    Thanks&regards,
    Krishna

    I am facing same issue I am using BO 4.1sp1 64bit windows 2008  server
    when I go http://BOhostname:port/BOE/BI
    When I click Web intelligence icon
    I will run webi report and also edit it what JAVA version need to install in client Machine and also 32bit or 64bit because BOBJ server is 64bit but BOBJ client is 32bit .
    Regards

  • ITunes won't run because a required component is not installed

    I think a Quicktime upgrade went wrong and now I can no longer open my iTunes and this message appears:
    "The itunes application could not be opened. a required iTunes component is not installed. Please repair or reenstall Quicktime (-42404)"
    I have tried uninstalling and reinstalling Quicktime but it still does not work, and I don't want to risk losing my 50GB of music..
    Thanks in advance

    Download iTunes 11 from the Apple site and reinstall. The error message was quite plain in telling you what to do to resolve the error.

  • Itunes componenet not installed help

    ok ive had this same problem cant bring up my itunes at all but i get this message "the itunes application could not be opened. A required iTunes componentis not installed. Please repair or reinstall itunes. (-42404)"... ok so this is a diff message cos before i was getting the itunes.msi message now this and guess what i cant uninstall or reinstall crap... im thinking an i pod is just an expensive waste of time if I cant use the dam thing! Oh and i did try a reg cleaner i have several none worked! So what do I do now??

    Try the following method for removal and installer clean up.
    Download a fresh copy of iTunes and the stand alone version of Quicktime (the one without iTunes)
    http://www.apple.com/quicktime/download/win.html
    http://www.apple.com/itunes/download/
    Download and install Microsoft Installer cleanup utility, there are instructions on the page as well as the download. Note that what you download is the installer not the program – you have to run it to install the program.
    To run the program – All Programs>>Windows Install Cleanup
    http://support.microsoft.com/kb/290301/
    Now use the following method to remove iTunes and its components:
    XP
    http://support.apple.com/kb/HT1925
    Vista
    http://support.apple.com/kb/HT1923
    *If you hit a problem with one of the uninstalls don't worry*, carry on with the deleting of files and folders as directed in the method.
    When you get to deleting Quicktime files in the system32 folder as advised in the method, you can delete any file or folder with Quicktime in the name.
    Restart your PC.
    Run the Microsoft Installer Cleanup Utility. (Start > All Programs > Windows Install Clean Up)
    Remove any references you find to the programs you removed - strictly speaking you only need to worry about those programs where the uninstall failed.
    If you don’t see an entry for one of the programs that did not uninstall, look out for blank entries or numeric entries that look like version numbers e.g. 7.x for Quicktime or 1.x for Bonjour.
    restart your PC
    Install the stand alone Quicktime and check that it works.
    If it does, install iTunes.

  • [SOLVED] How to really install Open VMware Tools?

    I tried the steps shown in the wiki, but it's not working at all. I have Arch+KDE installed in VMware Player 5. The steps I followed for the installation of VMware tools are:
    pacman -S open-vm-tools open-vm-tools-modules
    systemctl enable vmtoolsd.service
    But after a reboot the Tools doesn't seem to work properly, even If I try to restart with the tools enabled the systems hangs on the process.
    Some help will be really appreciated.
    Cheers.
    Last edited by AurosGamma (2012-12-02 05:09:42)

    There are some known issues regarding the current versions of the open VMWare tools, check this topic.
    The steps you took provide minimal functionality, at least keeping the clock in sync with the host and handling screen resizing. For copy and paste and shared folders, the wiki has some additional info.
    The system seems to hang on reboot, but proceeds normally after about 90 seconds (it's how long systemd waits before forcefully killing the vmtoolsd daemon).
    Some tips to work around current issues:
    - don't use the latest version of xorg-server (use xorg-server 1.13.0-3 instead)
    - issue a 'killall -9 vmtoolsd; systemctl poweroff' to power off the system

  • Vmware-tools does not install in 2.6.22 dont panic arch guest os

    Dear All,
    I get the following error while compiling the vmware tools in guest arch linux 2.6.22-ck dont panic (vmware workstation 5.5.3). Though the output shows the vmhgfs module is able to load but I do not get my shared folder directory in the /mnt/hgfs. What is the work around.
    Stopping VMware Tools services in the virtual machine:
    Guest operating system daemon: done
    Guest filesystem driver: done
    Trying to find a suitable vmhgfs module for your running kernel.
    None of the pre-built vmhgfs modules for VMware Tools is suitable for your
    running kernel. Do you want this program to try to build the vmhgfs 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.22-ck/build/include]
    Extracting the sources of the vmhgfs module.
    Building the vmhgfs module.
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-config0/vmhgfs-only'
    make -C /lib/modules/2.6.22-ck/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
    make[1]: Entering directory `/usr/src/linux-2.6.22-ck'
    CC [M] /tmp/vmware-config0/vmhgfs-only/cpName.o
    CC [M] /tmp/vmware-config0/vmhgfs-only/cpNameLinux.o
    CC [M] /tmp/vmware-config0/vmhgfs-only/dev.o
    CC [M] /tmp/vmware-config0/vmhgfs-only/driver.o
    CC [M] /tmp/vmware-config0/vmhgfs-only/hgfsUtil.o
    CC [M] /tmp/vmware-config0/vmhgfs-only/main.o
    CC [M] /tmp/vmware-config0/vmhgfs-only/staticEscape.o
    LD [M] /tmp/vmware-config0/vmhgfs-only/vmhgfs.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/vmware-config0/vmhgfs-only/vmhgfs.mod.o
    LD [M] /tmp/vmware-config0/vmhgfs-only/vmhgfs.ko
    make[1]: Leaving directory `/usr/src/linux-2.6.22-ck'
    cp -f vmhgfs.ko ./../vmhgfs.o
    make: Leaving directory `/tmp/vmware-config0/vmhgfs-only'
    The module loads perfectly in the running kernel.
    pcnet32 29828 0
    Unloading pcnet32 module
    Extracting the sources of the vmxnet module.
    Building the vmxnet module.
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-config0/vmxnet-only'
    make -C /lib/modules/2.6.22-ck/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
    make[1]: Entering directory `/usr/src/linux-2.6.22-ck'
    CC [M] /tmp/vmware-config0/vmxnet-only/vmxnet.o
    /tmp/vmware-config0/vmxnet-only/vmxnet.c: In function 'vmxnet_open':
    /tmp/vmware-config0/vmxnet-only/vmxnet.c:674: warning: 'deprecated_irq_flag' is deprecated (declared at include/linux/interrupt.h:66)
    /tmp/vmware-config0/vmxnet-only/vmxnet.c: In function 'vmxnet_netpoll':
    /tmp/vmware-config0/vmxnet-only/vmxnet.c:1058: error: too many arguments to function 'vmxnet_interrupt'
    make[2]: *** [/tmp/vmware-config0/vmxnet-only/vmxnet.o] Error 1
    make[1]: *** [_module_/tmp/vmware-config0/vmxnet-only] Error 2
    make[1]: Leaving directory `/usr/src/linux-2.6.22-ck'
    make: *** [vmxnet.ko] Error 2
    make: Leaving directory `/tmp/vmware-config0/vmxnet-only'
    Unable to build the vmxnet module.
    The fast network device driver (vmxnet module) is used only for our fast
    networking interface. The rest of the software provided by VMware Tools is
    designed to work independently of this feature.
    If you wish to have the fast network driver enabled, 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 ]
    Thanks in advance.
    saa_1973.

    You shouldn't need the kernel sources, just point vmware tools to the right location :
    What is the location of the directory of C header files that match your running
    kernel? [/lib/modules/2.6.22-ck/build/include]
    Replace with usr/src/linux-2.6.22-ck/include/
    If you still get this error /tmp/vmware-config0/vmxnet-only/vmxnet.c:1058: error: too many arguments to function 'vmxnet_interrupt'
    see vmware tools 5.5.3, linux 2.6.19, vmxnet compile fix
    as mentioned at the bottom of the wiki page.

Maybe you are looking for