Unable to install vmware tool

Hi,
How do i install vmware tools? I am new to linux. Reading through various other posts, when i try to install headers i get an error message no package available.
[root@localhost /]#
urname -r = kernel-2.6.32-100.26.2.el5
yum install kernel-headers
Loaded Plugins: rhnplugin, security
This system is not registered with ULN
ULN support will be disabled
Setting up Install Process
No package kernel-headers available
Nothing to do
[root@localhost /]#
what am i missing?

You are using the Oracle UEK kernel. Try yum install kernel-uek-devel kernel-uek-headers. For this of course you will need to have ULN access or public yum configured according to http://public-yum.oracle.com

Similar Messages

How to install vmware tools in cucm on Vmware Player

I'm running CUCM 8.0.1 and Unity Connection 8.0.1 on VMWare Player. I need to install the VMWare Tools. I'm using the COP file from the CCO (ciscocm.vmtoolsUpgrade4.1-8.3.2-257589-v14.cop.sgn). However, it's not loading. I Clicked Install VMWare Tools from Player so the CDRom is mounted and has the COP file in it, but I can't seem to get the path. The connection is use physical device /dev/cdrom and I have a burned COP file in the dvd drive. I keep getting "The directory could not be located."
I have NTP enabled and "the NTP Service is accessible"
I tried the Remote File System but keep getting the error: "An unknown error occurred while accessing the upgrade file." I tried different files, e.g. locale file, but get the same error. Is there something else I need to do on the VM? The Host machine is Ubuntu 12.04 32 bit.
Is there a document on this? VMWare Player is ver 6.0. The VMs were built in VMWare server 2.0 a while back.

Thanks for the link. It is for vSphere and I'm using Player so Step 2 is a little different. I choose Virtual Machine>Upgrade VMWare Tools. The settings are set to "use ISO file" and the path is to the linux.iso file.
When I run the 'utils vmtools upgrade' command, it says: "Executed command unsuccessfully, no valid command entered"
Any other procedures to try?

How to install VMWare Tools on OEL 5.7

Hi,
I am not able to install VMWare tools on OEL 5.7
Oracle Linux Release 5 Update 7 on 32 bit env.
How shoould we proceed?
thanks!
Srinivas

Hi ,
Dd you fix it .... I am facing the same issue with OEL 5.7 and I did install headers and devel for 2.6.32-200.13.1 but the issue still exists
[root@rac1 bin]# rpm -qa|grep kernel
kernel-uek-firmware-2.6.32-200.13.1.el5uek
kernel-uek-2.6.32-200.13.1.el5uek
kernel-uek-headers-2.6.32-200.13.1.el5uek
kernel-2.6.18-274.el5
kernel-uek-devel-2.6.32-200.13.1.el5uek
[root@rac1 bin]# uname -r
2.6.32-200.13.1.el5uek
hitting the error
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: [ OK ]
None of the pre-built vmmemctl modules for VMware Tools is suitable for your
running kernel. Do you want this program to try to build the vmmemctl module
for your system (you need to have a C compiler installed on your system)?
[no]
The memory manager driver (vmmemctl module) is used by VMware host software to
efficiently reclaim memory from a virtual machine.
If the driver is not available, VMware host software may instead need to swap
guest memory to disk, which may reduce performance.
The rest of the software provided by VMware Tools is designed to work
independently of this feature.
If you want the memory management 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 ]
Please help me ....

Is it ok to install VMware Tools onto vWLC appliances?

I have two vWLC appliances which I've noticed don't have vmware tools installed by default. Is there a reason for this or am I ok to install it? I'd also like to keep all my VM's on vmx9 but am not sure how this will affect the appliance.
Is there any guidance on this anywhere from Cisco?

From Cisco's perspective our vWLC is just like any other VM running on hypervisor. So installing VMWare tools is no issue. You can install.
There is no guidance from cisco on install vmware tools and you should check with VMWare support.
-Thanks
Vinod
**Rating Encourages contributors, and its really free. **

Unable to install Phone Tools Update Pack

Hi,
I own Lumia 930 with Denim and I tried to install Phone Tools Update Pack so I would be able to monitor my device but unfortunately I cannot. When I am trying to install I am receiving error 0x80070057 - Unable to scan for packages from the update server. In
another topic there were hint to check date and time, I checked mine it's ok, on default I have set for automatically but I even tried with manual settings - no solution. I am using Visual Studio 2013 with SP 4 Community Edition. I tried do this on both my
PC and Laptop (windows 8.1 x64). I can without problem deploy application on device. I would be very grateful for any help.

