All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Wayne Li <waynli329@gmail.com>, qemu-devel@nongnu.org
Subject: Re: QEMU VM crashes when enabling KVM
Date: Thu, 12 Dec 2019 02:16:33 +0100	[thread overview]
Message-ID: <76b207cd-09ce-b3df-e288-a515df40677e@redhat.com> (raw)
In-Reply-To: <CAM2K0nrhkOhiJDxnANGmAu2140-TP0a9pY58i_PN1k9xAWGz9A@mail.gmail.com>

On 11/12/19 22:23, Wayne Li wrote:
> 
> Now I am fairly sure KVM is actually enabled on the system.  Finding
> that out was another story that spanned a couple of months.  But long
> story short, lsmod doesn't show that the KVM kernel module is running. 
> But that's because KVM is built-in and it can't actually be built as a
> loadable kernel module in this particular system.
> 
> So I'm not really sure what could be the problem.  Though I was thinking
> if I understood the error better that might help?  Following the code I
> see that the "Missing PVR setting capability." is called when a variable
> called "cap_segstate" is 0:
> 
> if (!cap_segstate) {
>             fprintf(stderr, "kvm error: missing PVR setting capability\n");
>             return -ENOSYS;
> }
> 
> And the cap_segstate variable is set by the following function:
> 
> cap_segstate = kvm_check_extension(s, KVM_CAP_PPC_SEGSTATE);

You are not saying how you are running QEMU.  I think you are using a
CPU model that requires a Book3S KVM.

Paolo



  reply	other threads:[~2019-12-12  1:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 21:23 QEMU VM crashes when enabling KVM Wayne Li
2019-12-12  1:16 ` Paolo Bonzini [this message]
2019-12-12  1:59   ` Wayne Li
2019-12-12  7:17     ` Paolo Bonzini
2019-12-12 16:40       ` Wayne Li
2019-12-12 18:57         ` BALATON Zoltan
2019-12-13  3:49         ` David Gibson
2019-12-13 18:36           ` Wayne Li

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=76b207cd-09ce-b3df-e288-a515df40677e@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=waynli329@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.