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: Thu, 16 Dec 2004 13:29:00 -0600
Delivery-date: Thu, 16 Dec 2004 19:31:01 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <41C1CE1E.1030306@xxxxxxxxxx>
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: <41C0A148.2040209@xxxxxxxxxx> <41C0D1BC.7020305@xxxxxxxxxx> <41C19E98.9010802@xxxxxxxxxx> <41C1CE1E.1030306@xxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
Derrik ,

Thanks for the feedback.

Derrik Pates wrote:

David F Barrera wrote:

The distro I am using is RHEL 4 Beta 2 (Red Hat Enterprise Linux Desktop release 3.90 (Nahant)


/dev/hdc1 / ext2 defaults 1 1


LABEL=SWAP-hdc2 swap swap defaults 0 0 /dev/hda /media/cdrom auto pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed 0 0


# disk = [ 'phy:hda1,hda1,r' ]
disk = [ 'phy:hdc1,hdc1,r' ]


Well, the configuration of the virtual disk looks correct; the swap might disagree with it, but that shouldn't appear until later in the boot process. Perhaps it's an interaction with devfs? Do you have devfs enabled in your xenU (unprivileged domain) kernel? This gave me fits when I first began using Xen, mostly because it seems that the xenU prebuilt kernel that's included with the binary pack has devfs support enabled, and this breaks things.

I will try rebuilding the xenU kernel.

The only other possibility I can think of is that you need to change the block-device import to read-write.

I've already tried changing the block-device import to read-write. No difference.


-------------------------------------------------------
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