qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Bharata B Rao <bharata@linux.vnet.ibm.com>, qemu-ppc@nongnu.org
Cc: David Gibson <david@gibson.dropbear.id.au>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] pseries machine does not like older CPUs anymore
Date: Tue, 28 Jun 2016 09:29:33 +0200	[thread overview]
Message-ID: <5772275D.8090400@redhat.com> (raw)


 Hi Bharata,

there seems to be a regression with current QEMU master: The pseries
machine does not work with older 64-bit ppc CPUs anymore. With QEMU
2.6.0, it is possible to run:

 qemu-system-ppc64 -nographic -M pseries -cpu 970

or

 qemu-system-ppc64 -nographic -M pseries -cpu POWER5+

but with QEMU master, I now only get a "Unable to find sPAPR CPU Core
definition" error message and then QEMU quits.

At a quick glance, this seems to be related to the new CPU hotplug
code... so could you maybe have a look?

 Thanks,
  Thomas

             reply	other threads:[~2016-06-28  7:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28  7:29 Thomas Huth [this message]
2016-06-28  7:58 ` [Qemu-devel] pseries machine does not like older CPUs anymore Bharata B Rao

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=5772275D.8090400@redhat.com \
    --to=thuth@redhat.com \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --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).