linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Alexander Graf <agraf@suse.de>,
	"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>
Cc: Darren Stevens <darren@stevens-zone.net>,
	"R.T.Dickinson" <rtd2@xtra.co.nz>,
	Christian Zigotzky <info@xenosoft.de>
Subject: Re: PowerPC KVM-PR issue
Date: Wed, 10 Jun 2020 13:23:28 +0200	[thread overview]
Message-ID: <7e859f68-9455-f98f-1fa3-071619fa1731@xenosoft.de> (raw)
In-Reply-To: <cf99a8c0-3bad-d089-de54-e02d3dba7f72@xenosoft.de>

On 10 June 2020 at 11:06 am, Christian Zigotzky wrote:
> On 10 June 2020 at 00:18 am, Christian Zigotzky wrote:
>> Hello,
>>
>> KVM-PR doesn't work anymore on my Nemo board [1]. I figured out that 
>> the Git kernels and the kernel 5.7 are affected.
>>
>> Error message: Fienix kernel: kvmppc_exit_pr_progint: emulation at 
>> 700 failed (00000000)
>>
>> I can boot virtual QEMU PowerPC machines with KVM-PR with the kernel 
>> 5.6 without any problems on my Nemo board.
>>
>> I tested it with QEMU 2.5.0 and QEMU 5.0.0 today.
>>
>> Could you please check KVM-PR on your PowerPC machine?
>>
>> Thanks,
>> Christian
>>
>> [1] https://en.wikipedia.org/wiki/AmigaOne_X1000
>
> I figured out that the PowerPC updates 5.7-1 [1] are responsible for 
> the KVM-PR issue. Please test KVM-PR on your PowerPC machines and 
> check the PowerPC updates 5.7-1 [1].
>
> Thanks
>
> [1] 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d38c07afc356ddebaa3ed8ecb3f553340e05c969
>
>
I tested the latest Git kernel with Mac-on-Linux/KVM-PR today. 
Unfortunately I can't use KVM-PR with MoL anymore because of this issue 
(see screenshots [1]). Please check the PowerPC updates 5.7-1.

Thanks

[1]
- 
https://i.pinimg.com/originals/0c/b3/64/0cb364a40241fa2b7f297d4272bbb8b7.png
- 
https://i.pinimg.com/originals/9a/61/d1/9a61d170b1c9f514f7a78a3014ffd18f.png


  reply	other threads:[~2020-06-10 11:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 14:16 Boot issue with the latest Git kernel Christian Zigotzky
2020-06-04 14:26 ` Christophe Leroy
2020-06-04 14:29   ` Christophe Leroy
2020-06-04 15:46     ` Christian Zigotzky
2020-06-04 15:53     ` Christian Zigotzky
2020-06-04 17:15       ` Christophe Leroy
2020-06-05 16:23         ` Christian Zigotzky
2020-06-07 13:27           ` Christian Zigotzky
2020-06-07 14:07           ` Aneesh Kumar K.V
2020-06-09 22:18             ` PowerPC KVM-PR issue Christian Zigotzky
2020-06-10  9:06               ` Christian Zigotzky
2020-06-10 11:23                 ` Christian Zigotzky [this message]
2020-06-11 14:47                   ` Christian Zigotzky
2020-06-12 13:01                     ` Christian Zigotzky
2020-06-14  8:50                       ` Nicholas Piggin
2020-06-14 12:53                       ` Nicholas Piggin
2020-06-14 14:52                         ` Christian Zigotzky
2020-06-14 23:39                           ` Christian Zigotzky
2020-06-15  7:34                             ` Christian Zigotzky
2020-06-25  9:38                             ` Christian Zigotzky

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=7e859f68-9455-f98f-1fa3-071619fa1731@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=agraf@suse.de \
    --cc=darren@stevens-zone.net \
    --cc=info@xenosoft.de \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=rtd2@xtra.co.nz \
    /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).