Re: [Xen-users] Booting dom0: Kernel Panic - not syncing: Attempted to kill init!

[Fabian Lueghausen <lueghausen@xxxxxxxxxxxxxxxxxx>]

Hey Steven,

yes, I did a depmod on the kernel tree and created an initrd after compiling the kernel. This initrd image is being loaded when starting the machine.
The latest prebuilt rpm's on www.xen.org are for RHEL5, not 4.
I tried to run the rpm for xen 3.0.2 and RHEL4.1 (downloaded in the archiv) but this did not work, because PAE is not supported by this package.
Thanks for this hint!

More ideas?

Fabian


Steven Timm schrieb:

Fabian--did you do a depmod on the kernel tree and do a mkinitrd
on your machine after you compiled the kernel?  The error
you are getting to me looks like you do not have the block
devices loaded right in the initrd images you have and thus
it can't find the root directory to continue
the linux boot, maybe it is not even loading the vmlinuz-2.6.18xen
correctly.

Or did you try to use the pre-built rpms or tarballs for RHEL/SL that
are on the www.xen.org site?  I have not tried the 3.1.0 version
of those on SL4 but there are rpms there for SL4.  I did use the
Xen 3.0.4 precompiled version for SL4 on SL4 and that works fine.

Steve Timm


On Fri, 28 Mar 2008, Fabian Lueghausen wrote:

Hello list,

I tried to install Xen 3.1.0 on Scientific Linux (RHEL4), but this mission failed.. Hope you can help me by finding the reason for my problem.
I downloaded the xen sources from http://bits.xensource.com/oss-xen/release/3.1.0/src.tgz/xen-3.1.0-src.tgz and compiled them by running "make" and "./install.sh". This seemed to work.
After setting up grub like this,

  # grub.conf generated by anaconda
  #
  # Note that you do not have to rerun grub after making changes to
  this file
  # NOTICE:  You have a /boot partition.  This means that
  #          all kernel and initrd paths are relative to /boot/, eg.
  #          root (hd0,0)
  #          kernel /vmlinuz-version ro root=/dev/hda3 console=tty0
  console=ttyS0,9600
  #          initrd /initrd-version.img
  boot=/dev/hda1
  default=0
  timeout=5
  splashimage=(hd0,0)/grub/splash.xpm.gz
  hiddenmenu
  #
  title Scientific Linux (2.6.9-11.EL)
   root (hd0,0)
   kernel /vmlinuz-2.6.9-11.EL ro root=LABEL=/ rhgb quiet console=tty0
  console=ttyS0,9600
   initrd /initrd-2.6.9-11.EL.img
  *#
  title Xen 3.1 / XenLinux 2.6
   root (hd0,0)
   kernel /xen-3.1.0.gz dom0_mem=256000 noreboot
   module /vmlinuz-2.6.18-xen ro root=LABEL=/ rhgb quiet console=tty0
  console=ttyS0,9600**
   module /initrd-2.6.18-xen.img
  *

I shut down my machine and restarted it. But it won't come up... as you can see right here:

  (XEN) Command line: /xen-3.1.0.gz dom0_mem=256000 noreboot

      (...)

  System RAM: 511MB (523356KB)
  Xen heap: 10MB (10272KB)
  Domain heap initialised: DMA with 32 bits
  PAE enabled, limit: 16GB
  Processor #0 15:0 APIC version 20
  IOAPIC[0]: apic_id 1, version 32, adress 0xfec00000, GSI 0-23
  Enabling APIC mode: Flat, Using 1 I/O APICs
  Using scheduler: SMP Credit Scheduler (credit)
  Detected 1694.889MHz processor
  CPU0: Intel(R) Pentium(R) 4 CPU 1700MHz stepping 0a
  Mapping CPU0 to node 255
  Total of 1 processors activated.
  ENABLING IO-APIC IRQs
   -> Using new ACK method
  Platform timer is 1.193MHz PIT
  Brought up 1 CPUs
  *** LOADING DOMAIN 0 ***
   Xen kernel: 32-bit, PAE, lsb
   Guest kernel: 32-bit, PAE, lsb, paddr 0xc0100000 -> 0xc045f53c
  PHYSICAL MEMORY ARRANGEMENT:
   Dom0 alloc.: 000000001f000000 -> 000000001f800000 (61952 pages to
  be allocated)
  VIRTUAL MEMORY ARRANGEMENT:
   Loaded kernel: c....... -> c.......
   Init. ramdisk: c....... -> c.......
   Phys-Mach mag: c....... -> c.......
   Start info:    c....... -> c.......
   Page tables:   c....... -> c.......
   Boot stack:    c....... -> c.......
   TOTAL:         c....... -> c.......
   ENTRY ADRESS:  c....... -> c.......
  Dom0 has maximum 1VCPUs
  Initrd len 0x112200, start at 0xc0460000
  Scrubbing Free RAM: .. done.
  Xen trace buffers: disabled
  Std Loglevel: Errors and warnings
  Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
  *Kernel Panic - not syncing: Attempted to kill init!*

Is there anyone who has an idea what I'm doing wrong?! Tried it by myself for a few hours, but I'm in the dark...

Thanks for every reply to this email!

Ciao,
Fabian

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