Kernel panic after upgrading CentOs 6.5 to 6.7 and LIS from 4.07 to 4.0.11

For those that you don’t know, Linux Integration Services or LIS in short, are a set of drivers that enable synthetic device support in Linux VMs that are running on Hyper-V. Plainly speaking, these drivers allow you have almost all the nice stuff you take for granted when you use Windows under Hyper-V and that’s mouse support (remember the days when you had to press CTRL + Left/Right arrow? Not anymore), dynamic memory, synthetic network adapters (not the legacy Intel 1000 which only works in 10mbps mode) and lots more feature where you can read about HERE

Now recently I got a chance to update LIS from 4.07 to 4.0.11 on some production CentOS servers that were updated to 6.7 a while back that were still running version 4.0.7 without any issues, even if CentOS 6.7 wasn’t officially supported by Microsoft.
So I did all the necessary steps for roll-back purposes and started the upgrade process which worked just fine until I rebooted the VMs and got a very nice cup of kernel panic.

SCVMM 2012 R2 – Service Template Deployment fails on “Installing VM Components”

Picture this, you install a brand new Virtual Machine Manager to manage your Hyper-V cluster and after everything works just fine for a month or so, then you get a request to provision a couple of VMs. You say no problem, because you invested a lot of time in creating a couple of service templates coupled with some PowerShell scripts for post deployment configuration so you can just press a button and do something else right?


Pin It on Pinterest