LIS 4.0.11 not working with CentOS 7.2 about lis-next

[shirgall]

This is now fixed with the release of LIS 4.1: https://www.microsoft.com/en-us/download/details.aspx?id=51612

[shirgall]

It is important to uninstall LIS before performing a kernel upgrade. Sometimes a kernel upgrade will reinstall LIS daemons or conflict with the LIS RPMs. AFter the kernel upgrade, reinstalling LIS will unload the distro versions of these packages and load the LIS ones in their place.

[NTICompass]

I didn't uninstall LIS before, but I did uninstall and then reinstall it afterwards. That unfortunately didn't seem to help.

I think that something changed in the new kernel that needs to be addressed in the code. I think RHEL72 (3.10.0-327) may need to be added to the LIS ISO.

[shirgall]

Sorry, I missed that you were talking about 7.2. Yes, getting 7.2 support into lis-next is currently in progress and is not complete.

[NTICompass]

Ok, cool. I could find any info when I was searching, so I figured I'd post a bug.

[MHT980]

i have the exact same problem.
kernel: hyperv_keyboard: disagrees about version of symbol vmbus_driver_unregister
CentOS Linux release 7.2.1511 (Core), kernel 3.10.0-327.3.1.el7.x86_64
It works with kernel 3.10.0-229.20.1.el7.x86_64
this only occurs with HyperV generation 2 virtual machine.

in generation 1 with same kernel and distro it works fine.

[NTICompass]

We'll just need to wait until LIS is updated for RHEL/CentOS 7.2

[marcinbojko]

I am really tired fighting with LIS modules every time I do yum-update. Instead of writing excuses everytime, just put the code in Linux kernel, as the others. Developement stopped on 3.1 and thats all.

[shirgall]

All of LIS gets submitted and accepted upstream eventually, and we do work with the distributions to get our work pulled in from there. The only reason for the separate package is for the timely availability of new features and fixes that have not worked their way through the upstream process yet. The "3.1" version number is an artifact of upstream inclusion and does not reflect the capabilities of the underlying Hyper-V drivers that have been included.

[marcinbojko]

Thanks Joshua. You convinced me to use distribution provided modules.
However, everything what Hyper-V is showing right now is just 'Detected' not a version number.

[shirgall]

The 7.2 kernel has a lot of support built in. We don't carry separate version numbers because what backports Red Hat takes is not a linear mapping to releases here. Bug fixes are easy, features are hard, and it all has to mesh with their release cycles. The work we are putting into LIS here will add 7.2 to the roster of supported versions, but it is also going to add more features that are not yet fully through the upstream process and backport process.