From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FuyPS-0007Hl-03
	for qemu-devel@nongnu.org; Mon, 26 Jun 2006 17:14:18 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FuyPQ-0007Gt-81
	for qemu-devel@nongnu.org; Mon, 26 Jun 2006 17:14:17 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FuyPQ-0007Go-1H
	for qemu-devel@nongnu.org; Mon, 26 Jun 2006 17:14:16 -0400
Received: from [66.249.82.196] (helo=wx-out-0102.google.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1FuybN-0003C6-CA
	for qemu-devel@nongnu.org; Mon, 26 Jun 2006 17:26:37 -0400
Received: by wx-out-0102.google.com with SMTP id t4so893845wxc
	for <qemu-devel@nongnu.org>; Mon, 26 Jun 2006 14:14:15 -0700 (PDT)
Message-ID: <d5a13c80606261414h7b88fad3v@mail.gmail.com>
Date: Mon, 26 Jun 2006 23:14:15 +0200
From: VMiklos <vmiklos@gmail.com>
Subject: Re: [Qemu-devel] initrd & kernel panic
In-Reply-To: <c1bf1cf0606251902w159ed914waf5598e47fa6ac9c@mail.gmail.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>
	<d5a13c80606251823q313dbaf1j@mail.gmail.com>
	<c1bf1cf0606251902w159ed914waf5598e47fa6ac9c@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

2006/6/26, Ed Swierk <eswierk@arastra.com>:
> 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.

as i said the kernel&initrd is ok if i boot them (using grub) from an
iso image. anyway i've tried to uncompress the gzipped initrd, and it
didn't help (same "RAMDISK: Couldn't find valid RAM disk image
starting at 0." error message)

if grub is able to boot the kernel & initrd and qemu isn't then the
kernel & initrd should be ok, just the parameters may be wrong or
there should be some problem with qemu itself. or am i wrong?

thanks,
VMiklos

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