From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Dlty4-0005re-1a for qemu-devel@nongnu.org; Fri, 24 Jun 2005 15:36:00 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Dltxv-0005mu-Gn for qemu-devel@nongnu.org; Fri, 24 Jun 2005 15:35:54 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dltxt-0005fD-IY for qemu-devel@nongnu.org; Fri, 24 Jun 2005 15:35:50 -0400 Received: from [209.55.3.83] (helo=mxo3.broadbandsupport.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DltnP-0004xn-IL for qemu-devel@nongnu.org; Fri, 24 Jun 2005 15:24:59 -0400 Received: from organiza3bfb0e (unknown [209.33.77.51]) by mxo3.broadbandsupport.net (Postfix) with SMTP id 97E71236EA8 for ; Fri, 24 Jun 2005 15:21:13 -0400 (EDT) Message-ID: <00a401c578f1$e04d4920$334d21d1@organiza3bfb0e> From: References: <42BC8085.5030901@kotinet.com> Subject: Re: [Qemu-devel] What happened to linuxppc-img from Freeoszoo Date: Fri, 24 Jun 2005 14:21:04 -0500 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 "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.