I am not sure why this is happening neither the hostnode or VM changed.  All I did was reboot the hostnode and startup the Centos VM again, also note it happened with the original kernel on the VM and also the latest 6.9 kernel as of this writing as shown below.

Host Node: Centos 6.9

Kernel: 2.6.32-696.6.3.el6.x86_64 

Kernel: 2.6.32-042stab123.9

Same result in any kernel above

=========

VM Node: Centos 6.6 originally (this is where the error started but chrooting and upgrading did not fix it).

Kernels: 2.6.32-504.el6.x86_64,  2.6.32-696.6.3.el6.x86_64

I have tried different kernels on the host node and in the VM it made no difference.

I restored the same VM image and so far it boots fine but I have not made any changes to see if it boots again.  As mentioned even chrooting into the VM and upgrading the kernel and rebuilding initramfs has not fixed it.

Kernel panic - not syncing: Attempted to kill init!


Pid: 1, comm: init Not tained 2.32-696.6.3.el6.x86_64 #1


Call Trace:


[] ? panic+0xa7x0x179


[] ? perf_event_exit_task<+0xc0/0x340


[] ? do_group_exit+0x0/0xd0


[] ? fput+0x25/0x30


[] ? do_group_exit+0x58/0xd0


[] ? sys_exit_group+0x17/0x20


[] ? system_call_fastpath+0x16/0x1b

centos, kvm, vm, kernel, syncing, init, hostnode, reboot, startup, node, _, originally, chrooting, upgrading, kernels, restored, rebuilding, initramfs, pid, comm, tained, xa, perf_event_exit_task, xc, do_group_exit, xd, fput, sys_exit_group, system_call_fastpath,

Latest Articles