Linux Integration Services V3.3 For Hyper-V

Version 3.3 of the Linux integration components was just released with support for Windows 8 and Windows Server 2012.

It supports the following versions of Hyper-V:

  • Windows Server 2008 Standard, Windows Server 2008 Enterprise, and Windows Server
  • 2008 Datacenter
  • Microsoft® Hyper-V Server 2008
  • Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, and Windows
  • Server 2008 R2 Datacenter
  • Microsoft Hyper-V Server 2008 R2
  • Windows 8 Release Preview
  • Windows Server 2012

See those last two?  Windows 8 and Windows Server 2012 are supported.

The supported guest OS’s are:

  • Red Hat Enterprise Linux 6.0-6.2 x86 and x64 (Up to 4 vCPU)
  • CentOS 6.0-6.2 x86 and x64 (Up to 4 vCPU)
  • Red Hat Enterprise Linux 6.0-6.2 x86 and x64 (Up to 32 vCPU when used on a Windows 8 Release Preview or Windows Server 2012 host)
  • CentOS 6.0-6.2 x86 and x64 (Up to 32 vCPU when used on a Windows 8 Release Preview or Windows Server 2012 host)

RHEL 6.2 and CentOS 6.2 were added to the list in v3.3. SLES and RHEL 5.x use version 2.1 of the Linux Integration Services.

Notice that RHEL and Centos support up to 32 virtual CPUs on Windows Server 2012 or Windows 8???  Nice scalable Linux workloads on Hyper-V Smile  OK let’s talk turkey.

Once you start adding lots of vCPUs to Linux, you have a few concerns:

  • Bear in mind that I’m a Linux noob and forgive me for lack of details, but Linux has issues where it needs some work to have more than 8 vCPUs in a VM.  One fix is to use Linux Kernel 3.4 or later.
  • With lots of vCPUs you need to handle NUMA nodes, and your Linux guest will be NUMA hardware aware on WS2012 with Linux Kernel 3.4 or later.

Thanks to the folks in MSFT for the quick updates!

10 thoughts on “Linux Integration Services V3.3 For Hyper-V”

  1. Great! Now, does anyone if it is possible to upgrade the v3.1 Hyper-V Integration Components that come with Ubuntu 12.04 to v3.3? And if so, what is the easiest way to do so?

      1. Thanks. However, in the Hyper-V Manager in Server 2012 RC, for the running Ubuntu 12.04 Server VM, under the Networking tab, it shows “Status: Degraded (Integration services upgrade required). Also, you need to upgrade the IC to make use of more virtual CPUs, etc. So it seems that being able to upgrade would be useful. Do you know if that is possible, given that Ubuntu won’t run the RPM package provided on the ISO?

      2. I asked Mike Sterling (‏@mikester01), Virtualization Program Manager at Microsoft. He tweeted “@davidtrounce No need. Drivers in Ubuntu 12.04 are the same functionally as the 3.3 release.”

        But this doesn’t answer why under the Networking tab, it shows “Status: Degraded (Integration services upgrade required).

        1. I’ve verified this in my WS2012 RC lab, and I’m chasing it up. I’ll update if I have any news.

  2. On CentOS 6.3 you have to manually run installation of Integration Services because of dependecy error, but then it works. First install kmod_microsoft_hyper_v.rpm, then microsoft_hyper_v_whichever_version_you_require.rpm.
    rpm -Uvh –nodeps kmod-microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm
    rpm -Uvh –nodeps microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm

    Courtesy of DuaneBV at

    1. Hi Mike,
      It’s more a dependency on the Linux Integration Services, which don’t have Dynamic Memory functionality.
      – Aidan.

  3. Hi,

    RHEL 5.9 has built in support for Hyper-V. However when I check which version here is what I het :

    /sbin/modinfo hv_vmbus
    filename: /lib/modules/2.6.18-348.el5/kernel/drivers/hv/hv_vmbus.ko
    version: 3.1
    license: GPL
    srcversion: 10368D768C4FEEA9FB4A5E9
    vermagic: 2.6.18-348.el5 SMP mod_unload gcc-4.1
    module_sig: 883f35050b6c87d1fe58725e3e141a6112ec4f0a0c5d626d4d0572396d5814e2e127780e69c76b00a0916dc9c01b6138d0aad4139db1fee9e7b459b7

    which seems to indicate that it is not the latest 3.4 version. If I mount the 3.4 ISO I don’t have a RHEL59 folder.

    I’m trying to update the drivers as I have a disinct lag in pings :

    64 bytes from icmp_seq=147 ttl=63 time=1.37 ms
    64 bytes from icmp_seq=148 ttl=63 time=1.41 ms
    64 bytes from icmp_seq=149 ttl=63 time=1.42 ms
    64 bytes from icmp_seq=150 ttl=63 time=4204 ms
    64 bytes from icmp_seq=151 ttl=63 time=3205 ms
    64 bytes from icmp_seq=152 ttl=63 time=2205 ms
    64 bytes from icmp_seq=153 ttl=63 time=1205 ms
    64 bytes from icmp_seq=154 ttl=63 time=205 ms
    64 bytes from icmp_seq=155 ttl=63 time=1.46 ms
    64 bytes from icmp_seq=156 ttl=63 time=31.8 ms
    64 bytes from icmp_seq=157 ttl=63 time=4187 ms
    64 bytes from icmp_seq=158 ttl=63 time=3188 ms
    64 bytes from icmp_seq=159 ttl=63 time=2188 ms
    64 bytes from icmp_seq=160 ttl=63 time=1189 ms
    64 bytes from icmp_seq=161 ttl=63 time=189 ms

    If you have any advice …

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.