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 ...

Similar Messages

  • VMware Tools for Windows 3.x

    Hello,
    I created a fork of VMware Tools for Windows 3.x 16-bit operating systems. Currently these tools include:
    time synchronization between ESXi host and VM
    CPU idle support
    FAT12 and FAT16 shrink support
    experimental 100 mbit/s network card support
    famous Intel 8086 turbo button emulation
    emulation of 5.25“ floppy drives and their sound for a better user-experience
    For the future 10 Gbit/s and InfiniBand support is planned.
    Check-out the source code on GitHub: stdevel/vmtools-w16 · GitHub
    Best regards!

    I know you must use 16-bit DLLs if LabVIEW is installed on Win 3.x. The LabVIEW CD for versions 4 and 5 contains NT/95/3.1 versions. Can't you just install the Win 95 version? If you're using an older version, maybe its time to upgrade.

  • Vmware Tools for Nexus 1000v, VNMC and VSG

    Hi everyone, a customer is asking me about how to install the vmware tools in the virtual machines of N1Kv, VSG and VNMC.
    Someone knows the procedure, or if thats posiible or not.

    @Robert
    Wanted to know / understand what hardware version would be compatible for Nexus 1000V ? Is there any dependency for hardware version ?
    Regards,
    Amit Vyas

  • Vmware tools for cisco acs 5.3

    to backup an ACS 5.3 vm running on ESXi 5.0 our backup admin requested to install vmware tools on the acs server.
    How to do this - if possible?

    Hi Joe
    yes the vmware HA works for us and is enough if you can live with risk of data corruption. (which we never experienced up to now...)
    In our case it's good enough to recover from the backup instead of adding more complexity.
    regards
    Frank

  • VMware tools for OEL 5 Update 3

    Dear All,
    Recently I tried installing VMware tools on OEL 5 with Update 3 Linux Virtual Machine. The GNOME X Desktop which was working fine before the install stopped working after I installed VMware Tools.
    Why am I looking to Install VMware tools.
    I have two issues with OEL 5.3 Virtual Machines.
    #1. The Desktop is very small. I have difficulty in finding and navigating to the Next Button in OUI (runInstaller).
    #2. Mouse gets stuck while moving causing pain in the hand.
    Note: The above two issues are not appearing in Red Hat Virtual Machines I have on the same box.
    I'm not sure if OEL 5.3 is supported to be installed on VMware.
    Please help.
    Regards,
    Madhu

    There are some points to answer here:
    Change of resolution:
    1. login as root
    2. System > Administration > Display
    3. Change number of colors to thousands
    4. Select your resolution.
    5. Logoff
    6. Display size should change
    Certification on VMware:
    Officially there is no VMware certification of any Oracle product. You can run it in a VMware but if you encouter a problem you have to reproduce it on real hardware.
    --olaf                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • 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)

  • 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 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.

  • Missing tools for Flash CC?

    How do you download missing tools for Flash CC?

    and some were deprecated: Deprecated features in Flash Professional CC
    if you need any (like bones), use flash cs6:  in your cc desktop app>apps>filters&versions>previous versions>flash install>cs6

  • Tool for Support

    Hello,
    I am searching for a tool for SCCM.
    I have some IT responsible persons (who are not realy it technicans) in diffrent locations.
    I want to give them a possibility to deploy Software to their clients with GUI without using ConfigMgr Console.
    Does anyone knows such tools?

    Is there a reason you don't want them to have the console? You should be able to setup permissions that will only allow them to admin their area if that is the worry.
    Also are you wanting them to push the install or would they be able to go to the machine, and do the install. If they would be able to go to machine to do the install then the solution below should work for you, I have it in place in my environment.
    AD group that has the supporting team members in it
    then created a User Collection in SCCM, and based its membership on the AD group I created
    then created deployments for each of the applications that I want the support team members to have access to.
    The support team member can go to the Application Catalog on the web, and install the application from there. This allows for you to control who all has access to installs by their AD group.
    Also to make the online application catalog easier to get to I made a redirect site in IIS on the application catalog server.
    Without the redirect you have to tell your support team to go to http://ServerName/CMApplicationCatalog"
    With the redirect you can name it whatever you want like http://ServerName/apps"
    Had to add the quote to make it not link.

  • 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

  • [SOLVED] Location of header files (for vmware tools)

    Attempting to install VMWare Tools (http://www.vmware.com/support/ws5/doc/w … linux.html) for my Archlinux guest, encountered this question:
    What is the location of the directory of C header files that match your running
    kernel? [/usr/src/linux/include]
    I found a few old posts saying to use the AUR package, but I can't per my divisions linux server policies (no non-official repositories). Are these included by default, or do I need to get them via some package? Is this kernels-26-headers package, or similar?
    Last edited by Intrepidus (2010-10-25 22:38:07)

    Thanks, that got me a bit farther than before. I've now gone from that error to this error:
    The directory of kernel headers (version @@VMWARE@@ UTS_RELEASE) does not match your running kernel (version 2.6.35-ARCH). Even if the module were to compile successfully, it would not load into the running kernel.
    This was after pointing it to /usr/src/linux-2.6.35-ARCH/include. Any ideas what the story is now?
    EDIT: Had to copy utsrelease.h and autoconf.h to version.h and autoconf.h, respectively, to /usr/src/linux-2.6.35-ARCH/include/linux.
    Last edited by Intrepidus (2010-10-25 22:17:10)

  • Far tool fails to compile

    This worked a couple weeks ago on my linux machine - suddenly it's not.
    In my directory I have a server-side asc file (myapp.asc). If I type:
    /opt/adobe/fms/tools/far -compile myapp.asc
    I get a dump that looks like:
    Copyright(c) 1993-2009 Adobe Systems Incorporated. All Rights Reserved.
    Failed to compile script : myapp.asc
    *** glibc detected *** /opt/adobe/fms/tools/far: free(): invalid pointer: 0x08764330 ***
    ======= Backtrace: =========
    /lib/libc.so.6[0x80f595]
    /lib/libc.so.6(cfree+0x59)[0x80f9d9]
    /lib/libc.so.6(fclose+0x136)[0x7fdc96]
    /opt/adobe/fms/tools/far(_ZN3fms4util10TCFileUtil6fcloseEP8_IO_FILE+0x23)[0x80756f3]
    /opt/adobe/fms/tools/far(main+0x117e)[0x806c71a]
    /lib/libc.so.6(__libc_start_main+0xdc)[0x7bbe9c]
    /opt/adobe/fms/tools/far(__gxx_personality_v0+0xa1)[0x8068f11]
    ======= Memory map: ========
    00124000-00149000 r-xp 00000000 fd:00 37290028   /lib/libm-2.5.so
    00149000-0014a000 r--p 00024000 fd:00 37290028   /lib/libm-2.5.so
    0014a000-0014b000 rw-p 00025000 fd:00 37290028   /lib/libm-2.5.so
    0014d000-0022d000 r-xp 00000000 fd:00 34753334   /usr/lib/libstdc++.so.6.0.8
    0022d000-00231000 r--p 000df000 fd:00 34753334   /usr/lib/libstdc++.so.6.0.8
    08117000-0811c000 rw-p 000ce000 fd:00 19104144   /opt/adobe/fms/tools/far
    08751000-08772000 rw-p 08751000 00:00 0          [heap]
    b7fea000-b7fee000 rw-p b7fea000 00:00 0
    b7ff7000-b7ff8000 rw-p b7ff7000 00:00 0
    bfc9a000-bfcaf000 rw-p bffea000 00:00 0          [stack]
    Aborted
    I'm running Centos 5.5 - uname shows 2.6.18-194.32.1.el5.centos.plus.
    If anyone could point me in the right direction, I'd appreciate it. I just need it to compile. Thanks.

    Oh, nevermind... turns out there was a syntax error in myapp.asc. Yeah. That's some tasty shoe-leather.

  • VMware tools and hardware version for Cisco vWLC

    I am currently running a Cisco vWLC (v8.0.100.0) on VMware vSphere 5.5U2 supporting about 20 APs. I just recently upgraded to vSphere 5.5U2 and I was working my way through updating the VMware tools and VM Versions on all my VMs when I glanced at this info for the vWLC. The vWLC shows a VM version of 1 with the VMware tools not running and not installed. I am curious if it is necessary or even possible to update the VMware tools and VM version for the vWLC. The vWLC is working perfectly fine and I have no issue with leaving well enough alone, but this just kind of peeked my curiosity as I really couldn't find any concrete answers in any online documentation. Does anyone have any insight on this matter?

    If it's working, then leave it alone. Some of the Cisco virtual, well maybe most, don't support the VMWARE tools. Updating the version to the latest will make you have to use vCenter as the sphere client will not allow you to edit the VM anymore. 
    -Scott

  • How can I use some of the image i am working on to paint with? like if I wanted to give someone an extra eye in the forehead, ow could i then paint their own i in the forehead? I know there is a paint tool for that, i just can't find it ... :/

    How can I use some of the image i am working on to paint with? like if I wanted to give someone an extra eye in the forehead, ow could i then paint their own i in the forehead? I know there is a paint tool for that, i just can't find it ... :/

    It sounds like you are talking about the cloning tool?
    Tool looks like this:
    Then when selected you can change the size of the brush and using Alt (windows) and Command (Mac) to select your region you want to copy then start to create you cloned image.
    Hope this helps?

Maybe you are looking for