From: Tero Kaarlela <tero.kaarlela@kotinet.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] What happened to linuxppc-img from Freeoszoo
Date: Sat, 25 Jun 2005 00:52:05 +0300 [thread overview]
Message-ID: <42BC8085.5030901@kotinet.com> (raw)
Hi,
I tried to boot linuxppc image from freeoszoo with QemuCVS. kernel
boots ok but then I get errors that it cant read filesystem from dev hda.
Also tried with 0.7.0 and it freezes at: Freeing unused kernel memory
my boot command line was: 0.7.0 qemu-system-ppc -prep -kernel
zimage.prep linuxppc.img
CVS qemu-system-ppc M
prep -kernel zimage.prep linuxppc.img
So am I doing something wrong or is it broken currently?
Tero
next reply other threads:[~2005-06-24 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 21:52 Tero Kaarlela [this message]
2005-06-24 19:21 ` [Qemu-devel] What happened to linuxppc-img from Freeoszoo jeebs
2005-06-25 11:19 ` [Qemu-devel] " Stefano Marinelli
2005-06-25 16:23 ` Tero Kaarlela
2005-06-25 15:45 ` Stefano Marinelli
2005-06-25 19:58 ` Tero Kaarlela
-- strict thread matches above, loose matches on Subject: below --
2005-06-27 14:46 [Qemu-devel] " Jim C. Brown
2005-06-27 17:12 ` jeebs
2005-06-27 18:24 ` Jim C. Brown
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=42BC8085.5030901@kotinet.com \
--to=tero.kaarlela@kotinet.com \
--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).