From: David F Barrera <dfbp@us.ibm.com>
To: xen-devel@lists.sourceforge.net
Subject: Re: Kernel panic - not syncing: Attempted to kill init!
Date: Wed, 22 Dec 2004 09:39:07 -0600 [thread overview]
Message-ID: <41C9951B.8050705@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D123152@liverpoolst.ad.cl.cam.ac.uk>
Ian,
It was a setup problem after all. Mea culpa.
One thing I had to do was to change the /etc/fstab on the xenU partition
(hdc1 in my machine):
/dev/sda1 / ext2 defaults
1 1 <----------- I had the original /dev/hdc1 here
to match the xen config file:
disk = [ 'phy:hdc1,0801,w' ] < ---- This suggestion you gave to use
'0801' and 'sda1' works for some reason.
Using 'hdc1'
here and on the root = /dev/ line does NOT work, as you were aware.
root = "/dev/sda1 ro"
I need to have an initrd in order to have a console. It will not work
without it:
# Kernel image file.
kernel = "/boot/vmlinuz-2.6.9-xenU"
# Optional ramdisk.
ramdisk = "/boot/initrd-2.6.9-xenU.img"
Thanks for all your suggestions!
David F Barrera
Ian Pratt wrote:
>>OK. I copied all the contents from (hdc3) /dev to (hdc1)
>>/dev, and that let's me boot xenU on hdc1. The problem,
>>however, is that this is not they way RHEL 4 works--I need to
>>figure out how the xen0 is able to boot off essentially the
>>same setup.
>>
>>
>
>Have you tried using the xen0 kernel in the other domain? It's possible
>there's some difference in the .config that is causing this.
>
>
I tried this just for kicks, and, of course, it worked.
>Ian
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now.
>http://productguide.itmanagersjournal.com/
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/xen-devel
>
>
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-22 15:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 3:13 Kernel panic - not syncing: Attempted to kill init! Ian Pratt
2004-12-22 15:39 ` David F Barrera [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-22 9:19 Woody Wu
2012-11-22 9:50 ` Jello huang
2012-11-26 7:40 ` Woody Wu
2012-11-26 7:51 ` Baruch Siach
2012-11-26 7:53 ` Woody Wu
2011-07-13 2:57 史星星(研六 福州)
2011-07-13 4:02 ` Vladimir Murzin
2011-07-13 4:16 ` 史星星(研六 福州)
2009-10-16 23:23 2.6.31 kernel for mips compile failure - war.h:12:17: error: war.h: No such file or directory myuboot
2009-10-16 23:50 ` David Daney
2009-11-11 0:22 ` Kernel panic - not syncing: Attempted to kill init! myuboot
2009-11-11 7:45 ` Gaye Abdoulaye Walsimou
2009-11-11 15:48 ` myuboot
2008-04-10 2:07 Kernel Panic " Sreen Tallam
2008-04-10 8:50 ` Sebastian Siewior
2008-04-10 16:53 ` Sreen Tallam
2004-12-22 2:30 Kernel panic " Ian Pratt
2004-12-21 21:25 David F Barrera
2004-12-15 20:40 David F Barrera
2004-12-16 0:07 ` Derrik Pates
2004-12-16 14:41 ` David F Barrera
2004-12-16 18:04 ` Derrik Pates
2004-12-16 19:29 ` David F Barrera
2004-12-17 20:39 ` David F Barrera
2004-12-18 18:18 ` Ian Pratt
2004-12-20 16:08 ` David F Barrera
2004-12-20 19:02 ` Ian Pratt
2004-12-20 19:45 ` David F Barrera
2004-12-20 23:22 ` Ian Pratt
2004-12-21 15:43 ` David F Barrera
2004-12-21 18:53 ` David F Barrera
2004-12-20 17:53 ` David F Barrera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41C9951B.8050705@us.ibm.com \
--to=dfbp@us.ibm.com \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.