-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/13/2013 05:52 PM, Nux! wrote: > On 12.03.2013 20:41, Emmett Culley wrote: >> After successfully updating three CentOS 6.3 VM guests to 6.4 I decided >> to update the host as well. And it failed to boot. >> >> Kernel panic - Not syncing: Attempted to kill init! Pid: 1, comm: init >> not tainted: 2.6.32-358.2.1.el6.x86_64 #1 Plus a call trace I couldn't >> see > > Is selinux on? If you boot the new kernel with selinux=0 does the panic > happen? I had this happen to me recently. > You can leave SELinux on in permissive mode using enforcing=0. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFBx90ACgkQrlYvE4MpobNW9QCglp3IoeXleJWrxbMwQsngaf6w mR0AoMBamEd6Zcz+h/mbtrLG11bnMLCW =ZqVF -----END PGP SIGNATURE-----