VmWare

Aus Doku-Wiki
Zur Navigation springenZur Suche springen

VmWare-Tools

Installation

TAR-File am Beispiel von Debian

Benötigte Debian-Packete:
(Achtung: Kernel-Header des installierten Kernels verwenden)

Debian Sarge

apt-get install make binutils cpp cpp-3.3 gcc-3.3 autoconf automake gcc kernel-headers-2.6-386
mkdir -p /usr/src/linux
ln -s /usr/src/kernel-headers-2.6.8-2/include /usr/src/linux/include

Debian Etch

 apt-get install make binutils cpp cpp-3.3 gcc-3.3 autoconf automake gcc linux-headers-2.6.18-4-686 build-essential psmisc
 ln -s /usr/src/linux-headers-2.6.18-4-686 /usr/src/linux

Nun in der VMware-console bzw. im Menue von VMware-Workstation auf VM -> Install VMware Tools... klicken.
Jetz wird dem Gast-System vom Host die Installationspackete an der CD/DVD Schnittstelle bereit gestellt.
Diese können mittels Mount-Befehl ins System eingebunden werden:

mount /dev/cdrom /mnt 

und dann folgende Befehle auf der Konsole im Linux-System ausführen:

mkdir /mnt/vmware

mount /dev/cdrom /mnt
cd /tmp/

tar xvzf /mnt/VMwareTools*.tar.gz

cd vmware-tools-distrib/

./vmware-install.pl
/etc/init.d/networking stop

Etch

modprobe vmxnet

Wenn dieser Test positiv verläuft, kann man das Netwürking und die VMWare-Tools starten
Wenn nicht, dann weiter wie unten beschrieben.

/etc/init.d/networking start
/etc/init.d/vmwaretools start
rmmod pcnet32

rmmod vmxnet

depmod -a

modprobe vmxnet

/etc/init.d/networking start

Debian Lenny

aptitude update
aptitude install build-essential module-assistant autoconf automake gcc-4.1
aptitude install linux-headers-`uname -r` 
VMware-Tools entpacken
cd /usr/local/src
tar xvzf VMwareTools-3.5.0-xxxx.tar.gz
Fehler in VMware-Tools bei Kernel 2.6.26 >

Der Fehler tritt bei mir mit folgenden VMware-Tools auf:

VMwareTools-3.5.0-130756.tar.gz

Der Kernel ab 2.6.26 kennt den Aufruf get_info nicht mehr. Deshalb kann das Module vmmemctl nicht kommpiliert werden.
Deshalb ist folgende Änderung am Source-Code nötig:

Entpacken der folgender Quellen:
       cd vmware-tools-distrib/lib/modules/source/
       tar xvf vmmemctl.tar
       vi vmmemctl-only/os.c
Angepasster Code:
       #if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,26)
         global_proc_entry = create_proc_entry("vmmemctl", S_IFREG | S_IRUGO, NULL);
               if (global_proc_entry != NULL) {
               ## Alter Code
               ##      global_proc_entry->get_info = os_proc_read;
               ## Neuer Code
                       global_proc_entry->read_proc = os_proc_read;
               )


Quellen wieder packen
       tar cvf vmmemctl.tar vmmemctl-only

Danach follgt dann die Installation

cd vmware-tools-distrib/
export CC=/usr/bin/gcc-4.1
./vmware-install.pl

Dokumentation

VMWare Online

Problembehebung

CPU Takt-Erkennung

To work around this problem, specify the correct maximum CPU speed in your global configuration file:

Find the speed of your host's CPU. For example, in Windows XP, right click My Computer, then
choose Properties. This path may be different, depending on the version of Windows you use.

Look for config.ini in one of the following locations:

C:\Documents and Settings\All Users\Application Data\VMware\VMware Workstation\config.ini

C:\Documents and Settings\All Users\Application Data\VMware\VMware GSX Server\config.ini

C:\Documents and Settings\All Users\Application Data\VMware\VMware Server\config.ini

C:\ProgramData\VMware\VMware Workstation
(on a Windows Vista host running Workstation 6.0)


Note: If the file does not exist, create it as a plain text file in the appropriate location as described above, then edit it as follows. For more detail, see "Creating and Editing config.ini on Windows Hosts" at http://kb.vmware.com/kb/1754.

Edit config.ini, adding the lines described below.

The example presented here assumes that the host computer has a maximum speed of 1700MHz. The
first line is the most important one. It should be your host computer's maximum speed in
KHz—that is, its speed in MHz times 1000, or its speed in GHz times 1000000.

host.cpukHz = "1700000"
host.noTSC = "TRUE"
ptsc.noTSC = "TRUE"

The second and third lines enable a mechanism that tries to keep the guest clock accurate even when the time stamp counter (TSC) is slow.
Note: On Windows, you can use Notepad, but be careful when you save the file that Notepad does not add an extra .txt extension to the filename. You can do that by selecting All files instead of Text files in the Save dialog box.

In addition, check the VMware Tools control panel in the guest operating system. On the Options tab, ensure that Time synchronization between the virtual machine and the host operating system is selected.