1 2 Previous Next 15 Replies Latest reply: Dec 3, 2013 9:35 AM by WoodyZ RSS

VMtools installation problem on Ubuntu 13.04

LinuxG1rl Novice
Currently Being Moderated

Hi,

 

I  have a vm (workstation 8.0.6) running with ubuntu 13.04 64 bit - I am trying to install vm tools, but am getting this error in the middle of the installation:

 

"The path "" is not a valid path to the 3.8.0-19-generic kernel headers"

 

It gives me this error all the time, even after I did sudo apt-get update && sudo apt-get install build-essential linux-headers-$(uname -r)

 

Any suggestions?

 

Thanks!

  • 1. Re: VMtools installation problem on Ubuntu 13.04
    LinuxG1rl Novice
    Currently Being Moderated

    Update:

     

    I did this:

     

    cd /lib/modules/3.8.0-19-generic/build/include/linux

    ln -s ../generated/uapi/linux/version.h .

     

    It seems to have solved the above issue, but gave other errors, please see output for further help:

     

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

     

    vmware-tools stop/waiting
    This program previously created the file
    /usr/lib/vmware-tools/lib64/libconf/etc/pango/pango.modules, and was about to
    remove it.  Somebody else apparently did it already.

     

    File /etc/vmware-tools/vmware-user.desktop is backed up to
    /etc/vmware-tools/vmware-user.desktop.old.12.

     

    File /usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gtk.immodules is backed up
    to /usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gtk.immodules.old.12.

     

    File /usr/lib/vmware-tools/lib64/libconf/etc/fonts/fonts.conf is backed up to
    /usr/lib/vmware-tools/lib64/libconf/etc/fonts/fonts.conf.old.12.

     

    File /usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gdk-pixbuf.loaders is
    backed up to
    /usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gdk-pixbuf.loaders.old.12.

     

    This program previously created the file
    /usr/lib/vmware-tools/libconf/etc/gtk-2.0/gdk-pixbuf.loaders, and was about to
    remove it.  Somebody else apparently did it already.

     

    This program previously created the file
    /usr/lib/vmware-tools/lib64/libconf/etc/pango/pangorc, and was about to remove
    it.  Somebody else apparently did it already.

     

    This program previously created the file
    /usr/lib/vmware-tools/libconf/etc/gtk-2.0/gtk.immodules, and was about to
    remove it.  Somebody else apparently did it already.

     

    This program previously created the file
    /usr/lib/vmware-tools/lib64/libconf/etc/pango/pangox.aliases, and was about to
    remove it.  Somebody else apparently did it already.

     

    File /etc/pulse/default.pa is backed up to /etc/pulse/default.pa.old.12.

     

    update-initramfs: Generating /boot/initrd.img-3.8.0-19-generic
    update-initramfs: Generating /boot/initrd.img-3.5.0-28-generic
    update-initramfs: Generating /boot/initrd.img-3.2.0-38-generic
    update-initramfs: Generating /boot/initrd.img-3.0.0-19-generic
    The removal of VMware Tools 8.8.6 build-1035889 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]

     

    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 8.8.6 build-1035889 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.

     

     

     

    [EXPERIMENTAL] The VMware FileSystem Sync Driver (vmsync) is a new feature that
    creates backups of virtual machines. Please refer to the VMware Knowledge Base
    for more details on this capability. Do you wish to enable this feature?
    [no]

     


    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.8.0-19-generic/build/include".
    The path "/lib/modules/3.8.0-19-generic/build/include" appears to be a valid
    path to the 3.8.0-19-generic kernel headers.
    Would you like to change it? [no]

     

    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmci-only'
    make -C /lib/modules/3.8.0-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-headers-3.8.0-19-generic'
      CC [M]  /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/linux/driver.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/driverLog.o
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:127:4: error: implicit declaration of function ‘__devexit_p’ [-Werror=implicit-function-declaration]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:127:4: error: initializer element is not constant
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:127:4: error: (near initialization for ‘vmci_driver.remove’)
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:1745:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘vmci_probe_device’
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:1973:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘vmci_remove_device’
    /tmp/vmware-root/modules/vmci-only/linux/driver.c: In function ‘__check_disable_host’:
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2498:1: warning: return from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c: In function ‘__check_disable_guest’:
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2501:1: warning: return from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c: In function ‘__check_disable_msi’:
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2504:1: warning: return from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c: In function ‘__check_disable_msix’:
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2507:1: warning: return from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c: At top level:
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:119:12: warning: ‘vmci_probe_device’ used but never defined [enabled by default]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:121:13: warning: ‘vmci_remove_device’ used but never defined [enabled by default]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2054:1: warning: ‘vmci_interrupt’ defined but not used [-Wunused-function]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2128:1: warning: ‘vmci_interrupt_bm’ defined but not used [-Wunused-function]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:1708:1: warning: ‘vmci_enable_msix’ defined but not used [-Wunused-function]
    cc1: some warnings being treated as errors
    make[2]: *** [/tmp/vmware-root/modules/vmci-only/linux/driver.o] Error 1
    make[2]: *** Waiting for unfinished jobs....
    make[1]: *** [_module_/tmp/vmware-root/modules/vmci-only] Error 2
    make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-19-generic'
    make: *** [vmci.ko] Error 2
    make: Leaving directory `/tmp/vmware-root/modules/vmci-only'

     

    The communication service is used in addition to the standard communication
    between the guest and the host.  The rest of the software provided by VMware
    Tools is designed to work independently of this feature.
    If you wish to have the VMCI 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 ]

     

    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmci-only'
    make -C /lib/modules/3.8.0-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-headers-3.8.0-19-generic'
      CC [M]  /tmp/vmware-root/modules/vmci-only/linux/driver.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
      CC [M]  /tmp/vmware-root/modules/vmci-only/driverLog.o
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:127:4: error: implicit declaration of function ‘__devexit_p’ [-Werror=implicit-function-declaration]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:127:4: error: initializer element is not constant
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:127:4: error: (near initialization for ‘vmci_driver.remove’)
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:1745:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘vmci_probe_device’
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:1973:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘vmci_remove_device’
    /tmp/vmware-root/modules/vmci-only/linux/driver.c: In function ‘__check_disable_host’:
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2498:1: warning: return from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c: In function ‘__check_disable_guest’:
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2501:1: warning: return from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c: In function ‘__check_disable_msi’:
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2504:1: warning: return from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c: In function ‘__check_disable_msix’:
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2507:1: warning: return from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c: At top level:
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:119:12: warning: ‘vmci_probe_device’ used but never defined [enabled by default]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:121:13: warning: ‘vmci_remove_device’ used but never defined [enabled by default]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2054:1: warning: ‘vmci_interrupt’ defined but not used [-Wunused-function]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2128:1: warning: ‘vmci_interrupt_bm’ defined but not used [-Wunused-function]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:1708:1: warning: ‘vmci_enable_msix’ defined but not used [-Wunused-function]
    cc1: some warnings being treated as errors
    make[2]: *** [/tmp/vmware-root/modules/vmci-only/linux/driver.o] Error 1
    make[2]: *** Waiting for unfinished jobs....
    make[1]: *** [_module_/tmp/vmware-root/modules/vmci-only] Error 2
    make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-19-generic'
    make: *** [vmci.ko] Error 2
    make: Leaving directory `/tmp/vmware-root/modules/vmci-only'

     

    The VM communication interface socket family is used in conjunction with the VM
    communication interface to provide a new communication path among guests and
    host.  The rest of this software provided by VMware Tools is designed to work
    independently of this feature.  If you wish to have the VSOCK 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 the Enter key to continue.]

     

    The module vmxnet3 has already been installed on this system by another
    installer or package and will not be modified by this installer.  Use the flag
    --clobber-kernel-modules=vmxnet3 to override.

     

    The module pvscsi has already been installed on this system by another
    installer or package and will not be modified by this installer.  Use the flag
    --clobber-kernel-modules=pvscsi to override.

     

    The module vmmemctl has already been installed on this system by another
    installer or package and will not be modified by this installer.  Use the flag
    --clobber-kernel-modules=vmmemctl to override.

     

    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]

     

    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmxnet-only'
    make -C /lib/modules/3.8.0-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-headers-3.8.0-19-generic'
      CC [M]  /tmp/vmware-root/modules/vmxnet-only/vmxnet.o
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:525:4: error: unknown field ‘get_rx_csum’ specified in initializer
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:525:4: warning: initialization from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:525:4: warning: (near initialization for ‘vmxnet_ethtool_ops.get_eeprom_len’) [enabled by default]
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:526:4: error: unknown field ‘set_rx_csum’ specified in initializer
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:526:4: warning: initialization from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:526:4: warning: (near initialization for ‘vmxnet_ethtool_ops.get_eeprom’) [enabled by default]
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:527:4: error: unknown field ‘get_tx_csum’ specified in initializer
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:527:4: warning: initialization from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:527:4: warning: (near initialization for ‘vmxnet_ethtool_ops.set_eeprom’) [enabled by default]
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:528:4: error: unknown field ‘set_tx_csum’ specified in initializer
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:528:4: warning: initialization from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:528:4: warning: (near initialization for ‘vmxnet_ethtool_ops.get_coalesce’) [enabled by default]
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:529:4: error: unknown field ‘get_sg’ specified in initializer
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:529:27: error: ‘ethtool_op_get_sg’ undeclared here (not in a function)
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:530:4: error: unknown field ‘set_sg’ specified in initializer
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:530:27: error: ‘ethtool_op_set_sg’ undeclared here (not in a function)
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:532:4: error: unknown field ‘get_tso’ specified in initializer
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:532:27: error: ‘ethtool_op_get_tso’ undeclared here (not in a function)
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:533:4: error: unknown field ‘set_tso’ specified in initializer
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:533:4: warning: initialization from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:533:4: warning: (near initialization for ‘vmxnet_ethtool_ops.get_pauseparam’) [enabled by default]
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:535:4: error: unknown field ‘get_ufo’ specified in initializer
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:535:27: error: ‘ethtool_op_get_ufo’ undeclared here (not in a function)
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_probe_device’:
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1008:7: error: unknown field ‘ndo_set_multicast_list’ specified in initializer
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1008:7: warning: initialization from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1008:7: warning: (near initialization for ‘vmxnet_netdev_ops.ndo_vlan_rx_add_vid’) [enabled by default]
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_map_pkt’:
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2085:32: error: incompatible type for argument 2 of ‘pci_map_page’
    In file included from /usr/src/linux-headers-3.8.0-19-generic/arch/x86/include/asm/pci.h:148:0,
                     from include/linux/pci.h:1422,
                     from /tmp/vmware-root/modules/vmxnet-only/./shared/compat_pci.h:27,
                     from /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:31:
    include/asm-generic/pci-dma-compat.h:43:1: note: expected ‘struct page *’ but argument is of type ‘struct <anonymous>’
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2104:26: error: incompatible type for argument 2 of ‘pci_map_page’
    In file included from /usr/src/linux-headers-3.8.0-19-generic/arch/x86/include/asm/pci.h:148:0,
                     from include/linux/pci.h:1422,
                     from /tmp/vmware-root/modules/vmxnet-only/./shared/compat_pci.h:27,
                     from /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:31:
    include/asm-generic/pci-dma-compat.h:43:1: note: expected ‘struct page *’ but argument is of type ‘struct <anonymous>’
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_rx_frags’:
    /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2599:48: error: incompatible types when assigning to type ‘struct <anonymous>’ from type ‘struct page *’
    make[2]: *** [/tmp/vmware-root/modules/vmxnet-only/vmxnet.o] Error 1
    make[1]: *** [_module_/tmp/vmware-root/modules/vmxnet-only] Error 2
    make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-19-generic'
    make: *** [vmxnet.ko] Error 2
    make: Leaving directory `/tmp/vmware-root/modules/vmxnet-only'

     

    The fast network device driver (vmxnet module) is used only for our fast
    networking interface. The rest of the software provided by VMware Tools is
    designed to work independently of this feature.
    If you wish to have the fast network driver enabled, you can install the driver
    by running vmware-config-tools.pl again after making sure that gcc, binutils,
    make and the kernel sources for your running kernel are installed on your
    machine. These packages are available on your distribution's installation CD.
    [ Press Enter key to continue ]

     

    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmblock-only'
    make -C /lib/modules/3.8.0-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-headers-3.8.0-19-generic'
      CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/block.o
      CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/control.o
      CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o
      CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/dentry.o
      CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/file.o
      CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o
      CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/inode.o
      CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/module.o
      CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/stubs.o
      CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/super.o
    /tmp/vmware-root/modules/vmblock-only/linux/control.c: In function ‘ExecuteBlockOp’:
    /tmp/vmware-root/modules/vmblock-only/linux/control.c:285:9: warning: assignment from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmblock-only/linux/control.c:296:4: warning: passing argument 1 of ‘putname’ from incompatible pointer type [enabled by default]
    In file included from include/linux/proc_fs.h:5:0,
                     from /tmp/vmware-root/modules/vmblock-only/linux/control.c:28:
    include/linux/fs.h:2052:13: note: expected ‘struct filename *’ but argument is of type ‘char *’
    /tmp/vmware-root/modules/vmblock-only/linux/inode.c:49:4: warning: initialization from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmblock-only/linux/inode.c:49:4: warning: (near initialization for ‘RootInodeOps.lookup’) [enabled by default]
    /tmp/vmware-root/modules/vmblock-only/linux/dentry.c:38:4: warning: initialization from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmblock-only/linux/dentry.c:38:4: warning: (near initialization for ‘LinkDentryOps.d_revalidate’) [enabled by default]
    /tmp/vmware-root/modules/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:
    /tmp/vmware-root/modules/vmblock-only/linux/dentry.c:104:7: warning: passing argument 2 of ‘actualDentry->d_op->d_revalidate’ makes integer from pointer without a cast [enabled by default]
    /tmp/vmware-root/modules/vmblock-only/linux/dentry.c:104:7: note: expected ‘unsigned int’ but argument is of type ‘struct nameidata *’
      LD [M]  /tmp/vmware-root/modules/vmblock-only/vmblock.o
      Building modules, stage 2.
      MODPOST 1 modules
    WARNING: "putname" [/tmp/vmware-root/modules/vmblock-only/vmblock.ko] undefined!
      CC      /tmp/vmware-root/modules/vmblock-only/vmblock.mod.o
      LD [M]  /tmp/vmware-root/modules/vmblock-only/vmblock.ko
    make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-19-generic'
    make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
    make[1]: Entering directory `/tmp/vmware-root/modules/vmblock-only'
    make[1]: `postbuild' is up to date.
    make[1]: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
    cp -f vmblock.ko ./../vmblock.o
    make: Leaving directory `/tmp/vmware-root/modules/vmblock-only'

     

    !!! [EXPERIMENTAL] !!!
    VMware automatic kernel modules enables automatic building and installation of
    VMware kernel modules at boot they are not already present.  By selecting yes,
    you will be enabling this experimental feature.  You can always disable this
    feature by re-running vmware-config-tools.pl.

     

    Would you like to enable VMware automatic kernel modules?
    [no]

     


    Disabling timer-based audio scheduling in pulseaudio.

     

     

     

    Detected X server version 1.13.3

     

     

     

    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.8.0-19-generic
    vmware-tools start/running
    The configuration of VMware Tools 8.8.6 build-1035889 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 or by invoking "/usr/bin/vmware-toolbox" from the command line
    during an X server session.

     

    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

  • 2. Re: VMtools installation problem on Ubuntu 13.04
    mfelker Expert
    Currently Being Moderated

    "The path "" is not a valid path to the 3.8.0-19-generic kernel headers"

     

    I have seen this error many times when installing VMware Tools.  Rerun sudo ./vmware-install.pl again.   What I found out after a lot of frustration is you just say "no" when it asks do you want to change this   Since you have already installed the headers and the build environment this works for me and then I  continue with the script and Tools installs. .  Please keep in mind that I haven't tried this with the kernel you are using so it might not work. 

  • 3. Re: VMtools installation problem on Ubuntu 13.04
    LinuxG1rl Novice
    Currently Being Moderated

    Hi mfelker,

     

    In my previous post I wrote:

     

     

    "Update:

    I did this:

    cd /lib/modules/3.8.0-19-generic/build/include/linux

    ln -s ../generated/uapi/linux/version.h .

    It seems to have solved the above issue, but gave other errors, please see output for further help:"

     

    So that specific problem with invalid path was corrected, but many other issues came up, for example, no more shared folder, and so on. So I downgraded my VM back to ubuntu 12.04.

     

    I would like to go back to the 13.04, but I need to be sure that things like shared folders will work. Any idea how to completely fix this problem? (above log still valid).

     

    Thanks!

  • 4. Re: VMtools installation problem on Ubuntu 13.04
    EdP Hot Shot
    Currently Being Moderated

    Wish I could help. I confirm this to be an issue.

     

    However the following may help home in on the just to home in on the problem area. I installed the Ringtail version of UbuntuGnome as a fresh guest (running under a Win8 host). It detected and installed vmware tools automatically without issue, however as soon as the guest updated the kernel to 3.8-0-19 it all went sour. Attempts to reinstall vmware tools aborted with issues similar to the ones you list.

     

    The Liquorix version  of 3.8-0-13 has similar vmware tools incompatibilities when used to upgrade the kernel of a Debian Sid guest install. Looks like we are back to the bad old days of vmware linux incompatibilities.

     

    btw the problems are even worse if you upgrade from a previous Ubuntu version, as then kernel panics seem to be a fairly typical problem.

  • 5. Re: VMtools installation problem on Ubuntu 13.04
    LinuxG1rl Novice
    Currently Being Moderated

    sigh....dont even know what to say....and now I have another problem....am almost giving up on VM :-( Will post in another thread as it is not vmtools related :-(

  • 6. Re: VMtools installation problem on Ubuntu 13.04
    zhfjyq Novice
    Currently Being Moderated

    hi,i meeted the same problem ,and using below steps to solved,may it can help you.

    1. cd /usr/src/linux-headers-3.8.0-22-generic/include/linux

    2. sudo ln -s ../generated/uapi/linux/version.h

    3. download the lastest version vmtools from :CDS Repository - /www/stage/session-32/cds/vmw-desktop/fusion/5.0.3/1040386/packages

    4. extract it in ubuntu

    5. cd vmware-tools-distrib/lib/modules/source

    6. Using attachment files to replace vmci.tar & vmhgfs.tar

    7. return vmware-tools-distrib/

    8. run sudo ./vmware-install.pl

     

    All OK.

  • 7. Re: VMtools installation problem on Ubuntu 13.04
    LinuxG1rl Novice
    Currently Being Moderated

    hi

     

    vmci.tar & vmhgfs.tar files that you attached here?

     

    did anyone else manage to install vmtools on ubuntu 13.04?

     

    thanks!

  • 8. Re: VMtools installation problem on Ubuntu 13.04
    WoodyZ Guru
    Currently Being Moderated

    LinuxG1rl wrote: vmci.tar & vmhgfs.tar files that you attached here?

     

    It looks like they were taken from com.vmware.fusion.tools.linux.zip.tar and I looked at the attached files and compared what was patched and it appears okay.  In the vmhgfs.tar file the inode.c file was patched and in the vmci.tar file the driver.c file was patched.

     

    I have not tried using them however I'd have no problem doing so after reviewing what was patched!

  • 9. Re: VMtools installation problem on Ubuntu 13.04
    WoodyZ Guru
    Currently Being Moderated

    Okay in a Terminal in an Ubuntu 13.04 Virtual Machine I use the following command:

     

    Note: Copy and paste, as is, into the Terminal so as to avoid any typos.  Make sure you copy the entire command line.

     

    sudo ln -s /usr/src/linux-headers-$(uname -r)/include/generated/uapi/linux/version.h /usr/src/linux-headers-$(uname -r)/include/linux/version.h

     

    Next I extracted the contents of the VMwareTools-9.2.2-893683.tar.gz file to /tmp and then replaced the existing vmhgfs.tar file and vmci.tar file in /tmp/vmware-tools-distrib/lib/modules/source with the ones attached by zhfjyq.

     

    Then in a Terminal I cd to /tmp/vmware-tools-distrib and issued the following command to install VMware Tools:

     

    sudo ./vmware-install.pl

     

    After installing VMware Tools I shutdown the VM and set a VMware Shared Folder then started the VM and tested, VMware Shared Folder, Drag & Drop and Copy and Paste (the last two in both directions) and all work as expected.

     

    BTW... I tested using VMware Fusion 5.0.3 and an Ubuntu 13.04 Guest however although I haven't compared the latest Linux VMware Tools for VMware Player/Workstation I see no reason why it shouldn't work in VMware Workstation 9.0.2 or VMware Player 5.0.2 although one might want to use the the VMware Tools for the corresponding VMware product version!   It worth a try either way.

  • 10. Re: VMtools installation problem on Ubuntu 13.04
    mykmelez Hot Shot
    Currently Being Moderated

    I followed these instructions in the VM I just updated from Ubuntu 64-bit 12.10 to 13.04, and they worked for me! The modules compiled successfully, and shared folders now work.

     

    Before doing so, however, I too examined the source code differences, which are relatively minor and appear to be safe:

     

    myk@ubuntu:~/Downloads$ diff -ur foo bar
    diff -ur foo/vmci-only/linux/driver.c bar/vmci-only/linux/driver.c
    --- foo/vmci-only/linux/driver.c    2012-10-31 16:59:58.000000000 -0700
    +++ bar/vmci-only/linux/driver.c    2013-05-29 23:30:55.000000000 -0700
    @@ -124,7 +124,8 @@
        .name     = "vmci",
        .id_table = vmci_ids,
        .probe = vmci_probe_device,
    -   .remove = __devexit_p(vmci_remove_device),
    +//   .remove = __devexit_p(vmci_remove_device),
    +   .remove = vmci_remove_device,
     };
     #if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 19)
    @@ -1750,7 +1751,7 @@
      *-----------------------------------------------------------------------------
      */
    -static int __devinit
    +static int
     vmci_probe_device(struct pci_dev *pdev,           // IN: vmci PCI device
                       const struct pci_device_id *id) // IN: matching device ID
     {
    @@ -1978,7 +1979,7 @@
      *-----------------------------------------------------------------------------
      */
    -static void __devexit
    +static void 
     vmci_remove_device(struct pci_dev* pdev)
     {
        struct vmci_device *dev = pci_get_drvdata(pdev);
    diff -ur foo/vmhgfs-only/inode.c bar/vmhgfs-only/inode.c
    --- foo/vmhgfs-only/inode.c    2012-10-31 16:58:29.000000000 -0700
    +++ bar/vmhgfs-only/inode.c    2013-05-30 00:00:53.000000000 -0700
    @@ -50,6 +50,18 @@
     #include "fsutil.h"
     #include "vm_assert.h"
    + int vmtruncate(struct inode *inode, loff_t newsize)
    + {
    +     int error;
    +     error = inode_newsize_ok(inode, newsize);
    +
    +     if (error)
    +          return error;
    +     truncate_setsize(inode, newsize);
    +     truncate_pagecache(inode, newsize, inode->i_size);
    +     return 0;
    + }
    +
     /* Private functions. */
     static int HgfsDelete(struct inode *dir,
                           struct dentry *dentry,

     

    -myk

  • 11. Re: VMtools installation problem on Ubuntu 13.04
    LinuxG1rl Novice
    Currently Being Moderated

    WoodyZ - that is fantastic, worked like a charm - and thanks for checking out the content and nature of the changes made on these two files ;-)

     

    You were all very helpful, thanks!!!!!

  • 12. Re: VMtools installation problem on Ubuntu 13.04
    GreenVomit8 Lurker
    Currently Being Moderated

    Thanks Woody. Commands worked for me as well

  • 13. Re: VMtools installation problem on Ubuntu 13.04
    WoodyZ Guru
    Currently Being Moderated

    GreenVomit8 wrote: Thanks Woody. Commands worked for me as well

     

    I wrote a script to automate the whole process, have a look at: Re: File sharing on Player betw host and guest doesn't work on Ubuntu 13.04

  • 14. Re: VMtools installation problem on Ubuntu 13.04
    mascotca Lurker
    Currently Being Moderated

    [ sorry somehow my first post was mistakenly addressed to LinuxG1rl)

     

    Woody:

     

    Would it be "worth a try" in Fusion Version 4.1.4? (I'm stuck on hardware that can't go beyond OS X Lion i.e. 10.7.5)?

     

    The Vmware Tools install supposedly worked but I don't have the Sharing Folder and the Drag & Drop (either way) etc. capabilities I'm supposed to and am hoping to get the latest Ubuntu or Linux Mint (based on Ubuntu) working properly with Fusion 4.1.4 sometime this century.

     

    Or will the Fusion 5 updated files (vmhgfs.tar file and vmci.tar file) that you and blow everything up?

     

    TIA

1 2 Previous Next

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 6 points

Share This Page