Hyper v integration services iso

Hyper-V Integration Services enhance virtual machine performance and provide convenience features by leveraging two-way communication with the Hyper-V host. Many of these services are conveniences, such as guest file copy, while others are important to the virtual machine’s functionality, such as synthetic device drivers. This set of services and drivers are sometimes referred to as "integration components". You can control whether or not individual convenience services operate for any given virtual machine. The driver components are not intended to be serviced manually.

For details about each integration service, see Hyper-V Integration Services.

Each service you want to use must be enabled in both the host and guest in order to function. All integration services except "Hyper-V Guest Service Interface" are on by default on Windows guest operating systems. The services can be turned on and off individually. The next sections show you how.

Turn an integration service on or off using Hyper-V Manager

From the center pane, right-click the virtual machine and click Settings.

From the left pane of the Settings window, under Management, click Integration Services.

The Integration Services pane lists all integration services available on the Hyper-V host, and whether the host has enabled the virtual machine to use them.

Turn an integration service on or off using PowerShell

The following examples demonstrate turning the guest file copy integration service on and off for a virtual machine named "demovm".

Get a list of running integration services:

The output should look like this:

Turn on Guest Service Interface:

Verify that Guest Service Interface is enabled:

Turn off Guest Service Interface:

Checking the guest’s integration services version

Some features may not work correctly or at all if the guest’s integration services are not current. To get the version information for a Windows, log on to the guest operating system, open a command prompt, and run this command:

Earlier guest operating systems will not have all available services. For example, Windows Server 2008 R2 guests cannot have the "Hyper-V Guest Service Interface".

Start and stop an integration service from a Windows Guest

In order for an integration service to be fully functional, its corresponding service must be running within the guest in addition to being enabled on the host. In Windows guests, each integration service is listed as a standard Windows service. You can use the Services applet in Control Panel or PowerShell to stop and start these services.

Stopping an integration service may severely affect the host’s ability to manage your virtual machine. To work correctly, each integration service you want to use must be enabled on both the host and guest. As a best practice, you should only control integration services from Hyper-V using the instructions above. The matching service in the guest operating system will stop or start automatically when you change its status in Hyper-V. If you start a service in the guest operating system but it is disabled in Hyper-V, the service will stop. If you stop a service in the guest operating system that is enabled in Hyper-V, Hyper-V will eventually start it again. If you disable the service in the guest, Hyper-V will be unable to start it.

Use Windows Services to start or stop an integration service within a Windows guest

Open Services manager by running services.msc as an Administrator or by double-clicking the Services icon in Control Panel.

Find the services that start with "Hyper-V".

Right-click the service you want start or stop. Click the desired action.

Use Windows PowerShell to start or stop an integration service within a Windows guest

To get a list of integration services, run:

The output should look similar to this:

Run either Start-Service or Stop-Service. For example, to turn off Windows PowerShell Direct, run:

Start and stop an integration service from a Linux guest

Linux integration services are generally provided through the Linux kernel. The Linux integration services driver is named hv_utils.

To find out if hv_utils is loaded, use this command:

Читайте также:  Dr web код ошибки 914 при удалении

The output should look similar to this:

To find out if the required daemons are running, use this command.

The output should look similar to this:

To see what daemons are available, run:

The output should look similar to this:

Integration service daemons that might be listed include the following. If any are missing, they might not be supported on your system or they might not be installed. Find details, see Supported Linux and FreeBSD virtual machines for Hyper-V on Windows.

  • hv_vss_daemon: This daemon is required to create live Linux virtual machine backups.
  • hv_kvp_daemon: This daemon allows setting and querying intrinsic and extrinsic key value pairs.
  • hv_fcopy_daemon: This daemon implements a file copying service between the host and guest.

Examples

These examples demonstrate stopping and starting the KVP daemon, named hv_kvp_daemon .

Use the process ID (PID) to stop the daemon’s process. To find the PID, look at the second column of the output, or use pidof . Hyper-V daemons run as root, so you’ll need root permissions.

To verify that all hv_kvp_daemon process are gone, run:

To start the daemon again, run the daemon as root:

To verify that the hv_kvp_daemon process is listed with a new process ID, run:

Keep integration services up to date

We recommend that you keep integration services up to date to get the best performance and most recent features for your virtual machines. This happens for most Windows guests by default if they are set up to get important updates from Windows Update. Linux guests using current kernels will receive the latest integration components when you update the kernel.

For virtual machines running on Windows 10 hosts:

The image file vmguest.iso isn’t included with Hyper-V on Windows 10 because it’s no longer needed.

