WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
From: David F Barrera <dfbp@xxxxxxxxxx>
Date: Wed, 22 Dec 2004 09:39:07 -0600
Delivery-date: Wed, 22 Dec 2004 15:40:19 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D123152@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D123152@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
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@xxxxxxxxxxxxxxxxxxxxx
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/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel