From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FugQk-0000fQ-Bw
	for qemu-devel@nongnu.org; Sun, 25 Jun 2006 22:02:26 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FugQi-0000fE-1P
	for qemu-devel@nongnu.org; Sun, 25 Jun 2006 22:02:25 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FugQh-0000fB-RL
	for qemu-devel@nongnu.org; Sun, 25 Jun 2006 22:02:23 -0400
Received: from [64.233.182.191] (helo=nf-out-0910.google.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1FugcT-0005IZ-MN
	for qemu-devel@nongnu.org; Sun, 25 Jun 2006 22:14:33 -0400
Received: by nf-out-0910.google.com with SMTP id c31so779271nfb
	for <qemu-devel@nongnu.org>; Sun, 25 Jun 2006 19:02:22 -0700 (PDT)
Message-ID: <c1bf1cf0606251902w159ed914waf5598e47fa6ac9c@mail.gmail.com>
Date: Sun, 25 Jun 2006 19:02:22 -0700
From: "Ed Swierk" <eswierk@arastra.com>
Sender: eswierk@gmail.com
Subject: Re: [Qemu-devel] initrd & kernel panic
In-Reply-To: <d5a13c80606251823q313dbaf1j@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <d5a13c80606240420p66862d2x@mail.gmail.com>
	<200606241320.37722.paul@codesourcery.com>
	<d5a13c80606251823q313dbaf1j@mail.gmail.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On 6/25/06, VMiklos <vmiklos@gmail.com> wrote:
> initrd=initrd-i686.img.gz -> dropped
> load_ramdisk=1 -> dropped
> prompt_ramdisk=0 -> dropped
> ramdisk_size=33888 -> dropped
> rw -> kept
> root=/dev/ram -> dropped
> console=ttyS0 -> kept as you requested
>
> now it panics with:
> "RAMDISK: Couldn't find valid RAM disk image starting at 0.
> VFS: Cannot open root device "<NULL>" or unknown-block(33,2)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(33,2)"
>
> ok, let's append root=/dev/ram again, still panics:
> "RAMDISK: Couldn't find valid RAM disk image starting at 0.
> XFS: bad magic number
> XFS: SB validate failed
> No filesystem could mount root, tried:  reiserfs ext3 ext2 xfs
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)"
>
> have i missed something?

What format is your initrd? It should be either a gzipped cpio archive
(initramfs) or an uncompressed filesystem image file.

See http://lxr.linux.no/source/Documentation/initrd.txt and
http://lxr.linux.no/source/Documentation/early-userspace/README.

--Ed