Guest Update mechanism Notes
Windows 10 Windows Update
Windows 8.1 Windows Update
Windows 8 Windows Update Requires the Data Exchange integration service.*
Windows 7 Windows Update Requires the Data Exchange integration service.*
Windows Vista (SP 2) Windows Update Requires the Data Exchange integration service.*
Windows Server 2016 Windows Update
Windows Server, Semi-Annual Channel Windows Update
Windows Server 2012 R2 Windows Update
Windows Server 2012 Windows Update Requires the Data Exchange integration service.*
Windows Server 2008 R2 (SP 1) Windows Update Requires the Data Exchange integration service.*
Windows Server 2008 (SP 2) Windows Update Extended support only in Windows Server 2016 (read more).
Windows Home Server 2011 Windows Update Will not be supported in Windows Server 2016 (read more).
Windows Small Business Server 2011 Windows Update Not under mainstream support (read more).
Linux guests package manager Integration services for Linux are built into the distro but there may be optional updates available. ********

* If the Data Exchange integration service can’t be enabled, the integration services for these guests are available from the Download Center as a cabinet (cab) file. Instructions for applying a cab are available in this blog post.

For virtual machines running on Windows 8.1 hosts:

Guest Update mechanism Notes
Windows 10 Windows Update
Windows 8.1 Windows Update
Windows 8 Integration Services disk See instructions, below.
Windows 7 Integration Services disk See instructions, below.
Windows Vista (SP 2) Integration Services disk See instructions, below.
Windows XP (SP 2, SP 3) Integration Services disk See instructions, below.
Windows Server 2016 Windows Update
Windows Server, Semi-Annual Channel Windows Update
Windows Server 2012 R2 Windows Update
Windows Server 2012 Integration Services disk See instructions, below.
Windows Server 2008 R2 Integration Services disk See instructions, below.
Windows Server 2008 (SP 2) Integration Services disk See instructions, below.
Windows Home Server 2011 Integration Services disk See instructions, below.
Windows Small Business Server 2011 Integration Services disk See instructions, below.
Windows Server 2003 R2 (SP 2) Integration Services disk See instructions, below.
Windows Server 2003 (SP 2) Integration Services disk See instructions, below.
Linux guests package manager Integration services for Linux are built into the distro but there may be optional updates available. **

For virtual machines running on Windows 8 hosts:

Guest Update mechanism Notes
Windows 8.1 Windows Update
Windows 8 Integration Services disk See instructions, below.
Windows 7 Integration Services disk See instructions, below.
Windows Vista (SP 2) Integration Services disk See instructions, below.
Windows XP (SP 2, SP 3) Integration Services disk See instructions, below.
Windows Server 2012 R2 Windows Update
Windows Server 2012 Integration Services disk See instructions, below.
Windows Server 2008 R2 Integration Services disk See instructions, below.
Windows Server 2008 (SP 2) Integration Services disk See instructions, below.
Windows Home Server 2011 Integration Services disk See instructions, below.
Windows Small Business Server 2011 Integration Services disk See instructions, below.
Windows Server 2003 R2 (SP 2) Integration Services disk See instructions, below.
Windows Server 2003 (SP 2) Integration Services disk See instructions, below.
Linux guests package manager Integration services for Linux are built into the distro but there may be optional updates available. **
Читайте также:  Забыл пароль на мейзу как сбросить настройки

Install or update integration services

For hosts earlier than Windows Server 2016 and Windows 10, you’ll need to manuallyВ installВ or update the integration services in the guest operating systems.

Open Hyper-V Manager. From the Tools menu of Server Manager, click Hyper-V Manager.

Connect to the virtual machine. Right-click the virtual machine and click Connect.

From the Action menu of Virtual Machine Connection, click Insert Integration Services Setup Disk. This action loads the setup disk in the virtual DVD drive. Depending on the guest operating system, you might need to start the installation manually.

After the installation finishes, all integration services are available for use.

These steps can’t be automated or done within a Windows PowerShell session for online virtual machines. You can apply them to offline VHDX images; see this blog post.

I’m frequently receiving questions about what’s wrong with Windows Server 2016 and how to manage Hyper-V IS. I’d like to discuss it in a FAQ manner. If your question is not answered, just feel free to leave a comment

Where is the integration services setup disk (VmGuest.iso)?

All of us remember times when we had to insert ISO which was available on Hyper-V host , run it on each VMs and check it’s version from time to time for keeping them up-to-date (yes, vmguest.iso was updated via Windows Update).

