Q:

Linux Integration Services no longer function after a kernel upgrade on Hyper-V

I've been running CentOS 6.2 as a VM under Hyper-V on my Windows Server 2008 R2 system.
If I run "uname -r" it shows my current Linux version as "2.6.32-220.4.1.el6.x86_64"
A while ago, I did a software update and included in the update was a kernel update. When I rebooted the Linux VM, it came up with a kernel panic message and would not continue. I figured out that if I pressed the space bar during boot and selected the old (original) Linux kernel version, the system would boot fine.
I did some Googling and it I found a site that explains that the Linux Integration Services code needs to be recompiled for the kernel that you're running. Since I can't boot into that kernel, I'm not sure how that is even possible.
More Googling got the following site - http://support.microsoft.com/kb/2387594/de - which says I need to install Dynamic Kernel Module Support - DKMS (which I did) but when I follow further in the instructions it references a "dkms.conf" file which doesn't exist. Creating a blank one doesn't work either as attempting to run the "dkms add -m linuxic -v 3.2" command (I'm running Linux Integration Services 3.2) comes back with "Error! Bad conf file."
Any clues as to how to fix the issue so I can keep my Linux kernel up-to-date on CentOS 6 running the Linux Integration Services 3.2 drivers?

A:

It turns out that the problem was with the CentosPlus kernels that were getting installed. The "CentOS-6-Plus" source was checked in "Add/Remove Software->System->Software Sources" and the "plus" kernels were getting installed with software updates. 
Apparently there is some incompatibility between these Plus kernels (they contain "plus" in the kernel name - which you can see by typing "rpm -q kernel" in a terminal screen).
I unchecked "CentOS-6 Plus" as a software source and deleted the new plus versions of the kernel that had been installed via "yum remove " and then with the next software update, the non-plus version of the updated kernel was installed and the system booted without a kernel panic.
Hope this helps someone else in the same boat.

