Debian 7.8 VMWare Tools installieren


open-vm-tools

VMWare empfiehlt mittlerweile, die open-vm-Tools zu verwenden.
Installation:

# apt-get install open-vm-Tools

Manuelle Installation

Wer jedoch die Tools passend zur virtuellen Umgebung installieren möchte, kann folgende Schritte verwenden:

Benötigte Programme installieren

# apt-get install gcc make
# apt-get install linux-headers-$(uname -r)

Virtuelle CD über die vSphere Client Console einlegen
vmtools

mounten der cd mit

# mount /dev/cdrom /mnt/

Auspacken des Archivs mit

# tar -zxf /mnt/VMwareTools-#.#.#-######.tar.gz -C /usr/src/

dismount der cd und Verzeichnis wechseln

# umount /mnt
# cd /usr/src/vmware-tools-distrib/

Installation/Konfiguration starten

# ./vmware-install.pl

Normalerweise können alle Fragen mit dem vorgegebenen Standard beantwortet werden.

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]

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 9.0.0 build-782409 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

The VMware FileSystem Sync Driver (vmsync) allows external third-party backup
software that is integrated with vSphere to create backups of the virtual
machine. 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.2.0-4-amd64/build/include".
The path "/lib/modules/3.2.0-4-amd64/build/include" appears to be a valid path
to the 3.2.0-4-amd64 kernel headers.
Would you like to change it? [no]

Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-6Va5xI/vmci-only'
/usr/bin/make -C /lib/modules/3.2.0-4-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. 
         MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-4-amd64'
 CC [M]  /tmp/modconfig-6Va5xI/vmci-only/linux/driver.o
 CC [M]  /tmp/modconfig-6Va5xI/vmci-only/linux/vmciKernelIf.o
 CC [M]  /tmp/modconfig-6Va5xI/vmci-only/common/vmciContext.o
 CC [M]  /tmp/modconfig-6Va5xI/vmci-only/common/vmciDatagram.o
 CC [M]  /tmp/modconfig-6Va5xI/vmci-only/common/vmciDoorbell.o
 CC [M]  /tmp/modconfig-6Va5xI/vmci-only/common/vmciDriver.o
 CC [M]  /tmp/modconfig-6Va5xI/vmci-only/common/vmciEvent.o
 CC [M]  /tmp/modconfig-6Va5xI/vmci-only/common/vmciHashtable.o
 CC [M]  /tmp/modconfig-6Va5xI/vmci-only/common/vmciQPair.o
 CC [M]  /tmp/modconfig-6Va5xI/vmci-only/common/vmciQueuePair.o
 CC [M]  /tmp/modconfig-6Va5xI/vmci-only/common/vmciResource.o
 CC [M]  /tmp/modconfig-6Va5xI/vmci-only/common/vmciRoute.o
 CC [M]  /tmp/modconfig-6Va5xI/vmci-only/driverLog.o
 LD [M]  /tmp/modconfig-6Va5xI/vmci-only/vmci.o
 Building modules, stage 2.
 MODPOST 1 modules
 CC      /tmp/modconfig-6Va5xI/vmci-only/vmci.mod.o
 LD [M]  /tmp/modconfig-6Va5xI/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-4-amd64'
