From: <jeebs@yango.us>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] What happened to linuxppc-img from Freeoszoo
Date: Fri, 24 Jun 2005 14:21:04 -0500 [thread overview]
Message-ID: <00a401c578f1$e04d4920$334d21d1@organiza3bfb0e> (raw)
In-Reply-To: 42BC8085.5030901@kotinet.com
"Tero Kaarlela"
> 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
What's the date of the disk image itself?
Late last year, QEMU reworked the disk geometry, and that can confuse old
disk images. The images expect an old style and the newer qemu offers a
different geometry.
qemu now more closely does what a real system does. But I think somebody in
the qemu user forum came across a situation where it wasn't true. Don't
remember the details, but I think it was for 512m sizes. I don't remember
well, so I could be wrong. Anyway, it works better now than it did before.
Somebody with lots of bandwidth needs to go through those old images and see
if they still work right.
We know for certain the ReactOS image doesn't work anymore and needs to be
replaced. I don't think anybody has gotten around to replacing it, though.
And since ReactOS is so small and installs so easily, there hasn't been a
great need to update it.
If you can figure out what the geometry was on the disk image, then you can
use the -hdacs command line option to tell qemu to use those settings.
next prev parent reply other threads:[~2005-06-24 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 21:52 [Qemu-devel] What happened to linuxppc-img from Freeoszoo Tero Kaarlela
2005-06-24 19:21 ` jeebs [this message]
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='00a401c578f1$e04d4920$334d21d1@organiza3bfb0e' \
--to=jeebs@yango.us \
--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).