Installation des prérequis
Pour Ubuntu
sudo apt-get install make gcc
Pour Debian
apt-get install autoconf gcc-4.3* make psmisc linux-headers-$(uname -r)
Installation des VMTools
Dans la console du client VSphere, cliquer droit sur la VM puis « Invité - Installer/ Mettre à jour VMWare Tools »
Créer le point de montage
mkdir /mnt/cdrom
Monter le lecteur
mount /dev/cdrom /mnt/cdrom
Décompresser l’archive dans le dossier /tmp
tar xzf /mnt/cdrom/VMwareTools-9.0.1-913578.tar.gz -C /tmp
Démonter le lecteur
umount /mnt/cdrom
Lancer le script d’installation (en général, les réponses par défaut suffisent)
cd /tmp/vmware-tools-distrib/
./vmware-install.pl
Exemple
Prérequis
user@server : $ sudo apt-get install make gcc
Les paquets supplémentaires suivants seront installés :
binutils cpp cpp-4.6 gcc-4.6 libc-bin libc-dev-bin libc6 libc6-dev libgomp1 libmpc2 libmpfr4 libquadmath0 linux-libc-dev manpages-dev
Copie des fichiers
user@server : $ sudo mkdir /mnt/cdrom
user@server : $ sudo mount /dev/cdrom /mnt/cdrom
mount : périphérique bloc /dev/sr0 est protégé en écriture, sera monté en lecture seule
user@server : $ sudo tar xzf /mnt/cdrom VMwareTools-.0.1-913578.tar.gz -C /tmp
user@server : $ sudo umount /mnt/cdrom
user@server : $ cd /tmp/vmware-tools-distrib/
Installation VM Tools
user@server :/tmp/vmware-tools-distrib$ sudo ./vmware-install.pl
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]
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.0.1 build-913578 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".
Configuration
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 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.5.0-23-generic/build/include". The path "/lib/modules/3.5.0-23-generic/build/include" appears to be a valid path to the 3.5.0-23-generic kernel headers. Would you like to change it ? [no]
Using 2.6.x kernel build system. make : entrant dans le répertoire « /tmp/modconfig-NsLvWm/vmci-only » /usr/bin/make -C /lib/modules/3.5.0-23-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1] : entrant dans le répertoire « /usr/src/linux-headers-3.5.0-23-generic » CC [M] /tmp/modconfig-NsLvWm/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-NsLvWm/vmci-only/linux/vmciKernelIf.o CC [M] /tmp/modconfig-NsLvWm/vmci-only/common/vmciContext.o CC [M] /tmp/modconfig-NsLvWm/vmci-only/common/vmciDatagram.o CC [M] /tmp/modconfig-NsLvWm/vmci-only/common/vmciDoorbell.o CC [M] /tmp/modconfig-NsLvWm/vmci-only/common/vmciDriver.o CC [M] /tmp/modconfig-NsLvWm/vmci-only/common/vmciEvent.o CC [M] /tmp/modconfig-NsLvWm/vmci-only/common/vmciHashtable.o CC [M] /tmp/modconfig-NsLvWm/vmci-only/common/vmciQPair.o CC [M] /tmp/modconfig-NsLvWm/vmci-only/common/vmciQueuePair.o CC [M] /tmp/modconfig-NsLvWm/vmci-only/common/vmciResource.o CC [M] /tmp/modconfig-NsLvWm/vmci-only/common/vmciRoute.o CC [M] /tmp/modconfig-NsLvWm/vmci-only/driverLog.o LD [M] /tmp/modconfig-NsLvWm/vmci-only/vmci.o Building modules, stage 2. MODPOST 1 modules CC /tmp/modconfig-NsLvWm/vmci-only/vmci.mod.o LD [M] /tmp/modconfig-NsLvWm/vmci-only/vmci.ko make[1] : quittant le répertoire « /usr/src/linux-headers-3.5.0-23-generic » /usr/bin/make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1] : entrant dans le répertoire « /tmp/modconfig-NsLvWm/vmci-only » make[1] : « postbuild » est à jour. make[1] : quittant le répertoire « /tmp/modconfig-NsLvWm/vmci-only » cp -f vmci.ko ./../vmci.o make : quittant le répertoire « /tmp/modconfig-NsLvWm/vmci-only »
Using 2.6.x kernel build system. make : entrant dans le répertoire « /tmp/modconfig-UZLtzM/vmci-only » /usr/bin/make -C /lib/modules/3.5.0-23-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1] : entrant dans le répertoire « /usr/src/linux-headers-3.5.0-23-generic » CC [M] /tmp/modconfig-UZLtzM/vmci-only/linux/driver.o CC [M] /tmp/modconfig-UZLtzM/vmci-only/linux/vmciKernelIf.o CC [M] /tmp/modconfig-UZLtzM/vmci-only/common/vmciContext.o CC [M] /tmp/modconfig-UZLtzM/vmci-only/common/vmciDatagram.o CC [M] /tmp/modconfig-UZLtzM/vmci-only/common/vmciDoorbell.o CC [M] /tmp/modconfig-UZLtzM/vmci-only/common/vmciDriver.o CC [M] /tmp/modconfig-UZLtzM/vmci-only/common/vmciEvent.o CC [M] /tmp/modconfig-UZLtzM/vmci-only/common/vmciHashtable.o CC [M] /tmp/modconfig-UZLtzM/vmci-only/common/vmciQPair.o CC [M] /tmp/modconfig-UZLtzM/vmci-only/common/vmciQueuePair.o CC [M] /tmp/modconfig-UZLtzM/vmci-only/common/vmciResource.o CC [M] /tmp/modconfig-UZLtzM/vmci-only/common/vmciRoute.o CC [M] /tmp/modconfig-UZLtzM/vmci-only/driverLog.o LD [M] /tmp/modconfig-UZLtzM/vmci-only/vmci.o Building modules, stage 2. MODPOST 1 modules CC /tmp/modconfig-UZLtzM/vmci-only/vmci.mod.o LD [M] /tmp/modconfig-UZLtzM/vmci-only/vmci.ko make[1] : quittant le répertoire « /usr/src/linux-headers-3.5.0-23-generic » /usr/bin/make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1] : entrant dans le répertoire « /tmp/modconfig-UZLtzM/vmci-only » make[1] : « postbuild » est à jour. make[1] : quittant le répertoire « /tmp/modconfig-UZLtzM/vmci-only » cp -f vmci.ko ./../vmci.o make : quittant le répertoire « /tmp/modconfig-UZLtzM/vmci-only » Using 2.6.x kernel build system. make : entrant dans le répertoire « /tmp/modconfig-UZLtzM/vsock-only » /usr/bin/make -C /lib/modules/3.5.0-23-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1] : entrant dans le répertoire « /usr/src/linux-headers-3.5.0-23-generic » CC [M] /tmp/modconfig-UZLtzM/vsock-only/linux/af_vsock.o CC [M] /tmp/modconfig-UZLtzM/vsock-only/linux/notify.o CC [M] /tmp/modconfig-UZLtzM/vsock-only/linux/notifyQState.o CC [M] /tmp/modconfig-UZLtzM/vsock-only/linux/stats.o CC [M] /tmp/modconfig-UZLtzM/vsock-only/linux/util.o CC [M] /tmp/modconfig-UZLtzM/vsock-only/linux/vsockAddr.o CC [M] /tmp/modconfig-UZLtzM/vsock-only/driverLog.o LD [M] /tmp/modconfig-UZLtzM/vsock-only/vsock.o Building modules, stage 2. MODPOST 1 modules CC /tmp/modconfig-UZLtzM/vsock-only/vsock.mod.o LD [M] /tmp/modconfig-UZLtzM/vsock-only/vsock.ko make[1] : quittant le répertoire « /usr/src/linux-headers-3.5.0-23-generic » /usr/bin/make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1] : entrant dans le répertoire « /tmp/modconfig-UZLtzM/vsock-only » make[1] : « postbuild » est à jour. make[1] : quittant le répertoire « /tmp/modconfig-UZLtzM/vsock-only » cp -f vsock.ko ./../vsock.o make : quittant le répertoire « /tmp/modconfig-UZLtzM/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] 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 ? [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.5.0-23-generic vmware-tools start/running The configuration of VMware Tools 9.0.1 build-913578 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
Commentaires