[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] domU custom kernel: Kernel panic - not syncing: No init found. Try passing init= option to kernel.


  • To: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
  • Date: Sat, 25 Apr 2009 22:12:36 +0700
  • Delivery-date: Sat, 25 Apr 2009 08:13:13 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Sat, Apr 25, 2009 at 9:07 PM, Alveox Services <alveox@xxxxxxxxxx> wrote:
> VFS: Mounted root (reiserfs filesystem) on device 202:17.
> Freeing unused kernel memory: 268k freed
> Kernel panic - not syncing: No init found.  Try passing init= option to
> kernel.
>
>
> Cannot figure why its not booting. It seems to find and mount root
> correctly....
> When I mount the filesystem manually, /sbin/init appears there.

You could try passing "init=/sbin/init". That would go in domU's
grub.conf (if you use pygrub) or "extra" line on domU config (if
kernel is on dom0).

Another possibility is that the kernel and userland has mismatched arch. Like :
- 32bit kernel on 64bit userland, or
- 64bit kernel, with 32bit compatibility turned off, on 32bit userland
(this happened to me once).

Regards,

Fajar

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.