From: Greg Kurz <groug@kaod.org>
To: qemu-devel@nongnu.org
Subject: [Bug 1853083] Re: qemu ppc64 4.0 boot AIX5.1 hung
Date: Wed, 20 Nov 2019 09:22:10 -0000 [thread overview]
Message-ID: <157424173100.22292.11046728314953589871.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 157413352600.6824.7282626865462030571.malonedeb@gac.canonical.com
Answering comment #4:
> What I don't understand is ppc64 for IBM machine emulation, but qemu ppc64
> can't support AIX most of the time, but can support Linux on power very well.
QEMU doesn't implement the full PAPR specification. Historically we've only
added the bits that are essential for a Linux guest to be happy.
AIX 5.1 is fairly old and neither IBM, nor the QEMU community invested time
and effort in getting it to work under QEMU. AIX being a closed source OS
certainly didn't help things to go forward.
Things have changed recently though. IBM added virtio drivers and some
workarounds to AIX, as well some fixes to QEMU. Latest AIX 7.2 releases
should now be able to run under QEMU with a POWER8 or newer CPU model.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1853083
Title:
qemu ppc64 4.0 boot AIX5.1 hung
Status in QEMU:
Incomplete
Bug description:
When boot AIX5.1 from cdrom device, qemu hung there, no further info
is displayed and cpu consumption is high.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1853083/+subscriptions
next prev parent reply other threads:[~2019-11-20 9:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 3:18 [Bug 1853083] [NEW] qemu ppc64 4.0 boot AIX5.1 hung wzis
2019-11-19 7:50 ` [Bug 1853083] " Philippe Mathieu-Daudé
2019-11-19 8:33 ` wzis
2019-11-19 8:35 ` Thomas Huth
2019-11-19 9:41 ` wzis
2019-11-20 5:53 ` wzis
2019-11-20 5:56 ` wzis
2019-11-20 6:46 ` Thomas Huth
2019-11-20 8:17 ` wzis
2019-11-20 8:18 ` wzis
2019-11-20 8:41 ` wzis
2019-11-20 9:22 ` Greg Kurz [this message]
2020-01-20 4:17 ` Launchpad Bug Tracker
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=157424173100.22292.11046728314953589871.malone@chaenomeles.canonical.com \
--to=groug@kaod.org \
--cc=1853083@bugs.launchpad.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.