From: Damien Mascord <tusker@tusker.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Custom floppy image not booting, hanging at ramdisk...
Date: Thu, 13 Apr 2006 14:13:14 +0800 [thread overview]
Message-ID: <443DEBFA.7050109@tusker.org> (raw)
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
next reply other threads:[~2006-04-13 6:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 6:13 Damien Mascord [this message]
2006-04-25 5:06 ` [Qemu-devel] Custom floppy image not booting, hanging at ramdisk Damien Mascord
2006-04-25 8:45 ` [Qemu-devel] " Jani Monoses
2006-04-25 14:47 ` [Qemu-devel] " Christian MICHON
2006-04-26 1:55 ` Damien Mascord
2006-04-26 6:40 ` Christian MICHON
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=443DEBFA.7050109@tusker.org \
--to=tusker@tusker.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).