linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: linuxppc-dev@lists.ozlabs.org,
	Darren Stevens <darren@stevens-zone.net>,
	Pat Wall <pjwall@mac.com>, Pat Wall <pjwall@me.com>,
	Christian Zigotzky <info@xenosoft.de>,
	madskateman@gmail.com, "R.T.Dickinson" <rtd2@xtra.co.nz>,
	hypexed@yahoo.com.au
Subject: KVM: PPC: Book3E: KVM HV host module doesn't work anymore
Date: Wed, 18 Dec 2024 12:10:51 +0100	[thread overview]
Message-ID: <04e5da1a-65e2-ce12-27a5-5fdba9f0408d@xenosoft.de> (raw)
In-Reply-To: <f31e176f-200d-f96c-2971-4da0fe8f1245@xenosoft.de>

Hello,

The KVM HV host module doesn't work anymore since the PowerPC updates 
6.13-1 [1] and PowerPC MM updates [2].

We have tested it with our FSL P5020/P5040 boards [3].

The guest kernel doesn't boot. There is no output via the serial 
connection and no output via the graphics card. (QEMU)

It boots without the PowerPC updates 6.13-1 [1] and PowerPC MM updates [2].

Is the problem already known? Is there already a solution? I have seen 
many Book3S KVM HV updates. Have you perhaps forgotten Book3E?

Thanks,
Christian

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=42d9e8b7ccddee75989283cf7477305cfe3776ff
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5c00ff742bf5caf85f60e1c73999f99376fb865d
[3] http://wiki.amiga.org/index.php?title=X5000

-- 
Sent with BrassMonkey 33.4.0 (https://github.com/wicknix/brass-monkey/releases/tag/33.4.0)



       reply	other threads:[~2024-12-18 11:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <F693EFBE-3F0D-4B7C-89D8-EA8DCAB3CAB7@xenosoft.de>
     [not found] ` <6CC404E2-2442-47FE-877C-252B1F2872C2@xenosoft.de>
     [not found]   ` <f31e176f-200d-f96c-2971-4da0fe8f1245@xenosoft.de>
2024-12-18 11:10     ` Christian Zigotzky [this message]
2024-12-18 14:41       ` KVM: PPC: Book3E: KVM HV host module doesn't work anymore Christian Zigotzky
2024-12-20 12:08         ` Christian Zigotzky
2024-12-20 12:48           ` Christian Zigotzky
2024-12-22  8:55             ` Paolo Bonzini
2024-12-22 16:23               ` Christian Zigotzky
2024-12-22 17:52                 ` Paolo Bonzini
2024-12-23 14:41                   ` Christian Zigotzky
2024-12-23 15:37                     ` Paolo Bonzini
2024-12-24 11:05                       ` Christian Zigotzky
2024-12-24 11:42                         ` Paolo Bonzini
2024-12-25 12:48                           ` Christian Zigotzky
2024-12-26  7:00                             ` Paolo Bonzini
2024-12-26 14:26                               ` Christian Zigotzky
2024-12-27  5:20                                 ` Paolo Bonzini
2024-12-27 14:50                                   ` Christian Zigotzky
2024-12-28 15:04                                     ` Christian Zigotzky
2024-12-31 10:57                                     ` Christian Zigotzky
2025-01-01 13:30                                       ` Christian Zigotzky
2025-01-01 17:21                                         ` 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=04e5da1a-65e2-ce12-27a5-5fdba9f0408d@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=darren@stevens-zone.net \
    --cc=hypexed@yahoo.com.au \
    --cc=info@xenosoft.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madskateman@gmail.com \
    --cc=pjwall@mac.com \
    --cc=pjwall@me.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).