Hi DeadStarlin,
Are both the computer and the phone connected to the Internet? On your computer, make sure that your web browser does not have
Work offline enabled. Also, you cannot connect through a proxy server that redirects to a login page; for example, in a hotel or an airport.
Is the phone turned on and the screen unlocked?
Is your Microsoft account information correct and valid?
If the above information still can not help, please try to restart your phone and computer to see if it works.
Best Regards,
Amy Peng
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Unable to install Management Tools

I am unable to install the Exchange Management Tools on my workstation. When I attempt to install, I get D:\exchangeserver.msi failed. This action is only valid for products that are currently installed. Error code is 1605.
None of the exchange components are installed. At one time, I had attempted to install it and although the install actually failed, it looked as if it had installed. The console would appear but never connect to the organization. My other workstation works
just fine, same login etc.. I couldn't even uninstall the Management tools either from the Programs applet in the control panel. I have essentially performed a manual uninstall by going through the registry and removing the installation directory on this computer.
Apparently I am missing something in the registry to finish out the uninstallation of the management tools, so I can attempt to install again. Has anyone else had this problem?
Thanks,
Kevin

Hi,
>When I attempt to install, I get D:\exchangeserver.msi failed. This action is only valid for products that are currently installed. Error code is 1605.
About error 1605, you can get more useful and try this way from the article:
http://support.microsoft.com/kb/168309/en-us
Hope it helps.
Thanks
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Installing VMware Tools on the ACS 5.2 VM Appliance

A cursory glance doesn't reveal any instructions on how to do this, does anyone know of documentation out there on how to insall VMware tools on the VM?

Hi Chris,
Unfortunately wmware tools cannot be install on ACS 5.x. Developers are already aware of the situation and there is an enhancement feature request.
CSCtg50048 Add support for VMWare Tools to ACS 5
Symptom:
VMWare Tools support is not present on ACS 5.
Conditions:
This affects ACS 5.
Workaround:
None.
No ETA for the enhancement. The next ACS version will be ready in summer this year, please look for it around that time.
Rgds, Jatin
Do rate helpful posts-

Unable to install Client Tools for Sybase ASE 15.7 on Windows Server 2012 64-Bit

Hello Folks,
I just downloaded the client tools package from https://support.sap.com/swdc --> Installation and Upgrades --> A-Z list --> SAP ADAPTIVE SERVER ENTERPRISE --> SYBASE ASE 15.7 --> Installation --> Microsoft Windows --> 51044415.zip
I'm trying to install the client tools for a newly provisioned Windows 2012 64-Bit machine. After unzipping the folder and running autorun, the installation does not proceed. When I go to pcclient64 and run either setup.exe or setupConsole.exe, I get the error "This Application has Unexpectedly Quit, Invocation of this Java Application has caused an InvocationTargetException. This application will now exit. (LAX)". I stumbled across various posts on the forum, and it appears that the installer is not certified for Windows Server 2012. I tried using the compatibility mode for Windows 7, and it proceeds further and launches the SAP GUI; however, it closes afterwards.
Any suggestions would be greatly appreciated. Thanks in advance.

Hi,
51044415 is a PC-Client 15.7 refresh.
You are using a version that was not certified with Windows 2012. Get the most current version PC-Client 15.7 SP130 or SDK 15.7 SP130 or SP132.
If your looking for PC-Client5.7 SP130 look for EBF23439
We didn't get certified with Windows 2012 until SDK 15.7 ESD#6 even with that I reported a few minor issues.
You need the following on the machine before the installation.
Microsoft Visual C++ 2010 Redistributable Package (x64)
Microsoft Visual C++ 2005 Redistributable Package (x86) (or dsedit and ocscfg will not work)
Microsoft Visual C++ 2005 Redistributable Package (x64) (or dsedit and ocscfg will not work)
Thanks,
Dawn Kim

Unable to instal Diagnostic - Tools : HP (UEFI) Support Environment

