Upgrade Vmware Tools always fails
I use VmWare WorksStation 10.0.6 build-2700073
Host Windows 8.1 on a Lenovo laptop with 16 GB Ram
Guest is Windows 7 with 4 GB Ram
When I try to upgrade VmWare Tools
I Try Download and install and got this
Any idea how to continue ?
AttracsHi Attracs,
Thank you for using Workstation.
Would you please answer the questions below?
So that we can investigate further.
1) What's the vmTools version number currently installed on your host?
You can follow the steps to see the version number:
1. Right click the VM -> Settings
2. Click CD/DVD tab, choose "Use ISO image file"
3. Then browse to the Workstation installation folder, choose "windows.iso". The tools installer is now mounted in guest.
4. Browse the contents in guest's CD/DVD driver.
5. Right click on the file "setup.exe"
6. Choose the Details tab, then you can see the Product version.
2) How did you install WorksStation 10.0.6 build-2700073?
Do you upgrade it from previous version, or just downloaded the installer from vmware.com and fresh installed it?
Thanks a lot!
Similar Messages
-
VMware tools installation fails
Hi,
I decided to try out Arch Linux in VMware Player before installing it on my system. The installation so far has gone well but I can't succeed in installing the VMware tools services. During installation I get several errors and warnings. These are the errors:
depmod: ERROR: Module 'hci_vhci' has devname (vhci) but lacks major and minor information. Igonring.
The above error seems not to be critical. But then I get another error when stopping Thinprint and VMware tools though all activities complete successfully:
sh: : command not found
sh: : command not found
Then I get the following errors at the end of the installation:
depmod: ERROR: Module 'hci_vhci' has devname (vhci) but lacks major and minor information. Igonring.
Warning: This script could not find mkinitrd or update-initramfs and cannot remake the initrd file!
depmod: ERROR: Module 'hci_vhci' has devname (vhci) but lacks major and minor information. Igonring.
VM communication interface socket family:[ 2530.549324] vmci: exports duplicate symbol vmci_context_get_priv_flags (owned by vmw_vmci)
Guest operating system daemon:
Unable to start services for VMware Tools
Execution aborted.
I have Linux kernel 3.13.5-1-ARCH (x64) on VMware Player 6.0.1 build-1379776 running atop Debian 7 with kernel 3.12.0.bpo.1-amd64. I have also the latest version of VMware tools.I uninstalled the VMware Tools that I had before. Then I installed wget and ran:
wget https://aur.archlinux.org/packages/vm/vmware-tools/vmware-tools.tar.gz
tar -xvzf vmware-tools.tar.gz
cd vmware-tools
makepkg -s --asroot
pacman -U vmware-tools.pkg.tar.xz
exit
umount /mnt
reboot
No errors were reported but unfortunately it doesn't work. If I run ifconfig, I can only see the loopback interface. VMware Player doesn't detect any version of VMware Tools installed.
Last edited by trifud (2014-03-02 18:50:05) -
Upgrade iphone 3g always failed
Hello,
I bought an iphone 3G ( firmware 2.0 ) in august. The first upgrade from 2.0.0 to 2.0.1 failed during installation ( error in Itunes and usb cable image on iphone) and I had to reinstall firmware than to restore my iphone settings and resync all music ( about 1 or 2 hours ). The same issue happens when doing the upgrade from 2.0.1 to 2.0.2. Now, I am afraid that each time I perform an upgrade it will fail.
I use Itune 7.7 and windows XP.
Anybody already noticed that ?
Do you think it is problem of the PC itself ?
thanks
ThomasBe sure you're connected directly to the PC, not a hub, and preferably a rear port (some PCs have issues with front USB ports). Since USB uses the CPU to manage data transfer, try to avoid heavy CPU activity when updating. All of my updates have been fine.
-
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,
JoeyHi 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 -
How To: Upgrade the VMware Tools in vCMA
I am by no means a linux expert but this method worked for me. I now have the latest version of VMware Tools from vSphere running in vCMA.
0. Snapshot the vCMA machine so you can undo if there are any problems!
1. Firstly download the latest linux.iso from your esx box to your desktop. Use WinSCP or other similar tool to download this from /vmimages/tools-isoimages
2. Extract the tar.gz file using an archive manager such as 7zip. The vSphere version is called VMwareTools-4.0.0-164009.tar.gz so this is what I will refer to from here on.
3. Upload VMwareTools-4.0.0-164009.tar.gz to the vCMA servers /tmp directory using WinSCP or downloading it from a webserver using wget http://server/VMwareTools-4.0.0-164009.tar.gz
4. On the vCMA server console install the The World-Wide Web library for Perl. yum install perl-libwww-perl
5. Extract the contents of the VMwareTools-4.0.0-164009.tar.gz file in the /tmp directory. tar zxf /tmp/VMwareTools-4.0.0-164009.tar.gz
6. Uninstall the previous version of VMware Tools using the uninstaller from the latest version. The uninstall script wasn't left from the initial install. /tmp/vmware-tools-distrib/bin/vmware-uninstall-tools.pl
7. Install the latest version accepting the defaults. /tmp/vmware-tools-distrib/vmware-install.pl
8. Reboot the vCMA server. shutdown -r now
9. If everything works correctly remove the snapshot.
That should be all there is to it.
Good luck!You could also replace steps 1 - 3 with the following alternates:
1. Shutdown the VCMA guest and add a "client" CD ROM to the VCMA appliance and power-on;
2a. Create a directory for mount point, "mkdir /mnt/cdrom"
2b. Select "VM->Guest->Install/Upgrade VMware Tools" from the console menu;
2c. Mount the VMware Tools CD, "mount -t iso9660 /dev/hda /mnt/cdrom"
3. Copy the VMwareTools to the /tmp directory, "cp /mnt/cdrom/VMwareTools-4*.gz /tmp"
Then proceed from your steps. Next Tools update you will only need to do steps 2b, 2c, 3, 5 and 7-9.
--Collin C. MacMillan
SOLORI - Solution Oriented, LLC
http://blog.solori.net
If you find this information useful, please award points for "correct" or "helpful". -
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? -
VMWare Tools install still blocked with 10.5(1)
I just upgraded CUCM and CUCX from 9.1 to 10.5(1) and ran into the issue described in CSCul78735 so it doesn't appear completely fixed. I wasn't able to upgrade VMWare Tools until setting SELinux to permissive mode.
Hi Gagarin,
I have recently upgraded 5 servers to 10.5.2.11900-3. With 2 servers I tried updating the VMware tools automatically through the vSphere client. The result was that the VMware tools were uninstalled from the VM. With the other 3 servers I selected the interactive install and used the 'utils vmtools refresh' command. Updating the tools on these 3 servers was successful. On the 2 servers that were not successful I am unable to use the 'utils vmtools refresh' command because I get a message stating "No VMware Tools install currently exists on the system...restart the system..." but after multiple reboots VMware tools still do not reinstall. I have set the 'utils os secure permissive" but that has not helped. The tools have now been uninstalled and I can not find a method to reinstall without TAC. TAC could probably install from root but instead has only emailed and recommended that I install a mystery COP file but they have not provided information on where I can locate a COP file for 10.5 and I believe that is because there is not a COP file available. If you would still like to troubleshoot this issue please let me know.
For others looking to upgrade the VMware tools I recommend the approach of using the 'utils vmtools refresh' command from the cli. -
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 -
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.
-
VMware Tools now broken with gcc 5.1.0 upgrade
This is more of a VMware Tools problem I believe as the community currently has to "patch" the vmware-tools-distro.pl script manually to get it to compile vmhgfs (which is used for file sharing between host and the Arch guest). I am starting a thread here to document any resolve, which currently there is none...
Around April 28th, the Arch linux kernel was compiled with gcc 5.1.0, even though gcc 4.9 was in the repository. This started the problems with vmware tools install:
https://bbs.archlinux.org/viewtopic.php?id=196915
I was able to resolve it by recompiling the kernel using the gcc 4.9 on the system. All attempts at upgrading gcc to 5.1.0 failed, because as I was able to build the tools using gcc 5.1.0, the VM was lockup when trying to enable the kernel modules for vmware. Both on script install, and during reboot.
Today I've upgraded my system and found gcc 5.1.0 upgraded.
I switched back to using the core kernel (compiled with gcc 5.1.0) and allowed gcc 5.1.0 to be installed. I rebooted and got a panic from the vmhgfs not being able to run, and was dumped to emergency mode. (Do note that I have vmhgfs in my fstab, this is most likely why it failed on boot)
So, I went into vmware-tools-distro, my patched version (see link above), and attempted to rebuild the vmware tools under the kernel compiled with gcc 5.1.0 and with gcc 5.1.0. Yay, it found gcc binary this time - the 5.1.0 version.
Unfortunately, the same previous 5.1.0 errors exists:
* during vmware-tools-install.pl, it won't compile vmhgfs with errors of functions not found. needs to be patched (vmware issue, ignore)
* during vmware-tools-install.pl again with patched script, it compiles just fine.
* but during the Kernel Modules enabling portion, the system hangs / freezes / halts. Hard reset is only resolve.
* on system boot, system hangs / freezes / halts on vmhgfs initialization.
Only current resolves are:
* Do not use file sharing (not an option)
* Install gcc 4.9 and recompile your kernel (I already have one, so i am using it)
This is obviously not a long term solution.I have switched to the Open VM Tools, the public domain versions, and am running into exactly the same "vmhgfs" problem: system panics/hangs/locks when trying to mount the share.
I posted a bug report over in VMware... But considering they haven't even fixed the build issues with VMware Tools in 7 months (dev says he has fixed it, but it's not released yet), I seriously doubt that gcc 5.1.0 will get any attention before the next year.
Guess I may be going back to VirtualBox after all. But the 3D acceleration sucks in that, as well as disk I/O. -
I have set up icloud tool and I try to log in but it always fail showing error "you can not sign in because of server error", what can I do?
Hello, Sameh.tolba.
Thank you for visiting Apple Support Communities.
I would recommend going through the troubleshooting steps in the two articles below when experiencing this issue.
Apple software on Windows: May see performance issues and blank iTunes Store
http://support.apple.com/kb/ts4123
iCloud: Making sure that iCloud works with security software in Windows
http://support.apple.com/kb/TS4175
Cheers,
Jason H. -
Vmware tools for fc10 fail to compile some modules
I'm running esxi 3.5 u3 - when I try to install vmware tools on fedora core 10 (linux kernel 2.6.27.5).
vmmemctl breaks:
os.c: 590 erro struct proc_dir_entry has no member named get_info
vmghfs breaks:
bdhandler.c:29:27: erro: asm/semaphore.h : no such file or directory
I have checked in the kernel include files, and effectively these errors are correct. When I lookad at earlier 2.6 kernels, for example 2.6.18, proc_dir_entry did have a memeber named get_info, but no longer.
Is there anything I can do? (although this is not that critical) .
Otherwise, vmware-tools compile ok.Priot to the current version of VMWare Tools I used to try and compile them and ran into issues.
Now I find that they are much better supported (on Ubuntu at least) and so in the VM I click on Install VMware Tools from the menu, mount the "CD" in a virtual CD Rom and install them the normal way ...
I would hope that something like this would work for FC - this is what I do in Ubuntu:
sudo apt-get install linux-headers-server build-essential
sudo mount /dev/scd0/media/cdrom0
or
mount /cdrom
VM > Install VMWare Tools
cp /cdrom/VmwareTools-x.x.x-xxxxx.tar.gz ~
cd ~
tar -zxf VmwareTools-x.x.x-xxxxx.tar.gz
cd vmware-tools-distrib
./vmware-install.p
I am not a FC user so I don't know how much this will help ... -
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) -
Workstation 11.1
Ubuntu 15.04 Guest OS
Kernel 3.19.0-15-generic
VMwareTools-9.9.2-2496486
When I try to install vmwaretools in my Ubuntu 15.04, I receive the following compilation errors (shared folder feature don't work):
Initializing...
Making sure services for VMware Tools are stopped.
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
VMware User Agent (vmware-user): done
Blocking file system: done
Unmounting HGFS shares: done
Guest filesystem driver: done
Stopping Thinprint services in the virtual machine:
Stopping Virtual Printing daemon: done
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
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.19.0-15-generic/build/include".
The path "/lib/modules/3.19.0-15-generic/build/include" appears to be a valid
path to the 3.19.0-15-generic kernel headers.
Would you like to change it? [no]
make: Entering directory '/tmp/modconfig-O5xscq/vmhgfs-only'
Using kernel build system.
/usr/bin/make -C /lib/modules/3.19.0-15-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-headers-3.19.0-15-generic'
CC [M] /tmp/modconfig-O5xscq/vmhgfs-only/backdoorGcc64.o
CC [M] /tmp/modconfig-O5xscq/vmhgfs-only/message.o
CC [M] /tmp/modconfig-O5xscq/vmhgfs-only/dir.o
CC [M] /tmp/modconfig-O5xscq/vmhgfs-only/rpcout.o
CC [M] /tmp/modconfig-O5xscq/vmhgfs-only/filesystem.o
CC [M] /tmp/modconfig-O5xscq/vmhgfs-only/cpName.o
CC [M] /tmp/modconfig-O5xscq/vmhgfs-only/request.o
CC [M] /tmp/modconfig-O5xscq/vmhgfs-only/module.o
/tmp/modconfig-O5xscq/vmhgfs-only/dir.c: In function ‘HgfsPackDirOpenRequest’:
/tmp/modconfig-O5xscq/vmhgfs-only/dir.c:417:26: error: ‘struct file’ has no member named ‘f_dentry’
file->f_dentry) < 0) {
^
/tmp/modconfig-O5xscq/vmhgfs-only/dir.c: In function ‘HgfsDirLlseek’:
/tmp/modconfig-O5xscq/vmhgfs-only/dir.c:707:32: error: ‘struct file’ has no member named ‘f_dentry’
struct dentry *dentry = file->f_dentry;
^
In file included from /tmp/modconfig-O5xscq/vmhgfs-only/dir.c:39:0:
/tmp/modconfig-O5xscq/vmhgfs-only/dir.c: In function ‘HgfsReaddirNextEntry’:
/tmp/modconfig-O5xscq/vmhgfs-only/dir.c:993:31: error: ‘struct file’ has no member named ‘f_dentry’
si = HGFS_SB_TO_COMMON(file->f_dentry->d_inode->i_sb);
^
/tmp/modconfig-O5xscq/vmhgfs-only/module.h:89:62: note: in definition of macro ‘HGFS_SB_TO_COMMON’
#define HGFS_SB_TO_COMMON(sb) ((HgfsSuperInfo *)(sb)->s_fs_info)
^
/tmp/modconfig-O5xscq/vmhgfs-only/dir.c:1082:26: error: ‘struct file’ has no member named ‘f_dentry’
*entryIno = file->f_dentry->d_inode->i_ino;
^
In file included from /tmp/modconfig-O5xscq/vmhgfs-only/dir.c:30:0:
/tmp/modconfig-O5xscq/vmhgfs-only/dir.c:1088:44: error: ‘struct file’ has no member named ‘f_dentry’
*entryIno = compat_parent_ino(file->f_dentry);
^
/tmp/modconfig-O5xscq/vmhgfs-only/./shared/compat_fs.h:120:46: note: in definition of macro ‘compat_parent_ino’
#define compat_parent_ino(dentry) parent_ino(dentry)
^
/tmp/modconfig-O5xscq/vmhgfs-only/dir.c:1093:52: error: ‘struct file’ has no member named ‘f_dentry’
*entryIno = HgfsGetFileInode(&entryAttrs, file->f_dentry->d_inode->i_sb);
^
/tmp/modconfig-O5xscq/vmhgfs-only/dir.c: In function ‘HgfsDoReaddir’:
/tmp/modconfig-O5xscq/vmhgfs-only/dir.c:1173:13: error: ‘struct file’ has no member named ‘f_dentry’
!(file->f_dentry) ||
^
/tmp/modconfig-O5xscq/vmhgfs-only/dir.c:1174:13: error: ‘struct file’ has no member named ‘f_dentry’
!(file->f_dentry->d_inode)) {
^
scripts/Makefile.build:257: recipe for target '/tmp/modconfig-O5xscq/vmhgfs-only/dir.o' failed
make[2]: *** [/tmp/modconfig-O5xscq/vmhgfs-only/dir.o] Error 1
make[2]: ** Esperando que outros processos terminem.
Makefile:1394: recipe for target '_module_/tmp/modconfig-O5xscq/vmhgfs-only' failed
make[1]: *** [_module_/tmp/modconfig-O5xscq/vmhgfs-only] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-3.19.0-15-generic'
Makefile:120: recipe for target 'vmhgfs.ko' failed
make: *** [vmhgfs.ko] Error 2
make: Leaving directory '/tmp/modconfig-O5xscq/vmhgfs-only'
The filesystem driver (vmhgfs module) is used only for the shared folder
feature. The rest of the software provided by VMware Tools is designed to work
independently of this feature.
If you wish to have the shared folders feature, you can install the driver by
running vmware-config-tools.pl again after making sure that gcc, binutils, make
and the kernel sources for your running kernel are installed on your machine.
These packages are available on your distribution's installation CD.
[ Press Enter key to continue ]
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?
[no]
Thinprint provides driver-free printing. Do you wish to enable this feature?
[yes]
Disabling timer-based audio scheduling in pulseaudio.
Do you want to enable Guest Authentication (vgauth)? [yes]
Detected X server version 1.17.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.19.0-15-generic
Checking acpi hot plug done
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
Blocking file system: done
VMware User Agent: done
Guest operating system daemon: done
Starting Virtual Printing daemon: done
The configuration of VMware Tools 9.9.2 build-2496486 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
I tried to use these instructions to solve the problem:
http://rglinuxtech.com/?p=1281
compiling - VMWare player and Ubuntu 15.04: net driver does not compile anymore, how to fix? - Ask Ubuntu
However, I don't have the /usr/lib/vmware/modules/source with vmnet.tar file.
I just have /usr/lib/vmware-tools/modules/source with the following files:
legacy vmblock.tar vmhgfs.tar vmsync.tar vmxnet.tar pvscsi.tar vmci.tar vmmemctl.tar vmxnet3.tar vsock.tar
How I resolve this problem?
Thank You!Now It's working for me! :-) Thanks kikitora for the correct answer and Rahul Jha for this tutorial:
Please ensure that latest Workstation 11 is installed.
Make sure open-vm-tools is not installed.
sudo apt-get remove open-vm-tools
1. Make sure the updates are done:
sudo apt-get update
2. Make sure git is installed
sudo apt-get install git
3. Run the command to get the tools from repository.
sudo git clone https://github.com/rasa/vmware-tools-patches.git
4. cd to vmware-tools-folder
cd vmware-tools-patches
5. Run the patch
sudo ./download-tools.sh
6. Run the following patch
sudo ./untar-and-patch.sh
7. Run the complie.sh file
sudo ./compile.sh -
Hi,
we are upgrading our CUCM 8.6.1 to 10.5.1 on VMWare Enviroment (vSphere 5.5 running on UCS).
We are running this upgrade in a sandbox, in order to avoid any problem in the production cluster.
We followed the refresh upgrade guide ( http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/10_0_1/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100.pdf)
Pre-configuration steps
Take a clone of the running publisher and put it in the sandbox
Remove DNS servers (they are not available in the sandbox)
Change the NTP Server with a ntp that is recheable from the sandbox
Check that Gateway and NTP connectivity are OK for the CUCM
Pre-upgrade:
Run the cop files to update keys and increase disk space (log partition is 80% full)
Shutdown the CUCM VM and
Increase disk space on the VM configuration
change VM OS from RedHat5 (32bit) to RedHat 6 (64bits)
change VM nic from flexible to VMNIX3
Restart the VM
Upgrade
1. mount the iso
2. connect to OS Administration web interface and perform the Software installation from CD/DVD
3. upgrade process works fine up to the post-installation task
During post-installation tasks (after completing the DB Load and Transforming Copy) the Upgrade process always fails fails with an internal error
IPM|Internal Error, File:ipm.c:2011, Function: ipmReadNormalizedInputLine(), "/usr/local/cm/script/cm-dbl-install RU PostInstall 10.5.1.10000-7 8.6.1.21019-1 /usr/local/cm/ /common/component/database /common/log/install/capture.txt " failed (1)|<LVL::Critical>
IPM| end-of-session "Installing database component": 1109.369 secs.|<LVL::Info>
IPM|Close progress meter "Component Install"|<LVL::Info>
We also tried the intermediate steps:
- upgrade from 8.6.1 to 9.1 : worked
- from 9.1 to 10.5: Failed with the same error
- from 9.1 to 10.1: Failed with the same error
any help will be greatly appreciated, thanks
StefanoIssue was related to Dial Plans, the logs showed
16:45:46.204 | DBUtil::BlockCopyTable ### *ERROR* ###: (diagnosis): Bulk Data Migration for table availdialplan failed due to data constraint issue, (-971).
16:45:46.611 | DBUtil::BlockCopyTable *
16:46:16.555 |*ERROR* Error fetching column information: [Informix][Informix ODBC Driver][Informix]Could not position within a table (informix.systables).
16:46:16.588 | DataConverter_5to6::CopyTables *ERROR* BlockCopyTable failed to process table (availdialplan)
16:47:52.395 | installFull *ERROR* Prior Cancel or Error Processing convert5to6()
Cisco TAC fixed by updating the primary key in the DB.
After the fix we were able to perform the RU as expected.
Maybe you are looking for
-
I have a lot of photos in my trash bin and was thinking about emptying the trash. However, I got a message that said that if emptied, I would not be able to recover them. I chickened out. I looked at several pictures in the trash and noticed that
-
Unable to open a .zip file (Winzip) from the KM Repository
Hi.... while i am trying to open a .zip file (i.e., Winzip file) placed in the KM Repository.. I am getting an error - "Cannot open file : it does not appear to be a valid archieve." Is it someting related to the Winzip version ? Can somebody plz tel
-
Hi Experts, I am trying to create an uassigned Hu thru BAPI_HU_CREATE by providing the Packaging Material No in the HEADERPROPOSAL-PACK_MAT field.Now post executing the BAPI 'm able to get the HU no but the entry is not reflected in VEKP and VEPO ta
-
My itunes update failed. My reinstall is not working saying "service apple mobile device failed to start. Verify you have sufficent priveledges to start system services. Any advice? Thanks.
-
Attachements hidden if send from work in process
Hi Froum, GW Server 2014.0.0 GW Client 8.0.3 (latest FTF) one customer often uses the "work in process" folder to save mails for later editing and sending. Many of them have an attachement. If any mail (with attachement) from that folder is edited an