Linux Integration Services Version v3.3 for Hyper-V

A new version of Linux Integration Services for Hyper-V is released. Here are the changes:

• To mount an ISO file in the virtual machine, the following command must be run before executing the mount command:
  # insmod /lib/modules/$(uname -r)/kernel/drivers/ata/ata_piix.ko
  Alternatively, copy the ISO file into the virtual machine and mount it using the -o loop option.
• Windows 8 Release Preview/Windows Server 2012 and VHDX block size: Using the ext4 file system is recommended for production deployments of Linux on Hyper-V.
• To ensure all disks connected to the virtual machine are seen, all disks connected to a SCSI controller must start with location “0”.
• If a disk was hot-removed from the system, the connected disks will not be rescanned until a new disk is added.
• To use kdump functionality, configure kdump before installing the Linux Integration Services.
• You might see entries in /var/log/messages similar to the following:
  [ 44.870261] STORVSC: WARNING! cmd 0x12 scsi status 0x2 srb status 0x4
  These messages can be safely ignored.
• Virtual machines configured to use more than 7 virtual processors should add “numa=off” to the GRUB boot.cfg to work around a known issue in the Linux kernel.
• Virtual machines configured to use more than 30 GB RAM should add “numa=off” to the GRUB boot.cfg.
• If the Linux Integration Services are removed from a virtual machine configured to use more than one virtual processor, then the irqbalance service should be disabled to allow successful shutdown of the virtual machine.
• PS 278: by-id vs by-uuid (will be creating a KB article).
  12
• The ISO file also contains a .src.rpm (Source RPM) and debugging RPM. The debugging information should not be used unless instructed by Microsoft Support.
• This version of Linux Integration Services no longer includes the Hypercall adapter that was present in earlier versions.
• Verifying the digital signature of the RPM packages under Red Hat Enterprise Linux (by executing the rpm -K command) will return a “KEYS ARE NOT OK” message.
• Support for this version of Linux Integration Services is provided through the Microsoft TechNet forums at http://go.microsoft.com/fwlink/?LinkID=193443&clcid=0x409, or by contacting the appropriate support channels for Microsoft or Red Hat.
• Event log entries: You might see event log entries similar to the following. These messages can be safely ignored:

– Networking driver on ‘Virtual Machine’ loaded but has a different version from the server. Server version 3.2 Client version 0.2 (Virtual machine ID DC1CCF5C-0C1A-4825-B32C-9A4F8F85AA9D). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

– A storage device in ‘Virtual Machine’ loaded but has a different version from the server. Server version 4.2 Client version 2.0 (Virtual machine ID DC1CCF5C-0C1A-4825-B32C-9A4F8F85AA9D). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

Download them from here.