From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 209079] CPU 0/KVM: page allocation failure on 5.8 kernel
Date: Thu, 10 Sep 2020 15:33:27 +0000 [thread overview]
Message-ID: <bug-209079-28872-cxUtvigYDo@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209079-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209079
Martin Schrodt (kernel@martin.schrodt.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |OBSOLETE
--- Comment #3 from Martin Schrodt (kernel@martin.schrodt.org) ---
Damn.
I did some changes to the VM in the last few days, to make it support AVIC and
that made me change the kvm module parameters, without remembering what they
were before. They are now
> options kvm ignore_msrs=1 report_ignored_msrs=0
> options kvm_amd nested=0 avic=1 npt=1
and Seans post mentioning NPT having to be disabled for the bug to occur, I
updated the kernel again (to 5.8.7), and voilà, the VM works.
So I have to concur that it really was disabled before, but I can't remember
why I did so, maybe because of some bug that only existed when I setup the VM
somewhen in 2018.
Regarding GFP_DMA32, I don't know what it really means. Might be related to me
passing through a GPU, an NVME drive and a USB controller to the VM.
So I guess I'll leave learning how to bisect to my next future incident...
Thank you guys for all the work you do - Linux forever!
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-09-10 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 15:22 [Bug 209079] New: CPU 0/KVM: page allocation failure on 5.8 kernel bugzilla-daemon
2020-09-09 6:00 ` [Bug 209079] " bugzilla-daemon
2020-09-09 6:41 ` bugzilla-daemon
2020-09-10 15:33 ` bugzilla-daemon [this message]
2020-09-10 16:21 ` bugzilla-daemon
2020-09-10 21:03 ` bugzilla-daemon
2020-09-11 16:19 ` bugzilla-daemon
2020-09-20 9:17 ` bugzilla-daemon
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=bug-209079-28872-cxUtvigYDo@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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