From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FufpQ-0001lk-Kd
	for qemu-devel@nongnu.org; Sun, 25 Jun 2006 21:23:52 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FufpO-0001lH-2A
	for qemu-devel@nongnu.org; Sun, 25 Jun 2006 21:23:51 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FufpN-0001lE-Sm
	for qemu-devel@nongnu.org; Sun, 25 Jun 2006 21:23:49 -0400
Received: from [66.249.82.196] (helo=wx-out-0102.google.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1Fug19-0003HX-JC
	for qemu-devel@nongnu.org; Sun, 25 Jun 2006 21:35:59 -0400
Received: by wx-out-0102.google.com with SMTP id t4so772645wxc
	for <qemu-devel@nongnu.org>; Sun, 25 Jun 2006 18:23:49 -0700 (PDT)
Message-ID: <d5a13c80606251823q313dbaf1j@mail.gmail.com>
Date: Mon, 26 Jun 2006 03:23:49 +0200
From: VMiklos <vmiklos@gmail.com>
Subject: Re: [Qemu-devel] initrd & kernel panic
In-Reply-To: <200606241320.37722.paul@codesourcery.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <d5a13c80606240420p66862d2x@mail.gmail.com>
	<200606241320.37722.paul@codesourcery.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

hi,

2006/6/24, Paul Brook <paul@codesourcery.com>:
> > what i've tried:
> >
> > http://frugalware.org/~vmiklos/logs/qemu-initrd.log
> >
> > if i generate the iso and boot this kernel & initrd with the same
> > parameters from grub, it works fine
> >
> > have i missed something?
>
> You're telling it to load the initrd from floppy, which is obviously wrong.
> qemu already loaded the initrd. Remove all the broken initrd/ramdisk kernel
> commandline bits.

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?

thanks,
VMiklos

--
Developer of Frugalware Linux, to make things frugal - http://frugalware.org