The process of Hyper-V IS upgrading has been changed since Windows Server 2016. Now VMs get IS updates directly from Windows Update (WU). ISO is not included and it’s not needed anymore.

It’s completely true if you have new OS inside VMs (Windows 2012 R2/Windows 8.1 and later). Hyper-V IS automatically get updates from WU in these OSes. No actions required.

We have another picture for older OSes (Windows Server 2012/Windows 8 and older). For such OSes, you need to verify that Data Exchange Service (DES) is turned on and running.

DES provides shared registry values (HostSystemOSMajor and HostSystemOSMinor under the hive HKLMSOFTWAREMicrosoftVirtual MachineGuestParameters) between host and VMs for determining IS applicability. These values should be existed in VM in order to get IS updates from WU. If DES has never been enabled on VMs – IS won’t be provided.

Hack: you can edit/add these parameters and set values manually (of course, it’s unsupported)

Example of outdated IS in VM with WS2012R2 on WS2016 host (DES provided values from VM, compared them with host’s and they are not the same):

Unsupported Windows Server 2003? Integration services setup disk is required. Can be copied from WS2012R2 (download link is below). Better option: plan migration to newer OS

How to install IS manually?

Use this KB if DES can’t be enabled or WU is unavailable:

Update: IS was updated by the June’s month rollup to version 6.3.9600.18692

To install IS (CAB-file) use PowerShell:

If you want to do offline VM servicing : read guide from Sarah Cooley

TIP: IS with later version is available from uploaded VMGuest.iso below (use it to simplify overall process)

Where can I find ISO if I haven’t got Windows Server 2012 R2 installed?

I’ve uploaded Hyper-V Integrations Services ISO for you. It was taken from Windows Server 2012 R2 (up-to-date, 02/20/17 . IS version: 6.3.9600.18398). You can use this ISO to install Integration Services in “prehistoric” guest OSes (but again..migration to newer OS is better option for such VMs) on Windows Server 2016 or with hosts running on Windows 2012 R2/Windows 8.0/8.1 Download link for VMGuest.ISO

Update: here is a link for the latest Hyper-V Integration Services (version 6.3.9600.18692), taken from Server 2012 R2 + November updates: VMGuest.ISO (November, 2017)

Update: if you are running 2008 R2/2012R2 guest VMs on Windows 10/Server 2012R2/2016 hosts, there is a special update available at KB4072650 (6.3.9600.18907)

I’m querying Integration Services version from PowerShell but it shows me 0 for all VMs. What’s wrong?

I’ve provided example of outdated IS in a VM SQL01 above. Cluster validation report generates a warning. PowerShell shows 0 in IntegrationServicesVersion

By default, PowerShell loads Hyper-V module with version 2. I tried to remove that module, import one with 1.1 version and query again IS versions. In that case, I received actual IS versions and “Update required” in IntegrationServicesState. It seems like something wrong with Hyper-V 2.0 module. Waiting for official fixes or confirmations.

Update: this behavior is normal. VM support is based on the having critical updates and reporting IS version is no longer needed.

Службы интеграции Hyper-V отвечают за эффективное взаимодействие виртуальных машин и гипервизора посредством установки дополнительных сервисов в гостевую ОС. Для понимания степени важности, предлагаем кратко рассмотреть каждую из них, а также ключевые изменения в Windows Server 2016.

Читайте также:  Canon ir1435i драйвер для сканера 64 bit

По умолчанию, не все службы включены. Guest Services, как правило, включается по мере необходимости. Остальные отвечают за более важную функциональность.

Operating System Shutdown – включает возможность завершения работы ВМ (аналогия привычного shutdown из гостевой ОС), используя Hyper-V Manager или PowerShell/WMI.

Time Synchronization – отвечает за предоставление синхронизации времени между хостом и виртуальной машины.

Data Exchange или KVP (key-value pairs) – предоставляет функционал обмена значениями формата key + value типа strings, расположенных в ветке реестра HKLMSoftwareMicrosoftVirtual Machine или в файлах kvp_pool_x (для ОС Linux) через VMbus. На стороне хоста WMI-запросами занимается VMMS.exe (функции AddKvpItems, ModifyKvpItems и RemoveKvpItems). В свою очередь, на ВМ должна быть запущена служба Hyper-V Data Exchange Service.

HKLMSoftwareMicrosoftVirtual MachineAuto содержит информацию о ВМ, которая генерируется во время первого запуска службы Hyper-V Data Exchange Service.

