Kernel Panic on Hyper-V Virtual Machine after switching from (unsupported) kmod modules to (supported) Hyper-V kernel modules shipped in RHEL 6.4.

Solution Verified - Updated -

Issue

  • Switching from the ( ETES / Microsoft LIC ) (unsupported) kmod RPM packages to (supported) Hyper-V kernel module shipped in RHEL 6.4 fails during boot with below kernel panic.
kernel panic - not syncing: Attempted to kill init!
Pid: 1. comm: init Not tainted 2.6.32.358.0.1.el6.x86_64 #1
Call Trace:
  [<ffffffff814fd11a>] ? panic+0xa7/0x16f
  [<ffffffff81070db2>] ? do_exit+0862/0x870
  [<ffffffff8117ca75>] ? fput+0x25/0x30
  [<ffffffff81070c38>] ? do_group_exit+0x58/0x10
  [<ffffffff81070cc7>] ? sys_exit_group+0x17/0x20
  [<ffffffff8100b0f2>] ? system_call_fastpath+0x16/0x1b
atkbd.c: Unknown Key pressed (translated set 2, code 0x00 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e000 <keycode>' to make it known
  • Performed yum update and emptied /lib/modules/2.6.32-358.0.1.el6.x86_64/weak-updates (symlinks to old kmod RPM) and recreated the initramfs via following command:
# dracut --drivers "hv_netvsc hv_storvsc hv_utils hv_vmbus hid-hyperv" --force /boot/initramfs-2.6.32-358.0.1.el6.x86_64.img 2.6.32-358.0.1.el6.x86_64

Environment

  • Red Hat Enterprise Linux 6.4
  • Hyper-V virtual machine
  • ETES provided Hyper-V modules
  • Microsoft "Linux Integration Component" MS LIC drivers

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content