From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HBHqS-0000zr-OL for qemu-devel@nongnu.org; Sun, 28 Jan 2007 16:45:52 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HBHqR-0000wW-5u for qemu-devel@nongnu.org; Sun, 28 Jan 2007 16:45:52 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HBHqQ-0000vw-Uo for qemu-devel@nongnu.org; Sun, 28 Jan 2007 16:45:50 -0500 Received: from nz-out-0506.google.com ([64.233.162.234]) by monty-python.gnu.org with esmtp (Exim 4.52) id 1HBHqQ-0002IC-KC for qemu-devel@nongnu.org; Sun, 28 Jan 2007 16:45:50 -0500 Received: by nz-out-0506.google.com with SMTP id i11so2081835nzi for ; Sun, 28 Jan 2007 13:45:50 -0800 (PST) Message-ID: <46d6db660701281345r5de0a9e2pd9716ee06c20414c@mail.gmail.com> Date: Sun, 28 Jan 2007 22:45:49 +0100 From: "Christian MICHON" Subject: Re: [Qemu-devel] How to run qemu (i386) without hda image? In-Reply-To: <5d649bdb0701281337k7c894457p8a1d59c67310534f@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: <5d649bdb0701281211xc19afcal5c2b5d10d483695b@mail.gmail.com> <46d6db660701281249o61cf03bcycfad0d9106c4ecd9@mail.gmail.com> <5d649bdb0701281316p71cd6f3aq6a398a509ce73182@mail.gmail.com> <46d6db660701281325l45fcf5afq94f7180a33a64b3@mail.gmail.com> <5d649bdb0701281337k7c894457p8a1d59c67310534f@mail.gmail.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 On 1/28/07, Neo Jia wrote: > Thanks. After removing "root=/dev/hda", I still get the following > error messages. I think the kernel should be boot even without the > fc3.img, right? not necessarily. if your kernel contains an initramfs, then it is self sufficient. Again, the boot process ends with the initrd you supplied... Maybe this initrd lacks drivers or shell scripts to properly start init. I cannot tell unless I've a close look at the initrd content and the config file used to compile the kernel. try now adding "init=/bin/sh" :) -- Christian