From: Paul Mackerras <paulus@ozlabs.org>
To: joserz@linux.vnet.ibm.com
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au,
oohall@gmail.com
Subject: Re: KVM guests freeze under upstream kernel
Date: Thu, 20 Jul 2017 15:21:59 +1000 [thread overview]
Message-ID: <20170720052159.GB8602@fergus.ozlabs.ibm.com> (raw)
In-Reply-To: <20170720030222.GA21034@pacoca>
On Thu, Jul 20, 2017 at 12:02:23AM -0300, joserz@linux.vnet.ibm.com wrote:
> On Thu, Jul 20, 2017 at 09:42:50AM +1000, Benjamin Herrenschmidt wrote:
> > On Wed, 2017-07-19 at 16:46 -0300, joserz@linux.vnet.ibm.com wrote:
> > > Hello!
> > >
> > > We're not able to boot any KVM guest using upstream kernel (cb8c65ccff7f77d0285f1b126c72d37b2572c865 - 4.13.0-rc1+).
> > > After reaching the SLOF initial counting, the guest simply freezes:
> >
> > Can you send our .config ?
>
> Sure,
>
> Answering Michael as well:
>
> It's a P9 with RHEL kernel 4.11.0-10.el7a.ppc64le installed. The problem
> was noticed with kernel > 4.13 (I'm currently running 4.13.0-rc1+).
>
> QEMU is https://github.com/dgibson/qemu (ppc-for-2.10) but I gave the
> default packaged Qemu a try.
>
> For the guest, I tried both a vanilla Ubuntu 17.04 and the host kernel.
> But they had never a chance to run since the freezing happened in SLOF.
>
> Note that using the 4.11.0-10.el7a.ppc64le kernel it works fine
> (for any of these Qemu/Guest setup). With 4.13.0-rc1 I have it run after
> reverting that referred commit.
Is the host kernel running in radix mode?
Did you check the host kernel logs for any oops messages?
Paul.
next prev parent reply other threads:[~2017-07-20 5:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 19:46 KVM guests freeze under upstream kernel joserz
2017-07-19 22:31 ` Michael Ellerman
2017-07-19 23:42 ` Benjamin Herrenschmidt
2017-07-20 3:02 ` joserz
2017-07-20 5:21 ` Paul Mackerras [this message]
2017-07-21 1:18 ` joserz
2017-07-26 13:18 ` joserz
2017-07-27 3:14 ` Michael Ellerman
2017-07-27 6:56 ` Suraj Jitindar Singh
2017-07-27 11:10 ` Michael Ellerman
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=20170720052159.GB8602@fergus.ozlabs.ibm.com \
--to=paulus@ozlabs.org \
--cc=benh@kernel.crashing.org \
--cc=joserz@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=oohall@gmail.com \
/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).