From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=56547 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PAmhC-0001wk-HS for qemu-devel@nongnu.org; Tue, 26 Oct 2010 12:48:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PAmh9-0004aw-FH for qemu-devel@nongnu.org; Tue, 26 Oct 2010 12:48:22 -0400 Received: from gmplib-02.nada.kth.se ([130.237.222.242]:62632 helo=shell.gmplib.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PAmh8-0004a2-OM for qemu-devel@nongnu.org; Tue, 26 Oct 2010 12:48:19 -0400 From: Torbjorn Granlund Sender: tg@gmplib.org Date: Tue, 26 Oct 2010 18:38:20 +0200 Message-ID: <86sjzssydf.fsf@shell.gmplib.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] Which qemu ports actually work? List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org I am not sure this inquiry is appropriate for this mailing list. But at the qemu web site, this is the only mailing list mentioned. I would like to run as many OS's as possible under as many processors as possible, using qemu. Results thus far has not been very encouraging, though. Here is my test matrix: fbsd-8_1 nbsd-5_0_2 debian-5 gentoo hurd sparc n/a OK n/a n/a n/a sparc64 fw crash fw crash kern crash black fb n/a ppc early hang fw crash OK kern hang n/a ppc64 early panic fw crash kern hang kern hang n/a i386 OK OK OK installs, non-booti= ng x86_64 OK OK OK These are results from multiple attempts and google searches for what other people have done. Unfortunately, there aren't many matches, except that the various error messages I get have been experienced by several other people. Is this what I can expect from qemu today? Are the goals of the qemu project to make the various ports operational for running these OS's? If yes, what is the time frame? It would be nice with a status page (there is a blank such page already, I mean a non-blank page...) informing about the status of the various ports. A naive user--such as myself--tends to assume that a released port actually works. It takes many hours of poorly used effort before one can conclude that e.g., sparc64 does not work at all. (We should probably not blame qemu for hurd's shortcomings here. Hurd is highly experimental. I have not tried it on actual hardware.) --=20 Torbj=F6rn