/usr/bin/make -C $PWD SRCROOT=$PWD/. 
         MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-6Va5xI/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-6Va5xI/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/modconfig-6Va5xI/vmci-only'

Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-wIELEL/vmci-only'
/usr/bin/make -C /lib/modules/3.2.0-4-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. 
         MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-4-amd64'
 CC [M]  /tmp/modconfig-wIELEL/vmci-only/linux/driver.o
 CC [M]  /tmp/modconfig-wIELEL/vmci-only/linux/vmciKernelIf.o
 CC [M]  /tmp/modconfig-wIELEL/vmci-only/common/vmciContext.o
 CC [M]  /tmp/modconfig-wIELEL/vmci-only/common/vmciDatagram.o
 CC [M]  /tmp/modconfig-wIELEL/vmci-only/common/vmciDoorbell.o
 CC [M]  /tmp/modconfig-wIELEL/vmci-only/common/vmciDriver.o
 CC [M]  /tmp/modconfig-wIELEL/vmci-only/common/vmciEvent.o
 CC [M]  /tmp/modconfig-wIELEL/vmci-only/common/vmciHashtable.o
 CC [M]  /tmp/modconfig-wIELEL/vmci-only/common/vmciQPair.o
 CC [M]  /tmp/modconfig-wIELEL/vmci-only/common/vmciQueuePair.o
 CC [M]  /tmp/modconfig-wIELEL/vmci-only/common/vmciResource.o
 CC [M]  /tmp/modconfig-wIELEL/vmci-only/common/vmciRoute.o
 CC [M]  /tmp/modconfig-wIELEL/vmci-only/driverLog.o
 LD [M]  /tmp/modconfig-wIELEL/vmci-only/vmci.o
 Building modules, stage 2.
 MODPOST 1 modules
 CC      /tmp/modconfig-wIELEL/vmci-only/vmci.mod.o
 LD [M]  /tmp/modconfig-wIELEL/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-4-amd64'
/usr/bin/make -C $PWD SRCROOT=$PWD/. 
         MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-wIELEL/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-wIELEL/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/modconfig-wIELEL/vmci-only'

Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-wIELEL/vsock-only'
/usr/bin/make -C /lib/modules/3.2.0-4-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. 
         MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-4-amd64'
 CC [M]  /tmp/modconfig-wIELEL/vsock-only/linux/af_vsock.o
 CC [M]  /tmp/modconfig-wIELEL/vsock-only/linux/notify.o
 CC [M]  /tmp/modconfig-wIELEL/vsock-only/linux/notifyQState.o
 CC [M]  /tmp/modconfig-wIELEL/vsock-only/linux/stats.o
 CC [M]  /tmp/modconfig-wIELEL/vsock-only/linux/util.o
 CC [M]  /tmp/modconfig-wIELEL/vsock-only/linux/vsockAddr.o
 CC [M]  /tmp/modconfig-wIELEL/vsock-only/driverLog.o
 LD [M]  /tmp/modconfig-wIELEL/vsock-only/vsock.o
 Building modules, stage 2.
 MODPOST 1 modules
 CC      /tmp/modconfig-wIELEL/vsock-only/vsock.mod.o
 LD [M]  /tmp/modconfig-wIELEL/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-4-amd64'
/usr/bin/make -C $PWD SRCROOT=$PWD/. 
         MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-wIELEL/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-wIELEL/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/modconfig-wIELEL/vsock-only'

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? [no]

Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-VFP4v0/vmxnet-only'
/usr/bin/make -C /lib/modules/3.2.0-4-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. 
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-4-amd64'
 CC [M]  /tmp/modconfig-VFP4v0/vmxnet-only/vmxnet.o
 Building modules, stage 2.
 MODPOST 1 modules
 CC      /tmp/modconfig-VFP4v0/vmxnet-only/vmxnet.mod.o
 LD [M]  /tmp/modconfig-VFP4v0/vmxnet-only/vmxnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-4-amd64'
/usr/bin/make -C $PWD SRCROOT=$PWD/. 
         MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-VFP4v0/vmxnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-VFP4v0/vmxnet-only'
cp -f vmxnet.ko ./../vmxnet.o
make: Leaving directory `/tmp/modconfig-VFP4v0/vmxnet-only'

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?
[no]

!!! [EXPERIMENTAL] !!!
VMware automatic kernel modules enables automatic building and installation of
VMware kernel modules at boot that 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]

No X install found.

Creating a new initrd boot image for the kernel.
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
   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:                           done
   Guest operating system daemon:                                      done
The configuration of VMware Tools 9.0.0 build-782409 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

Im vSphere Client erkennt man, ob die Tools geladen wurden
vmtools2