From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fu782-0006Tc-1W for qemu-devel@nongnu.org; Sat, 24 Jun 2006 08:20:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fu77z-0006TO-E4 for qemu-devel@nongnu.org; Sat, 24 Jun 2006 08:20:44 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fu77z-0006TL-9V for qemu-devel@nongnu.org; Sat, 24 Jun 2006 08:20:43 -0400 Received: from [65.74.133.4] (helo=mail.codesourcery.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1Fu7JP-0006aH-AI for qemu-devel@nongnu.org; Sat, 24 Jun 2006 08:32:31 -0400 From: Paul Brook Subject: Re: [Qemu-devel] initrd & kernel panic Date: Sat, 24 Jun 2006 13:20:36 +0100 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606241320.37722.paul@codesourcery.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org > 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. Paul