HKLMSoftwareMicrosoftVirtual MachineExternal содержит данные, отправленные пользователем со стороны хоста. По умолчанию данный раздел пуст и не содержит никаких объектов KVP.

HKLMSoftwareMicrosoftVirtual MachineGuest презентует данные, которые необходимо отправить узлу виртуализации из данной ВМ. К примеру, сведения о AVMA-активации или кастомные параметры, которые вашему приложению необходимо передать на уровень выше (да, в целом, мы можем добавлять собственные пары key + value и работать с ними через KVP и WMI без предоставления credentials. Новая аналогия – PowerShell Direct, но со своими плюсами и минусами).

HKLMSoftwareMicrosoftVirtual MachineGuestParameters содержит информацию об узле виртуализации (наименование, FQDN, VMID и так далее). Запомните эту ветку – она далее нам пригодится.

Heartbeat отвечает за проверку состояния ВМ через hearbeats, выполняемые в определенный интервал, между ВМ и узлом.

Backup (volume snapshot) включает возможность использования задач резервного копирования ВМ на уровне хоста для обеспечения консистентности резервных копий.

Guest Services обеспечивают передачу файлов в ВМ через WMI или PowerShell (Copy-VMFile). По умолчанию, не включена. Более подробно можно почитать здесь.

Что нужно учитывать в Windows Server 2016?

Все помнят, что для установки служб интеграции приходилось монтировать ISO-образ (%systemroot%system32vmguest.iso) через опцию «Insert Integration Services Setup Disk» в консоли ВМ и запускать процесс установки внутри ВМ. Затем проверять версию IS время от времени для её актуализации (vmguest.iso, так же как и узел, тоже обновлялся через Windows Update). Данный процесс существенно поменялся в Windows Server 2016. Опции в консоли теперь нет, как и самого vmguest.iso. Теперь распространением IS на ВМ занимается сам Windows Update. Но есть особенности, которые мы рассмотрим ниже.

Автоматическая доставка IS через Windows Update доступна для новых ОС внутри ВМ (начиная с Windows Server 2012 R2/Windows 8.1 и новее). Дополнительных действий от вас не требуется.

Если гостевые ОС на базе Windows Server 2012/Windows 8 и старше, то требуется наличие рабочей службы Data Exchange Service (рассмотренная выше). DES предоставляет доступ к параметрам /values HostSystemOSMajor и HostSystemOSMinor, располагающимся в ветке HKLMSOFTWAREMicrosoftVirtual MachineGuestParameters, для определения необходимости обновления IS на ВМ. Данные параметры должны присутствовать и иметь значения. В противном случае (к примеру, если DES не включен для ВМ или служба не выполняется), IS не будут предоставляться через WU.

TIP: мы можем вручную создать или изменить данные значения реестра для подачи «фальш»-сигнала, но данное действие официально не поддерживается.

Предположим, что в рамках ВМ выполняется Windows Server 2012 R2, а на хосте – Windows Server 2016. DES получает сведения о ВМ, сверяет значения между имеющимися на узле и полученные от ВМ и они оказываются различными, таким образом IS на ВМ не актуальны и их обновление будет выполнено через WU.

В случае с ОС на базе Linux, как правило, IS идут встроенными. В ряде случаев требуется пакет Linux Integration Services или FreeBSD Integration Services. Получить подробные сведения о требованиях к различным дистрибутивам и функциональности можно из статьи «Supported Linux and FreeBSD virtual machines for Hyper-V on Windows».

Если у Вас всё ещё есть виртуализированный Windows Server 2003, который уже не поддерживается, то, как минимум, рекомендуется устанавливать IS, используя vmguest.iso из Windows Server 2012 R2, к примеру. Надежность и производительность не гарантируется, но 2003-й год был уже 14 лет назад. Конечно, миграция на более новые версии ОС будет предпочтительна в данном случае.

Как установить IS вручную?

Если DES не выполняется или Windows Update недоступен из ВМ, то есть специальный KB для самостоятельной загрузки IS «Hyper-V integration components update for Windows virtual machines that are running on a Windows 10 or Windows Server 2016-based host» (доступная в KB версия IS: 6.3.9600.17903) + IS Update для устранения проблем с Windows Server Guest OSes (IS ver.6.3.9600.18080, применим и для Windows 7/8.1).

IS из KB доступен в виде cab-файла, который можно применить через PowerShell: Add-WindowsPackage -PackagePath

-Online. Если нужно применить обновление IS на выключенной ВМ (offline vm servicing), то рекомендуем обратиться к данному руководству.