VMware Tools in Debian installieren
Hinweis: Bitte beachten Sie, dass dieser Artikel / diese Kategorie sich entweder auf ältere Software/Hardware Komponenten bezieht oder aus sonstigen Gründen nicht mehr gewartet wird. Diese Seite wird nicht mehr aktualisiert und ist rein zu Referenzzwecken noch hier im Archiv abrufbar. |
---|
Für Debian gibt es bislang für die VMware Tools keine vorgefertigten Operating System Specific Packages (OSPs) von VMware wie es sie etwa für Ubuntu gibt.[1] Da die von Debian mitgelieferten open-vm-tools von VMware nicht supportet werden müssen die VMware Tools unter Debian für eine vollständig supportete Umgebung manuell installiert werden.
VMware Tools installieren
Die Installation kann im vSphere Client für die betreffende virtuelle Maschine über den Punkt Install/Upgrade VMware Tools aufgerufen werden. Die folgenden Schritte zeigen die Installation der notwendigen Pakete sowie das manuelle Starten der Installation, da diese in der virtuellen Maschine nicht automatisch gestartet wird. Im diesem Beispiel läuft die virtuelle Maschine mit Debian 6 64-bit auf einem ESXi 5.0 Host:
mount /dev/cdrom /mnt
cp /mnt/VMwareTools-8.6.0-425873.tar.gz /root/
cd /root/
tar xzf VMwareTools-8.6.0-425873.tar.gz
cd vmware-tools-distrib/
./vmware-install.pl -d
Danach unter Linux den Befehl eject ausführen oder unter Windows auswerfen lassen, damit das Image sauber entfernt wird!!!
Ausgabe
Die folgende Ausgabe zeigt den Aufruf des letzten Kommandos der Installation:
root@debian-6:~/vmware-tools-distrib# ./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 8.6.0 build-425873 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 [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-4.3". The path "/usr/bin/gcc-4.3" 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/2.6.32-5-amd64/build/include". The path "/lib/modules/2.6.32-5-amd64/build/include" appears to be a valid path to the 2.6.32-5-amd64 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/2.6.32-5-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-headers-2.6.32-5-amd64' CC [M] /tmp/vmware-root/modules/vmci-only/vmciDatagram.o CC [M] /tmp/vmware-root/modules/vmci-only/vmci_drv.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciEvent.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciGuestDs.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciGuestKernelIf.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciKernelIf.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciNotifications.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciProcess.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciQPair.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciQueuePair.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciUtil.o CC [M] /tmp/vmware-root/modules/vmci-only/kernelStubsLinux.o LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-5-amd64' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only' cp -f vmci.ko ./../vmci.o make: Leaving directory `/tmp/vmware-root/modules/vmci-only' Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmci-only' make -C /lib/modules/2.6.32-5-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-headers-2.6.32-5-amd64' CC [M] /tmp/vmware-root/modules/vmci-only/vmciDatagram.o CC [M] /tmp/vmware-root/modules/vmci-only/vmci_drv.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciEvent.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciGuestDs.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciGuestKernelIf.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciKernelIf.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciNotifications.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciProcess.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciQPair.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciQueuePair.o CC [M] /tmp/vmware-root/modules/vmci-only/vmciUtil.o CC [M] /tmp/vmware-root/modules/vmci-only/kernelStubsLinux.o LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-5-amd64' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only' cp -f vmci.ko ./../vmci.o make: Leaving directory `/tmp/vmware-root/modules/vmci-only' Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vsock-only' make -C /lib/modules/2.6.32-5-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-headers-2.6.32-5-amd64' CC [M] /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/notify.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/notifyQState.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/stats.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/util.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.o CC [M] /tmp/vmware-root/modules/vsock-only/driverLog.o LD [M] /tmp/vmware-root/modules/vsock-only/vsock.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vsock-only/vsock.mod.o LD [M] /tmp/vmware-root/modules/vsock-only/vsock.ko make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-5-amd64' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vsock-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vsock-only' cp -f vsock.ko ./../vsock.o make: Leaving directory `/tmp/vmware-root/modules/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. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmmemctl-only' make -C /lib/modules/2.6.32-5-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-headers-2.6.32-5-amd64' CC [M] /tmp/vmware-root/modules/vmmemctl-only/backdoorGcc64.o CC [M] /tmp/vmware-root/modules/vmmemctl-only/os.o CC [M] /tmp/vmware-root/modules/vmmemctl-only/vmballoon.o LD [M] /tmp/vmware-root/modules/vmmemctl-only/vmmemctl.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vmmemctl-only/vmmemctl.mod.o LD [M] /tmp/vmware-root/modules/vmmemctl-only/vmmemctl.ko make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-5-amd64' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vmmemctl-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vmmemctl-only' cp -f vmmemctl.ko ./../vmmemctl.o make: Leaving directory `/tmp/vmware-root/modules/vmmemctl-only' 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/vmware-root/modules/vmxnet-only' make -C /lib/modules/2.6.32-5-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-headers-2.6.32-5-amd64' CC [M] /tmp/vmware-root/modules/vmxnet-only/vmxnet.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vmxnet-only/vmxnet.mod.o LD [M] /tmp/vmware-root/modules/vmxnet-only/vmxnet.ko make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-5-amd64' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vmxnet-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vmxnet-only' cp -f vmxnet.ko ./../vmxnet.o make: Leaving directory `/tmp/vmware-root/modules/vmxnet-only' Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmblock-only' make -C /lib/modules/2.6.32-5-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-headers-2.6.32-5-amd64' 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 LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.o Building modules, stage 2. MODPOST 1 modules 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-2.6.32-5-amd64' 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' No X install found. Creating a new initrd boot image for the kernel. update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64 Checking acpi hot plug done Starting VMware Tools services in the virtual machine: Switching to guest configuration: done Guest memory manager: done VM communication interface: done VM communication interface socket family: done File system sync driver: done Guest operating system daemon: done The configuration of VMware Tools 8.6.0 build-425873 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 Found VMware Tools CDROM mounted at /mnt. Ejecting device /dev/sr0 ... root@debian-6:~/vmware-tools-distrib#
Einzelnachweise
- ↑ VMware Operating System Specific Packages (OSPs) (vmware.com) Supported guest operating systems: Community ENTerprise Operating System (CentOS) 4.0 and higher, Red Hat Enterprise Linux 3.0 and higher, SUSE Linux Enterprise Server 9 and higher, SUSE Linux Enterprise Desktop 10 and higher, Ubuntu Linux 8.04 and higher
Autor: Werner Fischer Werner Fischer arbeitet im Product Management Team von Thomas-Krenn. Er evaluiert dabei neueste Technologien und teilt sein Wissen in Fachartikeln, bei Konferenzen und im Thomas-Krenn Wiki. Bereits 2005 - ein Jahr nach seinem Abschluss des Studiums zu Computer- und Mediensicherheit an der FH Hagenberg - heuerte er beim bayerischen Server-Hersteller an. Als Öffi-Fan nutzt er gerne Bus & Bahn und genießt seinen morgendlichen Spaziergang ins Büro.
|