From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=58439 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PB1ZT-000536-0T for qemu-devel@nongnu.org; Wed, 27 Oct 2010 04:42:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PB1Xk-0000aM-AX for qemu-devel@nongnu.org; Wed, 27 Oct 2010 04:41:21 -0400 Received: from gmplib-02.nada.kth.se ([130.237.222.242]:36024 helo=shell.gmplib.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PB1Xk-0000Zw-5l for qemu-devel@nongnu.org; Wed, 27 Oct 2010 04:39:36 -0400 Subject: Re: [Qemu-devel] Which qemu ports actually work? References: <86sjzssydf.fsf@shell.gmplib.org> <8642FB76-3D0B-4326-9C8B-B7ED8802B761@suse.de> <86r5fc22wx.fsf@shell.gmplib.org> <86iq0o20lh.fsf@shell.gmplib.org> From: Torbjorn Granlund Sender: tg@gmplib.org Date: Wed, 27 Oct 2010 10:39:33 +0200 In-Reply-To: (Alexander Graf's message of "Tue\, 26 Oct 2010 22\:06\:12 -0700") Message-ID: <8662wo112y.fsf@shell.gmplib.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: qemu-devel Developers > "install64", which comes a bit longer. It fails in a new way: it > ignores keyboard input, This happens after the kernel has booted, and > the installer has started. =20=20 Yes, ignoring keyboard input sounds right. The issue here is that we're basically emulating a PPC32 machine, but plug in a PPC64 CPU. This works mostly, but for ADB it breaks, as the guest kernel doesn't have support for our ADB controller. Unfortunately, keyboard and mouse are attached using ADB. =20=20 One way to get around this is to use -usb -usbdevice keyboard. That makes no difference. I suppose it is still using the adb keyboard. Another way is to use the serial port instead of graphical console. =20=20 I cannot get this to work either. With -nographic I get the same lock as initially, after Device tree strings 0x0000000002450000 -> 0x00000000024504d9 Device tree struct 0x0000000002451000 -> 0x0000000002453000 Calling quiesce ... returning from prom_init it hangs. Please also keep in mind that PPC emulation is _very_ slow. Why is it slow? If you need performance for this, please just grab a PPC machine and use KVM on it. It will be a lot faster. Physical machines take space and need power. Qemu is a lot leaner. :-) --=20 Torbj=F6rn