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

Re: [Xen-users] Xen 3.2 is not loading on FC8 - Error: Kernel panic -Attempted to kill init


  • To: "Tait Clarridge" <Tait.Clarridge@xxxxxxxxxxxx>
  • From: "Argyro Andreou" <argyro.andreou@xxxxxxxxx>
  • Date: Thu, 14 Feb 2008 09:59:33 -0500
  • Cc: weiming <zephyr.zhao@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 14 Feb 2008 07:00:18 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=upSbYhPirosaOTOWH8N4h45K/tLg7h1Yh8+T4qhzFUfwsUJegEAD2lHP+koSLGzZy0o4Z0Qbj6G/HgQcnyFy/tgWiigNsL/I50LiYJFYYMq4tP1D2+spNT1y9NhEWrGQrczZ9dXe6MH2DgREnutIK+Zr7sDtDrVjLf2jCT3UQc0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

So then what type of changes would I have to make to the config file to compile the kernel the way you describe? I took a look at it and I it seems to me that the write options are enabled.
 
Thanks for your help !!!
Argyro

On Wed, Feb 13, 2008 at 4:27 PM, Tait Clarridge <Tait.Clarridge@xxxxxxxxxxxx> wrote:
I remember that I had to compile all the RAID + LVM section of the kernel config directly into the kernel, and not as modules. As well I had to have each of the USB host sections as modules and the AHCI support built as a module.

Then I compiled my initrd with sd_mod, sg, ahci (I think) to get it to find my logical volumes.



From: weiming [mailto:zephyr.zhao@xxxxxxxxx]
Sent: Wednesday, February 13, 2008 4:24 PM
To: Argyro Andreou
Cc: Tait Clarridge; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Xen 3.2 is not loading on FC8 - Error: Kernel panic -Attempted to kill init

I guess some device driver for your sata driver was not loaded, so the kernel can't find the /dev/root device.
Did you change the .config of linux kernel? By default, it should include most of the drivers.
On Feb 13, 2008 4:09 PM, Argyro Andreou <argyro.andreou@xxxxxxxxx> wrote:
Hey Tait,
 
 
When I remove the quiet flag it says the following:
 
Scanning logical volumes
Reading all physical volumes
No volume groups found
Activating logical volumes
    Volume group VolGroup00 not found
Creating root device
Mounting root filesystem
mount: could not find filesystem /dev/root
Setting up other filesystems
Setting up new root fs
setuproot: moving /dev failed: No such file pr directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file ot directory
seturoot: error mounting /sys: No such file to directory
Switching to new root and running init
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Booting has failed
Kernel panic-not synching: Attempted to kill init!
 
 
When installing Fedora Core 8 I didn't do custom partitioning I used the default option. If custom partitioning is need can you please tell me exactly what partitions are needed?
 
Thanks
Argyro
On Feb 13, 2008 3:48 PM, Tait Clarridge <Tait.Clarridge@xxxxxxxxxxxx> wrote:
Hi Argyro,
 
Could you take out the "quiet" switch in the Xen kernel boot args and tell us exactly what it says? You might also want to add a "noreboot" in that section so you can write down exactly what it says.
 
Thanks,
-Tait
 
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Argyro Andreou
Sent: Wednesday, February 13, 2008 3:36 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen 3.2 is not loading on FC8 - Error: Kernel panic -Attempted to kill init
 
Hi all,

I compiled and installed Xen 3.2 source on FC8. Compilation and installation completed with no errors. However when I try to load Xen I get an error: Kernel panic - Attempted to kill init !!!

This is my grub configuration:

# 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/VolGroup00/LogVol00
#          initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=15
splashimage=(hd0,0)/grub/splash.xpm.gz
#hiddenmenu
title Fedora (2.6.23.1-42.fc8)
    root (hd0,0)
    kernel /vmlinuz-2.6.23.1-42.fc8 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
    initrd /initrd-2.6.23.1-42.fc8.img

title Fedora Core 8 + Xen 3.2.0
    root (hd0,0)
    kernel /xen-3.2.1-rc1-pre.gz
    module /vmlinuz-2.6.18.8-xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet
    module /initrd-2.6.18.8-xen.img   

I tried loading Xen without initrd also. But I get the same error.

Please can anyone help me. I've trying to solve this problem since last Friday and I can't see any light at the end of the tunnel


Regards
Argyro


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



_______________________________________________
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®.