I've bought Hp probook 4540s recently and formatted H.D.D throughout and made four partitions one primary and three others logical but after os (win7 64bit) installation,I tried to install HP (UEFI) Support Environment (located at :http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=5229457&... diagnostic ) and faced the following message:
Main drive already have four partition additional partition cannot be created
There is a problem with this windows installer package
A program run as part of the setup did not finish as expected contact your support …
Now I'm baffled as to what happend and don't know what it means and how to solve this issue.

I regret buying hp probook 4540s laptop, it's the worst I've ever had.

Vmware tools intallation -- linux 4 update 5 was not happening

Hi ,
I want to install Vmware tools for my machine. I installed VMware and Linux 4 update 5 but was unable to install vmware tools once i installed linux. I couldnt find vmware tools rpm. I just find vmwaretools-8.1.4-227600.tar.gz file. I was not able to move my cursor freely. everytime i need to use keystrokes like alt+control to come out. Can anyone help me how to install vmware tools.

Please, avoid duplicated thread :
Linux 4 Update 5 vmware tools
Nicolas.

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)

Vmware-tools install

Has anyone successfully installed vmware-tools on arch? im curious if just symlinking /etc/rc.{multi,single} to /etc/rc.0-6 is sufficient to get passed that question in the script?
ah ok,
ln -s rc.d/ rc6.d
ln -s rc.d/ rc5.d
ln -s rc.d/ rc4.d
ln -s rc.d/ rc3.d
ln -s rc.d/ rc2.d
ln -s rc.d/ rc1.d
ln -s rc.d/ rc0.d
next problem i run into is it fails to stop vmware tools services which has never been run in the first place : any ideas?
more info this is vmware workstation 5.5.1 build-19175, arch 7.1 xorg7 kde3.5 ive checked other postings here nothing related to what im seeing when trying to run vmware-config-tools
root@myhost dev]# vmware-config-tools.pl
sh: /etc/vmware-tools: is a directory
Making sure services for VMware Tools are stopped.
Unable to stop services for VMware Tools
Execution aborted.

check out the packagebuild in AUR
It sets up those folders and other stuff for vmware workstation 5.5 and may help you.
If Archlinux is running as a vmware guest system, did you install X ?

VMWare Tools Fails to Install - Guest OS Windows 8.1 - vSphere 6.0

