Changes

Jump to: navigation, search
m
Text replacement - "<google>BUY_HYPERV</google>" to "<htmlet>hyperv</htmlet>"
In [[An Overview of the Hyper-V Architecture]], the significance of the relationship between the Hyper-V parent partition (in which the host instance of Windows Server 2008 runs) and the child partitions containing the guest operating systems was covered in detail. Given the importance of this relationship, it is clear that anything which enhances the level of communication between parent and child partitions will serve to improve the performance and manageability of the Hyper-V environment. This is where the Hyper-V Integration Services come into play. <htmlet>hyperv</htmlet>
The goal of this chapter of [[Hyper-V Essentials]] is to provide an overview of the Hyper-V Integration Services, provide a list of guest operating systems for which the services are available and, finally, cover the steps involved in installing the services on a guest operating system.
In [[An Overview of the Hyper-V Integration Services are a set Architecture]], the significance of processes that may be installed into supported the relationship between the Hyper-V parent partition (in which the host instance of Windows Server 2008 runs) and the child partitions containing the guest operating systems was covered in detail. Given the importance of this relationship, it is clear that anything that enhances the level of communication between parent and child partitions will serve to improve the performance and usability manageability of that system running within a the Hyper-V virtual machineenvironment. In some respects, This is where the Hyper-V Integration Services are analogous come into play.  The goal of this chapter of [[Hyper-V Essentials]] is to provide an overview of the VMware Tools package used to improve the interaction Hyper-V Integration Services, provide a list of guest operating systems within the VMware virtualization infrastructure. This chapter will cover guest operating systems for which Integration Services the services are availableand, provide an overview of functions performed by the services. Finallyfinally, details of how to install cover the steps involved in installing the services on a supported guest operating systems will be coveredsystem.
== An Overview of Hyper-V Integration Services ==
Hyper-V Integration Services consists of a package of services which, when installed on a Hyper-V guest operating system, improve the performance and manageability of that system running within a Hyper-V virtualization environment. In this section we will take a look at each of the services provided as part of the overall many respects, Hyper-V Integration Services are analogous to the VMware Tools packageused to improve the interaction of guest operating systems within the VMware virtualization infrastructure.
The Hyper-V Integration Services provide a number of performance and usability enhancing features for Hyper-V based guest operating systems. These services are as follows:
* '''Virtual drivers and Hypervisor-aware Kernel''' - Allows the guest operating system to communicate directly with the parent partition over the VMBus when accessing devices and making I/O requests, thereby increasing performance of the guest operating system.
* '''Hyper-V Time Synchronization Service''' - The purpose of this services service is to synchronize the system time between Hyper-V child and parent partitions (for a detailed description of child and parent partitions, read the chapter entitled [[An Overview of the Hyper-V Architecture]]). This synchronization is important to avoid potential time drift between the guest operating systems running in a child partitions and the Hyper-V parent partition.
* '''Hyper-V Heartbeat Service''' - The heartbeat service allows the parent partition to detect when a virtual machine has locked up, crashed or otherwise ceased to function. The parent partition sends heartbeat messages to the guest operating system at regular intervals. It is then the job of the Hyper-V Heartbeat Service installed on the guest operating system to send a response to each of these heartbeat messages. When the parent partition fails to receive responses from the child partition, it assumes that the child's Heartbeat Service, and therefore the guest operating system on which it is running, has encountered problems. The administrative services on the parent partition will subsequently log the event accordingly such that it is brought to the attention of a system administrator for corrective action to be taken.
It is important to note that the Hyper-V Integration Services are not available for all guest operating system types. In addition, for some supported guest operating systems only a subset of the full range of integration services is actually provided.
At present the only Integration Services packages supplied by Microsoft are for members of the Windows family of operating systems. It is anticipated that Microsoft will also release Integration Services for SUSE Enterprise Linux in conjunction with Novelland also Red hat Enterprise Linux. It is also likely that other operating system vendors will eventually develop Integration Services packages for their respective offerings.
The following table lists the platforms for which Hyper-V integration Services are supported, together with details of the individual services provided in each case:
== Installing Hyper-V Integrated Services ==
Before installing Hyper-V integration Services into a guest operating system it is important to understand that some Windows operating systems ship with Integration Services built in. Presently these operating systems are limited to Windows Vista and Windows Server 2008. These two operating systems are able to detect the presence of the Hyper-V hypervisor and activate the Integration Services accordingly. Obviously, any Windows release which pre-dates the release of Hyper-V will be unaware that it is running on a hypervisor.
Despite the above caveat, it is still worth re-installing the Hyper-V Integration Services even on Windows Server 2008 and Windows Vista guests. The reasons for doing so are two-fold. Firstly, integration services bundled with the guest operating system installation media may not be the latest shipping version. Secondly, the version of the Integration Services bundled with the current versions these operating systems do not include the Virtual Machine Connection enhancements outlined earlier in this chapter.
Alternatively, navigate to the device containing the ISO image and double click on it to invoke the setup process. If an earlier version of Hyper-V Integration Services are is detected by the setup process, the option will be provided to install the latest release in place of the old release. Once completed, the guest system will need to be rebooted before the services will be active. The following image shows the successful installation of Hyper-V Integration Services on a Windows XP Professional system:
== Configuring Hyper-V Integrated Services ==
The Hyper-V Integration Services run as background services on the guest operating system and communicate with the parent partition. The method for viewing these running services differs slightly between the various guest operating system types. For example, the to view the services running on a Windows XP system, click on the ''Start'' menu, right click on the ''My Computer'' entry within the menu and select ''Manage'' from the popup menu to launch the ''Computer Management'' console. Within the management console select ''Services and Applications->Services'' to display a list of configured services. Scroll down this list until the ''Hyper-V'' services are visible as illustrated in the following figure:
Use the check boxes to enable or disable services and click on the ''OK'' button to commit the configuration changes. When configuring these services, it is important to keep in mind that the selected service may not be supported on the guest operating system. As such, activating the service within the Hyper-V Manager may have no effect of the performance and behavior of the guest within the Hyper-V environment.
 
 
<htmlet>hyperv</htmlet>

Navigation menu