From: Torbjorn Granlund <tg@gmplib.org>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Which qemu ports actually work?
Date: Tue, 26 Oct 2010 21:02:22 +0200 [thread overview]
Message-ID: <86r5fc22wx.fsf@shell.gmplib.org> (raw)
In-Reply-To: <8642FB76-3D0B-4326-9C8B-B7ED8802B761@suse.de> (Alexander Graf's message of "Tue\, 26 Oct 2010 10\:13\:42 -0700")
Alexander Graf <agraf@suse.de> writes:
Where exactly do the Linux kernels hang here? For BSD, I don't
know. If there are patches flowing in to fix BSD support, I'll gladly
review and take them, but I won't proactively try to get it running.
Is this how most qemu hackers feel, in effect that qemu is a hardware
emulator for the kernel linux? To me, that seem like aiming low, and also
a strategy resulting in a less robust program. (I maintain a couple of
free software packages, and I certainly run as many tests as possible to
make them robust.)
(1) For ppc32, gentoo hans quickly, the last line is this:
Memory: 247644k/262144k avalable (5652k kernel code, 14500l reserved, 212k data, 137k bss, 260k ini
This last line is long, it is truncated to the right.
(2) For ppc64, the last lines are:
Calling quiesce ...
returning from prom_init
This happens is almost immediately, within a second.
(Debian and Gentoo hangs at the same positions.)
(3) The sparc64 crash for Debian happens much later. The last lines are:
/bin/sh: relocation error: /bin/sh: symbol eaitpid, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
[ 48.xxxxxx] Kernel panic - not syncing: Attempted to kill init!
[ 48.xxxxxx] Press Stop-A (L1-A) to return to the boot prom
I am not sure gentoo should be expected to work, at least not the 64-bit
kernel. It claims to be "G5" whatever that means (G5 is Apple's name for
the IBM ppc970 processor, not a particular computer architecture, so I am
not sure what gentoo means).
Well, the good news on this part is that the qemu web page is a wiki! So
if there's no status in there at all, feel free to add your experience.
Natalia also has a page trying to list compatibility.
Do you have a pointer to that page of this Natalia?
BTW, this is the qemu version I am trying:
king$ qemu --version
QEMU emulator version 0.13.0, Copyright (c) 2003-2008 Fabrice Bellard
--
Torbjörn
next prev parent reply other threads:[~2010-10-26 19:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 16:38 [Qemu-devel] Which qemu ports actually work? Torbjorn Granlund
2010-10-26 17:13 ` Alexander Graf
2010-10-26 19:02 ` Torbjorn Granlund [this message]
2010-10-26 19:25 ` Alexander Graf
2010-10-26 19:52 ` Torbjorn Granlund
2010-10-27 5:06 ` Alexander Graf
2010-10-27 8:39 ` Torbjorn Granlund
2010-10-27 8:51 ` Alexander Graf
2010-10-27 9:21 ` Torbjorn Granlund
2010-10-27 9:24 ` Alexander Graf
2010-10-27 9:33 ` Torbjorn Granlund
2010-10-27 9:31 ` [Qemu-devel] " Paolo Bonzini
2010-10-28 8:32 ` [Qemu-devel] " Torbjorn Granlund
2010-10-28 20:00 ` Alexander Graf
2010-10-27 20:44 ` Blue Swirl
2010-10-27 22:39 ` Torbjorn Granlund
2010-10-28 8:57 ` Artyom Tarasenko
2010-10-28 9:37 ` Torbjorn Granlund
2010-10-28 10:41 ` Artyom Tarasenko
2010-10-26 19:34 ` [Qemu-devel] " Paolo Bonzini
2010-10-26 21:02 ` Stefan Weil
2010-10-26 17:53 ` [Qemu-devel] " Stefan Weil
2010-10-26 19:12 ` Torbjorn Granlund
2010-10-26 19:35 ` [Qemu-devel] " Paolo Bonzini
2010-10-26 20:07 ` Torbjorn Granlund
2010-10-26 20:54 ` Stefan Weil
2010-10-26 21:11 ` Torbjorn Granlund
2010-10-26 21:09 ` Paolo Bonzini
2010-10-26 18:19 ` [Qemu-devel] Which qemu targets actually work? (was: Which qemu ports actually work?) Andreas Färber
2010-10-26 18:25 ` [Qemu-devel] Which qemu ports actually work? Blue Swirl
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=86r5fc22wx.fsf@shell.gmplib.org \
--to=tg@gmplib.org \
--cc=agraf@suse.de \
--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).