Integration Services


Updated: August 4, 2014

Applies To: Windows Server 2012 R2, Windows Server 2012

Hyper-V integration services, are a bundled set of software which, when installed in the virtual machine improves integration between the host server and the virtual machine. Integration services come pre-installed in most supported guest operating systems.

The following topics list the guest operating systems supported in virtual machines running in Hyper-V on Windows Server 2012 and Windows Server 2012 R2 for use as guest operating systems:


After the integration services software package has been installed in the virtual machine, the following integration services can be presented to the virtual machine. The operating system running in the virtual machine must support the selected services.

The following is the list of the integration services that can be configure in the Integration Services settings page for each virtual machine. By default all of the services are enabled except for Guest services.

Service name

Server settings

Guest operating system

Default virtual machine setting

Supported on Hyper-V running on Windows Server version

Windows service name

Linux driver / daemon name 

Operating system shutdown


Windows Server 2012 and Windows Server 2012 R2

Hyper-V Guest Shutdown Service


Time synchronization


Windows Server 2012 and Windows Server 2012 R2

Hyper-V Time Synchronization Service


Data Exchange


Windows Server 2012 and Windows Server 2012 R2

Hyper-V Data Exchange Service

hv_utils and hv_kvp_daemon



Windows Server 2012 and Windows Server 2012 R2

Hyper-V Heartbeat Service


Backup (volume snapshot)


Windows Server 2012 and Windows Server 2012 R2

Hyper-V Volume Shadow Copy Requestor

hv_utils and hv_vss_daemon

Guest services

Not enabled

Windows Server 2012 R2

Hyper-V Guest Services Interface

hv_utils and hv_fcopy_daemon


On Linux virtual machines you can check to see if the integration services driver and daemons are running by running the following commands.

  • Run the following command in your Linux guest operating system to see if the hv_utils driver is loaded.

    lsmod|grep hv_utils
  • Run the following command in your Linux guest operating system to see if the required daemons are running.

    ps –eaf|grep hv

The operating system shutdown service provides a mechanism to shut down the operating system of a virtual machine from the management interfaces on the host or management computer. This allows the Hyper-V administrator the ability to initiate an orderly shutdown of the virtual machines without having to log into the virtual machine. The virtual machine will attempt to close open processes and write to disk any data in memory before shutting down the virtual machine, in the same way if the administrator had selected Shutdown from within the virtual machine.

You can shutdown virtual machines from the Hyper-V Manager console or via the Stop-VM PowerShell cmdlet. For more information about Stop-VM cmdlet, see Stop-VM.

The time synchronization service provides the ability to synchronize your virtual machines’ time with the time from the host. Just as time is critical to physical servers it is critical to virtual machines.

For additional information about time synchronization and in what scenarios you should disable the service, see Time Synchronization.

The data exchange service, also known as key-value pairs (KVP), allows for the sharing of information between the host and virtual machine. General information about the virtual machine and host is automatically generated and stored in the registry for virtual machines running Windows and in files for virtual machines running Linux. Additionally there is a registry key and file where information can be created manually that can be shared between the host and the virtual machine. For example a service running in a virtual machine could write to this location when a specific event has occurred that requires the Hyper-V administrator to perform a specific action.

Access to the data from the host is via WMI scripts only.

For additional information about data exchange, see Data Exchange: Using key-value pairs to share information between the host and guest on Hyper-V

The heartbeat service monitors the state of running virtual machines by reporting a heartbeat at regular intervals. This service helps you identify running virtual machines that might have stopped responding. You can check the heartbeat status of a virtual machine on the Summary tab of the Virtual Machines details page or you can use the Get-VMIntegrationSerivce cmdlet. For additional information about the Get-VMIntegrationService cmdlet, see Get-VMIntegrationService.

The backup service enables consistent backup of the virtual machines from backup software running on the host. The backup service allows for the virtual machine to be backed up while it is running without any interruption to the virtual machine or the services running in the virtual machine.

For more information about backing up your virtual machines, see Considerations for backing up and restoring virtual machines.

The guest service allows the Hyper-V administrator to copy files to a running virtual machine without using a network connection. Beforehand the only way to copy files to the virtual machine was for both the virtual machine and the host be connected to same network and then either use file services to copy file or to create a remote desktop session to the virtual machine and copy files via RDS session.


The Hyper-V Guest Service Interface service enters a running state when the Guest services service is selected on the Integration Services property page of the virtual machine.

To disable this feature in a virtual machine running Windows, set the Hyper-V Guest Service Interface service startup type to Disabled inside the virtual machine.

To disable this feature in a virtual machine running Linux, stop and disable the hv_fcopy_daemon daemon. Consult your Linux distribution’s documentation for the steps to stop or disable a daemon process.

To copy a file to a virtual machine you need to use the Copy-VMFile PowerShell cmdlet. For additional information about the Copy-VMFile Windows PowerShell cmdlet, see Copy-VMFile.