From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HF49g-00066d-IP for qemu-devel@nongnu.org; Thu, 08 Feb 2007 02:57:20 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HF49f-00066R-DN for qemu-devel@nongnu.org; Thu, 08 Feb 2007 02:57:20 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HF49f-00066O-7U for qemu-devel@nongnu.org; Thu, 08 Feb 2007 02:57:19 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HF49e-0005eQ-OO for qemu-devel@nongnu.org; Thu, 08 Feb 2007 02:57:18 -0500 From: David Woodhouse Content-Type: text/plain Date: Thu, 08 Feb 2007 07:57:15 +0000 Message-Id: <1170921435.29759.1252.camel@pmac.infradead.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Booting Fedora in qemu-system-ppc 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 Cc: l_indien@magic.fr When booting the Fedora install CD, we seem to fall over on the ofboot.b script which decides whether to use the 32-bit or 64-bit kernel. http://people.redhat.com/jkeating/qemu-ppc.png Attempting to boot yaboot instead (with -kernel /usr/lib/yaboot/yaboot) doesn't seem much happier -- instead it says: OF_property_copy cannot get property for 'alias' for No name in node! Attempting to boot either the 'vmlinux' or the zImage kernel+initrd in images/netboot/ppc32.img also fails similarly. Are there any special tricks to getting anything to boot in qemu-system-ppc? Now that OpenFirmware is GPL'd, is it worth porting it? -- dwmw2