From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1GkGDZ-0001xs-Ha
	for qemu-devel@nongnu.org; Wed, 15 Nov 2006 03:34:01 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1GkGDY-0001wZ-Ii
	for qemu-devel@nongnu.org; Wed, 15 Nov 2006 03:34:00 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1GkGDY-0001wI-81
	for qemu-devel@nongnu.org; Wed, 15 Nov 2006 03:34:00 -0500
Received: from [66.54.152.27] (helo=jive.SoftHome.net)
	by monty-python.gnu.org with smtp (Exim 4.52) id 1GkGDY-0000gm-05
	for qemu-devel@nongnu.org; Wed, 15 Nov 2006 03:34:00 -0500
From: Mulyadi Santosa <a_mulyadi@softhome.net>
Subject: SOLVED Re: [Qemu-devel] inside qemu,
	kernel 2.6.17-mm6 fails to boot disk image
Date: Wed, 15 Nov 2006 15:33:15 +0700
References: <200611101629.33619.a_mulyadi@softhome.net>
In-Reply-To: <200611101629.33619.a_mulyadi@softhome.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200611151533.15347.a_mulyadi@softhome.net>
Reply-To: a_mulyadi@softhome.net, 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..

> Hello everybody
>
> Today I boot my FC2 disk image along with 2.6.17-mm6 kernel using
> this command line:
> qemu -hda ./fc2.img -m 64 -net none -kernel
> /mnt/linux/linux-2.6.17-mm6-HZ1000/arch/i386/boot/bzImage -no-kqemu
> -append root=/dev/hda1

Following up my own post, I revealed that this problem was related with 
the fact that both of these kernel configs were disabled:
CONFIG_IDE_GENERIC
CONFIG_BLK_DEV_GENERIC

The solution , in case you meet the same trouble like me, is to enable 
those two configs and it should boot fine.

NB: Of course, it wouldn't hurt if you check the partition with fsck so 
you're sure nothing is wrong inside the partition itself. In my case, 
fsck found nothing wrong in my disk image.

regards,

Mulyadi