Re: [Xen-users] Kernel panic - not syncing: Attempted to kill init

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Thu, 2012-08-23 at 11:35 +0100, Yaogun Wen wrote:
> HI, everyone
> I'm trying to create a paravirtualized domU on Ubuntu 10.04 dom0.
> I follow Professional Xen Virtualization, create filesystem image
> file, clone host's root filesystem, and create configuration file to
> start pv domU.
> 
> 
> $ dd if=/dev/zero of=pv-rootfs.img bs=1024k seek=20480 count=0
> $ mkfs.ext3 pv-rootfs.img
> $ sudo mount -o loop pv-rootfs.img /mnt/tmp/
> $ sudo cp
> -ax /{bin,dev,etc,lib,lib32,lib64,root,sbin,usr,var} /mnt/tmp
> $ mkdir /mnt/tmp/{home,proc,opt,sys,tmp}
> $ chmod 777 /mnt/tmp/tmp/

This doesn't seem like a terribly reliable way to produce a root
filesystem to me. 

You might want to investigate the use of "debootstrap" or the xen-tools
scripts which simplify its use to create Xen guest images.

A fair bit of the info in 
http://wiki.debian.org/Xen#Installation_as_a_DomU_.28guest.29
also applies to Ubuntu.

[...]
> run-init: /sbin/init: No such file or directory
> [    6.272833] Kernel panic - not syncing: Attempted to kill init!
> [    6.272870] Pid: 1, comm: run-init Not tainted 2.6.32.57 #1
> [    6.272888] Call Trace:
> [    6.272919]  [<ffffffff8107758b>] panic+0xa0/0x168
> [    6.272947]  [<ffffffff810b038e>] ? atomic_add_unless+0x29/0x42
> [    6.272977]  [<ffffffff810a1166>] ? raw_local_irq_disable+0x19/0x1b
> [    6.273005]  [<ffffffff81080350>] ? raw_local_irq_enable+0x19/0x1b
> [    6.273032]  [<ffffffff81080362>] ? __write_unlock_irq+0x10/0x12
> [    6.273062]  [<ffffffff81080cfd>] ? exit_ptrace+0x9c/0x10d
> [    6.273089]  [<ffffffff810a1166>] ? raw_local_irq_disable+0x19/0x1b
> [    6.273116]  [<ffffffff81078f29>] ? raw_local_irq_enable+0x19/0x1b
> [    6.273143]  [<ffffffff8107a671>] do_exit+0x79/0x671
> [    6.273170]  [<ffffffff8107ad26>] complete_and_exit+0x0/0x1e
> [    6.273191]  [<ffffffff8103cc82>] system_call_fastpath+0x16/0x1b
> -----------------------------------------------------------------------------
> 
> 
> I've checked existence of file /sbin/init.

If /sbin/init exists in the root file system then this would usually
mean one of:
      * The dynamic loader referred to by /sbin/init is missing
      * One of the libraries referenced by /sbin/init is missing
      * The kernel does not support the architecture used by /sbin/init
        (e.g. it is a 32 bit binary and kernel is 64 bit but doesn't
        have the IA32_EMULATION option enabled)

I would start by "chroot /mnt/tmp" and within the chroot running
"ldd /sbin/init".

Ian.



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users