From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>
Cc: Darren Stevens <darren@stevens-zone.net>,
mad skateman <madskateman@gmail.com>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: [FSL P50x0] KVM HV doesn't work anymore
Date: Sat, 15 May 2021 11:48:16 +0200 [thread overview]
Message-ID: <34617b1b-e213-668b-05f6-6fce7b549bf0@xenosoft.de> (raw)
In-Reply-To: <04526309-4653-3349-b6de-e7640c2258d6@xenosoft.de>
Hi All,
I bisected today [1] and the bisecting itself was OK but the reverting
of the bad commit doesn't solve the issue. Do you have an idea which
commit could be resposible for this issue? Maybe the bisecting wasn't
successful. I will look in the kernel git log. Maybe there is a commit
that affected KVM HV on FSL P50x0 machines.
Thanks,
Christian
[1] https://forum.hyperion-entertainment.com/viewtopic.php?p=53209#p53209
On 14 May 2021 at 10:10 am, Christian Zigotzky wrote:
> Hi All,
>
> The RC1 of kernel 5.13 doesn't boot in a virtual e5500 QEMU machine
> with KVM HV anymore. I see in the serial console that the uImage
> doesn't load. I use the following QEMU command for booting:
>
> qemu-system-ppc64 -M ppce500 -cpu e5500 -enable-kvm -m 1024 -kernel
> uImage-5.13 -drive
> format=raw,file=MintPPC32-X5000.img,index=0,if=virtio -netdev
> user,id=mynet0 -device e1000,netdev=mynet0 -append "rw root=/dev/vda"
> -device virtio-vga -device virtio-mouse-pci -device
> virtio-keyboard-pci -device pci-ohci,id=newusb -device
> usb-audio,bus=newusb.0 -smp 4
>
> The kernel boots without KVM HV.
>
> Have you already tested KVM HV with the kernel 5.13?
>
> Thanks,
> Christian
>
>
next prev parent reply other threads:[~2021-05-15 9:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 8:10 [FSL P50x0] KVM HV doesn't work anymore Christian Zigotzky
2021-05-15 9:48 ` Christian Zigotzky [this message]
2021-05-15 10:08 ` Christophe Leroy
2021-05-15 13:46 ` Christian Zigotzky
2021-05-17 7:42 ` Nicholas Piggin
2021-05-17 9:42 ` Christian Zigotzky
2021-05-18 6:33 ` Christian Zigotzky
2021-05-19 7:57 ` Nicholas Piggin
2021-05-19 11:52 ` Christian Zigotzky
2021-05-19 23:07 ` Nicholas Piggin
2021-05-30 6:49 ` Christian Zigotzky
2021-06-02 11:26 ` Christian Zigotzky
2021-06-07 7:21 ` Christian Zigotzky
2021-06-11 2:24 ` Nicholas Piggin
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=34617b1b-e213-668b-05f6-6fce7b549bf0@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=darren@stevens-zone.net \
--cc=info@xenosoft.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madskateman@gmail.com \
--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).