From mboxrd@z Thu Jan 1 00:00:00 1970 From: David F Barrera Subject: Re: Kernel panic - not syncing: Attempted to kill init! Date: Fri, 17 Dec 2004 14:39:38 -0600 Message-ID: <41C3440A.5020806@us.ibm.com> References: <41C0A148.2040209@us.ibm.com> <41C0D1BC.7020305@dsdk12.net> <41C19E98.9010802@us.ibm.com> <41C1CE1E.1030306@dsdk12.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <41C1CE1E.1030306@dsdk12.net> Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org Derrick, I rebuilt the xenU kernel, with the devfs support disabled, and it makes no difference. It behaves in the same manner as the pre-built kernel that's included with the binary pack. I am at a loss. I've been able to boot a kernel under xen on a SuSE Linux 9.0 machine, so I've had a little experience with this:-) Freeing unused kernel memory: 92k freed Red Hat nash version 4.1.18 starting Mounted /proc filesystem Mounting sysfs Creating /dev Starting udev Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! <0>Rebooting in 1 seconds.. David Barrera 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. The only other possibility I > can think of is that you need to change the block-device import to > read-write. > ------------------------------------------------------- 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/