From: "Andreas Färber" <afaerber@suse.de>
To: Markus Armbruster <armbru@redhat.com>, Alexander Graf <agraf@suse.de>
Cc: "Hervé Poussineau" <hpoussin@reactos.org>,
qemu-ppc <qemu-ppc@nongnu.org>,
qemu-devel@nongnu.org, "Anthony Liguori" <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] For all targets and machine types: "start to monitor" smoke test
Date: Tue, 07 Aug 2012 22:34:52 +0200 [thread overview]
Message-ID: <50217BEC.907@suse.de> (raw)
In-Reply-To: <87obmmcxlh.fsf@blackfin.pond.sub.org>
Am 07.08.2012 21:26, schrieb Markus Armbruster:
> Very basic smoke test: start QEMU with -monitor stdio, quit immediately.
[...]
> Summary of results:
>
> * Bad unexplained
[...]
> qemu-system-ppc64 prep
> qemu: hardware error: Unknown device 'i82378' for bus 'PCI'
This is an untested configuration, none of the PReP machines I know are
64-bit. Alex wants all ppc machines in ppc64 for convenience though.
It sounds like CONFIG_I82378=y in default-configs/ppc64-softmmu.mak
would fix this.
> qemu-system-ppcemb ref405ep
> qemu-system-ppcemb taihu
> Unable to find PowerPC 405ep CPU definition
Alex?
> qemu-system-ppcemb mac99
> qemu-system-ppcemb g3beige
> qemu-system-ppcemb prep
> Unable to find PowerPC CPU definition
These three are not embedded CPUs so the error seems correct.
Alex, should we suppress the desktop machines for ppcemb?
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-08-07 20:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 19:26 [Qemu-devel] For all targets and machine types: "start to monitor" smoke test Markus Armbruster
2012-08-07 19:35 ` Anthony Liguori
2012-08-07 19:55 ` Markus Armbruster
2012-08-07 20:05 ` Peter Maydell
2012-08-07 20:30 ` Markus Armbruster
2012-08-07 20:37 ` Eric Blake
2012-08-08 7:50 ` Markus Armbruster
2012-08-08 8:03 ` Peter Maydell
2012-08-08 8:29 ` Markus Armbruster
2012-08-07 19:42 ` Peter Maydell
2012-08-08 7:22 ` Markus Armbruster
2012-08-10 1:29 ` Peter Crosthwaite
2012-08-07 20:34 ` Andreas Färber [this message]
2012-08-08 7:27 ` Markus Armbruster
2012-08-08 12:22 ` Markus Armbruster
2012-08-07 21:06 ` Blue Swirl
2012-08-08 7:39 ` Markus Armbruster
2012-08-08 19:34 ` Blue Swirl
2012-08-08 7:38 ` Max Filippov
2012-08-08 8:31 ` Markus Armbruster
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=50217BEC.907@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=hpoussin@reactos.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).