Microsoft has updated the Linux Integration Services (aka integration components or the Hyper-V enlightenments) from v3.1 to v.3.2 supporting Redhat Enterprise Linux (x86 and x64, 6.0 and 6.1) and CentOS 6.0 (x86 and x64).
I think no new features are listed. My guess is that v3.2 includes a fix or workaround for Key Value Pair exchange and SCVMM. But that is a guess. I’ll try to find out more.
You’ll continue to use Linux Integration Services 2.1 for SLES 10 and RHEL 5.
EDIT #1:
I did some comparisons between 3.1 and 3.2 text and noticed this is added in 3.2:
“Integrated Mouse Support: The cursor is no longer bound to the VMConnect window when used with the Linux Graphical User Interface”.
EDIT #2:
Thanks to Mike Sterling (Program Manager at Microsoft) for sharing the following info on new features in the V3.2 Integration Services:
- Synthetic Mouse Support: The virtualized mouse device is no longer bound to the VMConnect window, and can now be used with a RDP session.
- Merged Device Drivers: We now present a single device driver for both IDE and SCSI devices (hv_storvsc).
- Windows 8 Fix: The synthetic network device (hv_netvsc) can now be used with a Windows 8 host, eliminating the hang on boot that was previously seen.
- SCVMM Fix: This release fixes the issue as described in KB2586286.
- Improved Setup Experience: Users now only need to run install.sh (as root) to automatically detect the correct architecture and install the appropriate drivers.
Linux. Phooey.
JamesNT
But it’s a deal breaker for many if it doesn’t have support.
Have you noticed that both IC V 3.1 and 3.2 seem to kill the CDROM in Redhat 6.1? It has happened to me on two VMs. I am trying to get back into Unix/RedHat and can’t figure out how to get the cdrom back…
I’ve not had that problem. You might be able to log something via Connect.
Aidan, haven’t you mentioned this problem in the list of Hyper-V related patches couple posts below? (http://support.microsoft.com/kb/2600152/en-us?sd=rss&spid=14134). Or is this different issue?
I mentioned the issue with the V3.1 IC’s in that post. However, that was a workaround that disabled data exchange via disabling KVP. A hack rather than a fix. V3.2 fixes the actual issue.