[Fedora-xen] Re: Unable to reboot a domU

Ben bench at silentmedia.com
Thu Mar 16 07:02:39 UTC 2006


OK, so it turns out I am a tard. Or SELinux is too picky. Or some  
combination of those two.

In trying to disable SELinux, I accidently changed  
SELINUXTYPE=targeted to SELINUXTYPE=disabled. So the config  
effectively said:

SELINUX=enforcing
SELINUXTYPE=disabled

That probably shouldn't cause a kernel panic, but then again, that's  
probably not what I should change it to, either.

Bug updated.

On Mar 15, 2006, at 6:09 PM, Ben wrote:

> I installed a domU on x86_64 today, and was very happy. I even  
> logged into it and saw that things seemed to be working, and all  
> was well. I tried to reboot it, and now the domU kernel panics  
> every time I try to boot. :(
>
> The bug is 185603, and the console end with:
>
> no fstab.sys, mounting internal defaults
> Switching to new root and running init.
> unmounting old /dev
> unmounting old /proc
> unmounting old /sys
> Kernel panic - not syncing: Attempted to kill init!
>
> Call Trace: <ffffffff80128d62>{panic+134} <ffffffff8020b652> 
> {__up_read+19}
>        <ffffffff80170b04>{__fput+354} <ffffffff802d66f2> 
> {_spin_unlock_irq+9}
>        <ffffffff802d6006>{__down_read+52} <ffffffff802d67ef> 
> {_spin_lock_irqsave+38}
>        <ffffffff8020b652>{__up_read+19} <ffffffff8012c70b>{do_exit 
> +140}
>        <ffffffff8012cfa0>{sys_exit_group+0} <ffffffff8010ad82> 
> {system_call+134}
>        <ffffffff8010acfc>{system_call+0}
>
>
>
> Any thoughts?




More information about the Fedora-xen mailing list