Linux Integration Services Version 3.1 for Hyper-V – Part 1 – Installation

When installed on a virtual machine that is running a supported Linux operating system, Linux Integration Services for Hyper-V provides the following functionality:

  • Driver support: Linux Integration Services supports the network controller and the IDE and SCSI storage controllers that were developed specifically for Hyper-V.
  • Fastpath Boot Support for Hyper-V: Boot devices now take advantage of the block Virtualization Service Client (VSC) to provide enhanced performance.
  • Timesync: The clock inside the virtual machine will remain synchronized with the clock on the virtualization server with the help of the pluggable time source device.
  • Integrated Shutdown: Virtual machines running Linux can be shut down from either Hyper-V Manager or System Center Virtual Machine Manager by using the “Shut Down” command.
  • Symmetric Multi-Processing (SMP) Support: Supported Linux distributions can use up to 4 virtual processors (VP) per virtual
    machine.

 Note –SMP support is not available for 32-bit Linux guest operating systems running on Windows Server 2008 Hyper-V or Microsoft Hyper-V Server 2008.

  • Heartbeat: Allows the virtualization server to detect whether the virtual machine is running and responsive.
  • KVP (Key Value Pair) Exchange: Information about the running Linux virtual machine can be obtained by using the Key Value
    Pair exchange functionality on the Windows Server 2008 virtualization server.

Supported Guest Operating Systems

This version of Linux Integration Services supports the following guest operating systems and virtual CPU (vCPU) configurations:

  • Red Hat Enterprise Linux 6.0 and 6.1 x86 and x64 (Up to 4 vCPU)
  • CentOS 6.0 x86 and x64 (Up to 4 vCPU)

Other supported operating systems (including SUSE Linux Enterprise Server 10 and Red Hat Enterprise Linux 5) should use the version of
Linux Integration Services available at http://www.microsoft.com/downloads/en/details.aspx?FamilyID=eee39325-898b-4522-9b4cf4b5b9b64551

How to Install Linux Integration Services Version 3.1 on Red Hat Enterprise Linux 6

To install Linux Integration Services Version 3.1:

  1. Open Hyper-V Manager: Click Start, point to Administrative Tools, and then click Hyper-V Manager.
  2. Create a new virtual machine where you will install Linux: In the Actions menu, click New, and then click Virtual Machine.
  3. Specify the Linux installation media:
    Right-click the virtual machine that you created, and then click Settings. In IDE Controller, specify one of the following:
    1. An image file in ISO format that contains the files required for installation
    2. A physical CD/DVD drive that contains the installation media
  4. Turn on the virtual machine: Right-click the virtual machine that you created, and then click Connect.
    1. Begin installing Linux.
    2. When prompted, restart the virtual machine and complete any first-boot configuration tasks.

Note: Unless a legacy network adapter was added during the virtual machine’s initial configuration, the virtual machine will not have any network support.

  1. Log on to the virtual machine.
  2. In Hyper-V Manager, configure LinuxIC v30.ISO (located in the directory where you extracted the downloaded files) as a physical CD/DVD drive on the virtual machine.
  3. As the root user, mount the CD in the virtual machine by issuing the following command at a shell prompt:

# mount /dev/cdrom /media

4. As the root user, run the following command to install the synthetic drivers. A reboot is required after installation.

For 32-bit versions:

 # rpm –ivh /media/x86/kmod-microsoft-hyper-v-rhel6-60.1.i686.rpm

# rpm –ivh /media/x86/microsoft-hyper-v-rhel6-60.1.i686.rpm

# reboot

 For 64-bit versions:

 # rpm –ivh /media/x86_64/kmod-microsoft-hyper-v-rhel6-60.1.x86_64.rpm

# rpm –ivh /media/x86_64/microsoft-hyper-v-rhel6-60.1.x86_64.rpm

# reboot

Verifying Linux Integration Services Version 3.1 Functionality

Linux Integration Services provides support for the modinfo command. To get module information for each installed kernel module, run
the following command:

# /sbin/modinfo hv_vmbus

filename: /lib/modules/2.6.32-71.el6.i686/extra/hv_vmbus.ko

version: 3.1

license: GPL

srcversion: 56F00728DAE99444BE1FD9B

alias: acpi*:VMBus:*

alias: acpi*:VMBUS:*

depends:

vermagic: 2.6.32-71.el6.i686 SMP mod_unload modversions 686

parm: vmbus_loglevel:int

This command can be repeated for all kernel modules (hv_vmbus, hv_netvsc, hv_storvsc, hv_blkvsc, and hv_utils).

To verify that all subcomponents are running,, as the root user, issue the following command at a shell prompt:

# /sbin/lsmod | grep hv

The output should include lines similar to the following example:

hv_utils 4747 0

hv_netvsc 57832 0

hv_timesource 0 [permanent]

hv_storvsc 50288 0

hv_blkvsc 54032 3

hv_vmbus 70120 3
hv_netvsc,hv_storvsc,hv_blkvsc,hv_utils,hv_timesource,[permanent]

 Note : Your file system type or other local factors might result in different file sizes in your deployment.

  • “hv_netvsc” provides support for the synthetic network card.
  • “hv_storvsc” provides support for the synthetic SCSI controller and disks.
  • “hv_blkvsc” provides support for synthetic IDE  disks and fastpath boot.
  • “hv_timesource” is the pluggable time source module to assist in accurate timekeeping in the virtual machine.
  • “hv_vmbus” is the fast communication channel between the server running Hyper-V and the virtual machine.
  • “hv_utils” provides integrated shutdown, key value pair data exchange, and heartbeat.

4 thoughts on “Linux Integration Services Version 3.1 for Hyper-V – Part 1 – Installation”

  1. Because the Illinois Department of Professional Regulation inspects each parlor annually, you must pay special care to hygiene, safety and equipment sanitation.
    Some people think creams only give a temporary lasting result.
    QR code generated by the writer on Kaywa’s website.

  2. Everyone loves what you guys are usually up too. This sort of clever
    work and coverage! Keep up the great works guys I’ve incorporated you guys to blogroll.

  3. When I initially left a comment I appear to have clicked the -Notify me when new comments are added- checkbox and from now on each time a comment is added I recieve four emails with the exact same comment.
    Perhaps there is a way you can remove me from that service?
    Cheers!

Leave a Comment

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s