Hi,
I am having issues installing VMWare tools on a Windows 8.1 guest. I recently upgraded from ESXi 5.5 to 6 and used the automated upgrade. I logged on to one of my Windows 8.1 VMs and noticed that a glibc error was popping up related to VM Tools so I uninstalled and attempted a reinstall. VMWare tools now does not install.. I believe this is the relevant section of the logs before it rolls back:
2015-03-25 16:58:57| tools-build-2476743| --- VMInstallVideoDriver() : Installing video driver
2015-03-25 16:58:57| tools-build-2476743| Getting Property CustomActionData = C:\Program Files\Common Files\VMware\Drivers\video_wddm\vm3d.inf;5
2015-03-25 16:58:57| inst-build-2476743| I1: DInfo_GetDriverInfoFromInf: Got provider for inf: VMware, Inc.
2015-03-25 16:58:57| inst-build-2476743| I1: DInfo_GetDriverInfoFromInf: verified inf C:\Program Files\Common Files\VMware\Drivers\video_wddm\vm3d.inf signed by Microsoft
2015-03-25 16:58:57| inst-build-2476743| I1: DInfo_GetDriverInfoFromInf: Got provider for inf: VMware, Inc.
2015-03-25 16:58:57| inst-build-2476743| I1: DInfo_GetDriverInfoFromInf: Path is not absolute for oem7.inf, skipping signature check
2015-03-25 16:58:57| tools-build-2476743| VerifyDriverStillPresent: Checking driver store inf C:\Windows\System32\DriverStore\FileRepository\vm3d.inf_amd64_1cd9fc438ae97176\vm3d.inf
2015-03-25 16:58:57| inst-build-2476743| I1: DInfo_GetDriverInfoFromInf: Got provider for inf: VMware, Inc.
2015-03-25 16:58:57| inst-build-2476743| I1: DInfo_GetDriverInfoFromInf: verified inf C:\Windows\System32\DriverStore\FileRepository\vm3d.inf_amd64_1cd9fc438ae97176\vm3d.inf signed by Microsoft
2015-03-25 16:58:57| tools-build-2476743| VerifyDriverStillPresent: found match in both locations
2015-03-25 16:58:57| tools-build-2476743| Cannot query key value HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\Wnd: 2
2015-03-25 16:58:57| inst-build-2476743| I1: GetDriverForDeviceCallback: device PCI\VEN_15AD&DEV_0405&SUBSYS_040515AD&REV_00\3&18D45AA6&0&78 has inf oem7.inf
2015-03-25 16:58:57| inst-build-2476743| I1: GetDriverForDeviceCallback: Processing driver list entity #1
2015-03-25 16:58:57| inst-build-2476743| I1: GetDriverForDeviceCallback: Collecting information about driving using inf oem7.inf
2015-03-25 16:58:57| inst-build-2476743| I1: GetDriverForDeviceCallback: Recording provider VMware, Inc. date 00000000e9ffbb8c and ver 8.14.1.6
2015-03-25 16:58:57| inst-build-2476743| I1: GetDriverForDeviceCallback: original inf is "vm3d.inf" with cat "vm3d.cat"
2015-03-25 16:58:57| inst-build-2476743| I1: GetDriverForDeviceCallback: driver oem7.inf install rank 0x00f60000 params 0x00042044
2015-03-25 16:58:57| inst-build-2476743| I1: GetDriverForDeviceCallback: -- OS says driver is signed
2015-03-25 16:58:57| inst-build-2476743| I1: GetDriverForDeviceCallback: -- OS says driver is WHQL signed
2015-03-25 16:58:57| inst-build-2476743| I1: GetDriverForDeviceCallback: -- driver is installed
2015-03-25 16:58:57| tools-build-2476743| AllDevicesUsingSameDriver: Device PCI\VEN_15AD&DEV_0405&SUBSYS_040515AD&REV_00\3&18D45AA6&0&78 is using the correct inf oem7.inf
2015-03-25 16:58:57| tools-build-2476743| AllDevicesUsingSameDriver: Found: oem7.inf from VMware, Inc., version 8.14.1.6 used by 1 devices
2015-03-25 16:58:57| tools-build-2476743| AllDevicesUsingSameDriver: Detected that the one driver in use matches
2015-03-25 16:58:57| tools-build-2476743| Determined that svga_wddm has not changed
2015-03-25 16:58:57| tools-build-2476743| existing svga_wddm info:
2015-03-25 16:58:57| tools-build-2476743| Driver version 8.14.1.6 is WHQL (ca ver 1) inf "oem7.inf"
2015-03-25 16:58:57| tools-build-2476743| current svga_wddm info:
2015-03-25 16:58:57| tools-build-2476743| Driver version 8.14.1.6 is WHQL (ca ver 1) inf ""
2015-03-25 16:58:57| tools-build-2476743| End Logging
2015-03-25 16:58:57| tools-build-2476743| Begin Logging
2015-03-25 16:58:57| tools-build-2476743| --- VMMofCompile()
2015-03-25 16:58:57| tools-build-2476743| Getting Property CustomActionData = C:\Windows\system32\wbem\vmstatsprovider.mof;1
2015-03-25 16:58:57| tools-build-2476743| Found "C:\Windows\system32\wbem\vmstatsprovider.mof"
2015-03-25 16:58:58| tools-build-2476743| Successfully compiled 'C:\Windows\system32\wbem\vmstatsprovider.mof'
2015-03-25 16:58:58| tools-build-2476743| End Logging
2015-03-25 16:58:58| tools-build-2476743| Begin Logging
2015-03-25 16:58:58| tools-build-2476743| Resetting the Icon Cache
2015-03-25 16:58:58| tools-build-2476743| End Logging
2015-03-25 16:58:58| tools-build-2476743| Begin Logging
2015-03-25 16:58:58| tools-build-2476743| --- VMRun()
2015-03-25 16:58:58| tools-build-2476743| Getting Property VM_Run =
2015-03-25 16:58:58| tools-build-2476743| Getting Property CustomActionData = cscript.exe;"C:\Program Files\VMware\VMware Tools\guestproxy-cert-management.vbs" -g;0;0
2015-03-25 16:58:58| tools-build-2476743| Found "cscript.exe"
2015-03-25 16:58:58| tools-build-2476743| Attempting to launch ""cscript.exe" "C:\Program Files\VMware\VMware Tools\guestproxy-cert-management.vbs" -g"
2015-03-25 16:58:58| tools-build-2476743| Create Process failed: error 216
2015-03-25 16:58:58| tools-build-2476743| ERROR: Failed to run 'cscript.exe "C:\Program Files\VMware\VMware Tools\guestproxy-cert-management.vbs" -g'.
2015-03-25 16:58:58| tools-build-2476743| End Logging
2015-03-25 16:58:59| tools-build-2476743| Begin Logging
2015-03-25 16:58:59| tools-build-2476743| --- VMUninstallAudioDriver() : Uninstalling audio driver
2015-03-25 16:58:59| tools-build-2476743| Cannot query key value HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\Wnd: 2
2015-03-25 16:58:59| tools-build-2476743| Migrating device ID PCI\VEN_1274&DEV_1371&SUBSYS_13711274 to the best driver
2015-03-25 16:58:59| tools-build-2476743| End Logging
2015-03-25 16:58:59| instUtils-build-2476743| Begin Logging
2015-03-25 16:58:59| instUtils-build-2476743| VMUninstallKernelDriver running
Can anyone shed some light on this? I think it has something to do with cscript.exe, when I attempt to run it from a command prompt I get an error that the program or feature cannot start or run due to incompatibility with 64-bit version of windows. cscript located in syswow64 works, is there any way I can force it to use that?
Thanks!

