Article ID: 118424, created on Nov 4, 2013, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo
  • Virtuozzo containers for Linux
  • Virtuozzo hypervisor

Symptoms

After a fresh installation of PVC/PSBM/PCS, the server does not boot and gets a kernel panic:

dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.
dracut Warning: Signal caught!
dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.
Kernel Panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.32-042stab081.5 #1
Call Trace:
  [<ffffffff814c25ba>] ? panic+0x78/0x143
  [<ffffffff8106e8b9>] ? do_exit+0x909/0x910
  [<ffffffff81185565>] ? fput+0x25/0x30
  [<ffffffff8106e918>] ? do_group_exit+0x58/0xd0
  [<ffffffff8106e9a7>] ? sys_exit_group+0x17/0x20
  [<ffffffff8100b242>] ? system_call_fastpath+0x16/0x1b

Cause

Incompatible hardware is used on the server.

Resolution

If the sources of the necessary kernel modules are publicly available, they should be compiled specifically for vzkernel. The instructions can be found in this article.

If the sources are closed (example: HP hpvsa RAID controller module), it is necessary to contact the corresponding vendor and get the sources for compilation.

Additional resources

You can find more information about hardware compatibility with PCS/PVC/PSBM in this article.

Examples of driver compilations can be found in the following articles:
How to compile IBM RDAC drivers for PVC kernels
How to build HP-ILO modules for PVC

Search Words

modules

Kernel Panic - not syncing: Attempted to kill init!

dracut Warning

hpvsa

incompatible hardware

Boot has failed

reboot loop

drivers

node moved VEs to other nodes and restarted unexpectedly

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f e8e50b42231236b82df27684e7ec0beb 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF