Understanding and Installing VMware Tools

Revision as of 19:06, 2 October 2008 by Neil (Talk | contribs) (VMware Tools Service)

Revision as of 19:06, 2 October 2008 by Neil (Talk | contribs) (VMware Tools Service)

A key area where VMware Server differs from many other virtualization solutions is the ability to install tools (known as VMware Tools) onto the guest operating system. VMware Tools are available for Windows, Linux, FreeBSD and Netware guest operating systems and are designed to both improve the functionality of the guest within the virtual machine environment, and to enhance interaction between the guest and the host.

An Overview of VMware Tools

The VMware Tools package comprises four categories of utilities, each of which performs one or more specific purposes:


VMware Device Drivers

VMware Server presents the physical host hardware to the guest operating system as virtual devices. For example, whilst the host computer may have an Intel Gigabit Ethernet Adapter installed, the virtual network adapters presented to a 32-bit guest operating system appear as AMD PCnet‐PCI II devices. In order to ensure optimal performance of the guest in relation to these virtual devices, VMware Tools includes device drivers for each device category. These device drivers are so important, in fact, that without VMware Tools installed, the guest operating system may be unable to establish a network connection (currently the case with Windows Server 2008) because it lacks a built-in driver for the AMD network adapter, or drive the VMware Remote Console at anything above a rudimentary screen resolution. Installation of VMware Tools avoids these and other driver compatibility problems.

VMware Tools Service

The VMware Tools Service is a process which runs in the background of the guest operating system performing a multitude of different functions. This process is named VMwareService.exe on Windows guests and vmware-guestd on Linux and UNIX based operating systems.

One of the most important, yet least visible, functions of the VMware Tools Service is to send regular heartbeat messages VMware Server so that it can detect (via the lack of heartbeats) when a particular virtual machine, or its respective guest operating system, have failed.

Another responsibility of VMware Tools Service involves the handling of communication between the guest and host operating systems. It is not too unrealistic to make the statement that none of today's popular operating systems have been written specifically to run within a VMware Server virtual machine. As such, none of these guest operating systems are designed to accept and respond to any form of communication from the VMware Server environment. Whilst this isn't generally problem, an issue arises when we consider that the VI Web Access management interface provides the ability to power off, restart and suspend guest operating systems at the press of a tool bar button or menu option, avoiding the need to open a VMware Remote Console session, log into the guest operating system and perform an orderly shutdown or reboot. Since there is no mechanism built into most operating systems that would allow VMware Server to request a shutdown or restart, this functionality is instead provided by the VMware Tools Service. When a user, for example, restarts a virtual machine from the VI Web Access management interface, VMware Server notifies the VMware Tools Service running on the guest operating system which in turn executes the commands necessary to perform a clean shutdown or restart.