From: "Cédric Le Goater" <clg@kaod.org>
To: David Gibson <david@gibson.dropbear.id.au>,
Daniel Henrique Barboza <danielhb413@gmail.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/1] ppc/pnv.c: add a friendly warning when accel=kvm is used
Date: Fri, 26 Nov 2021 18:51:38 +0100 [thread overview]
Message-ID: <077efeac-3672-8b8f-dbe4-901c47c23eda@kaod.org> (raw)
In-Reply-To: <YaA0SIVnltlrarQZ@yekko>
On 11/26/21 02:11, David Gibson wrote:
> On Thu, Nov 25, 2021 at 07:42:02PM -0300, Daniel Henrique Barboza wrote:
>> If one tries to use -machine powernv9,accel=kvm in a Power9 host, a
>> cryptic error will be shown:
>>
>> qemu-system-ppc64: Register sync failed... If you're using kvm-hv.ko, only "-cpu host" is possible
>> qemu-system-ppc64: kvm_init_vcpu: kvm_arch_init_vcpu failed (0): Invalid argument
>>
>> Appending '-cpu host' will throw another error:
>>
>> qemu-system-ppc64: invalid chip model 'host' for powernv9 machine
>>
>> The root cause is that in IBM PowerPC we have different specs for the bare-metal
>> and the guests. The bare-metal follows OPAL, the guests follow PAPR. The kernel
>> KVM modules presented in the ppc kernels implements PAPR. This means that we
>> can't use KVM accel when using the powernv machine, which is the emulation of
>> the bare-metal host.
>>
>> All that said, let's give a more informative error in this case.
>>
>> Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
>> ---
>> hw/ppc/pnv.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/hw/ppc/pnv.c b/hw/ppc/pnv.c
>> index 71e45515f1..e5b87e8730 100644
>> --- a/hw/ppc/pnv.c
>> +++ b/hw/ppc/pnv.c
>> @@ -742,6 +742,11 @@ static void pnv_init(MachineState *machine)
>> DriveInfo *pnor = drive_get(IF_MTD, 0, 0);
>> DeviceState *dev;
>>
>> + if (kvm_enabled()) {
>> + error_report("The powernv machine does not work with KVM acceleration");
>> + exit(EXIT_FAILURE);
>> + }
>
>
> Hmm.. my only concern here is that powernv could, at least
> theoretically, work with KVM PR. I don't think it does right now,
> though.
At the same time, it is nice to not let the user think that it could work
in its current state. Don't you think so ?
C.
>
>> +
>> /* allocate RAM */
>> if (machine->ram_size < mc->default_ram_size) {
>> char *sz = size_to_str(mc->default_ram_size);
>
next prev parent reply other threads:[~2021-11-26 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 22:42 [PATCH 1/1] ppc/pnv.c: add a friendly warning when accel=kvm is used Daniel Henrique Barboza
2021-11-26 1:11 ` David Gibson
2021-11-26 17:51 ` Cédric Le Goater [this message]
2021-11-27 5:14 ` David Gibson
2021-11-29 21:09 ` Daniel Henrique Barboza
2021-11-30 0:14 ` David Gibson
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=077efeac-3672-8b8f-dbe4-901c47c23eda@kaod.org \
--to=clg@kaod.org \
--cc=danielhb413@gmail.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).