OK, got a bit further... forced it to use the cscript.exe executable that actually works but now receiving this error:
2015-03-25 17:44:07| tools-build-2476743| Getting Property VM_Run =
2015-03-25 17:44:07| tools-build-2476743| Getting Property CustomActionData = cscript.exe;"C:\Program Files\VMware\VMware Tools\guestproxy-cert-management.vbs" -g;0;0
2015-03-25 17:44:07| tools-build-2476743| Found "cscript.exe"
2015-03-25 17:44:07| tools-build-2476743| Attempting to launch ""cscript.exe" "C:\Program Files\VMware\VMware Tools\guestproxy-cert-management.vbs" -g"
2015-03-25 17:44:14| tools-build-2476743| Child exited with code 1
2015-03-25 17:44:14| tools-build-2476743| Process returned 1
2015-03-25 17:44:14| tools-build-2476743| ERROR: An error occurred while running 'cscript.exe "C:\Program Files\VMware\VMware Tools\guestproxy-cert-management.vbs" -g'.
2015-03-25 17:44:14| tools-build-2476743| End Logging
2015-03-25 17:44:14| tools-build-2476743| Begin Logging

VMWare tools install for MeetingPlace 8.0.1 App Server

So, this may seem like a non-trivial task. Install VMWare tools in a Virtual environment? Couldn't be easier, unfortunately I have run into issues with installing VMWare tools in the MeetingPlace Application Server. This server runs RHEL 4 but when installed it is setup under Windows Server 2003. So, once powered on the server runs RHEL 4 but VM sees it as a Windows 2003 server and does not contain that tar.gz file in the VMWare Tools install folder.
This is starting to give me a headache as it should be a simple task but I cannot figure it out. Any help is greatly appreciated.
Running vCenter 4.1.
Cisco Unified MeetingPlace 8.0.1 Application Server.
-Runs with Red Hat Enterprise Linux 4.
-Virtual Client setup as Windows Server 2003, the only way that the OS would install.
- When VMWare Tools datastore is mounted the only files available are for Windows, not Linux.
Any ideas?
Nick

Aaron,
The install guide that I followed on the Cisco Support page (here) instructed me to do it that way, also that is the only way that I could get the OS to mount in the VM. As for the normal way of doing things, I am unsure, I've only been working with MeetingPlace for about a week and have installed it twice now with this being the only method that worked for me.
I tried navigating through the datastore but couldn't ever find the vmimages folder, may not have gone high enough. I then tried changing the Guest OS and was able to get it back up and running. Once it was running you were spot on, there it is.
Thank you for the help,
Nick

Vmware tools installed but not working.

I installed vmware 9.0.2 from pacman and also installed vmware-tools but when I fire up windows xp (for brittanica encyclopedia) in vmware it asks me to download & install vmware tools,
1. When i've already installed it with pacman ( it contained tools for freebsd, linux, windows etc. ), why is vmware wants to install it again ?
2. When vmware asks to download & install vmware-tools, it downloads but gives error that "A software conponent failed to installed..." basically it fails to install.
3. How to get vmware-tools working ?
How to solve this problem ?

Make sure you are in bridged mode, not host only.

Unable to install vmware tool

Similar Messages

Maybe you are looking for