From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FYFlo-0007pS-Mr for qemu-devel@nongnu.org; Tue, 25 Apr 2006 01:07:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FYFlm-0007oz-Ey for qemu-devel@nongnu.org; Tue, 25 Apr 2006 01:07:28 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FYFlm-0007od-8z for qemu-devel@nongnu.org; Tue, 25 Apr 2006 01:07:26 -0400 Received: from [203.142.22.130] (helo=mx.new.tusker.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FYFo9-0000B6-VI for qemu-devel@nongnu.org; Tue, 25 Apr 2006 01:09:54 -0400 Received: from localhost (localhost [127.0.0.1]) by mx.new.tusker.net (Postfix) with ESMTP id 02B9717819B6 for ; Tue, 25 Apr 2006 13:07:16 +0800 (SGT) Received: from mx.new.tusker.net ([127.0.0.1]) by localhost (new.tusker.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13366-10 for ; Tue, 25 Apr 2006 13:07:10 +0800 (SGT) Received: from [192.168.1.13] (datalex.cable.nu [203.117.94.152]) by mx.new.tusker.net (Postfix) with ESMTP id 0BE0E17819B5 for ; Tue, 25 Apr 2006 13:07:10 +0800 (SGT) Message-ID: <444DAE6F.3000805@tusker.org> Date: Tue, 25 Apr 2006 13:06:55 +0800 From: Damien Mascord MIME-Version: 1.0 Subject: Re: [Qemu-devel] Custom floppy image not booting, hanging at ramdisk... References: <443DEBFA.7050109@tusker.org> In-Reply-To: <443DEBFA.7050109@tusker.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 Hi again, Sorry to top post, just wanted to know if anyone has had similar experiences to this? If not, can someone help me debug the issue (bug?) with qemu here? Damien Mascord wrote: > Heya guys, > > I am trying to create my own uclibc/busybox floppy bootdisk, and am running into an issue with the expansion of the RAMDISK... the > CPU shoots up to 100% and even leaving it overnight, it never recovers from that situation. > > I have tried it under qemu 0.7.2 and 0.8.0 in linux and windows, and all fail to boot the image, where as vmware (and/or native) > boot the disk fine, and goes correctly to the "Please press Enter to activate this console". > > I am using the command line: > > qemu -fda floppy.img -boot a > > And it loads up the kernel, no problem, reaching the ramdisk stage, and then it dies at the following: > > RAMDISK: Compressed image found at block 680 > > If anyone wants a crack at this, the image can be found at http://tusker.sg/floppy.img > > How would I go about debugging this issue? > > Cheers in advance, > > Damien > > > > > > > > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel