All of lore.kernel.org
 help / color / mirror / Atom feed
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 21:03:42 +0000	[thread overview]
Message-ID: <bug-209079-28872-rMRH9f2z0d@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209079-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=209079

--- Comment #5 from Martin Schrodt (kernel@martin.schrodt.org) ---
Strange things happen sometimes...

What I did (I did only unload/reload the module after config changes, hoping
this would suffice):

- running with "kvm_amd nested=0 avic=1 npt=0" and "kvm_amd nested=0 npt=0" on
5.8.7, all working fine.

- rolling back to the 5.8.5 kernel I had the bug with, and trying the above
combinations -> working fine

- rolling the VM back to a state before changing it to AVIC (reasonably sure
it's the same) -> working fine, on both 5.8.7 and 5.8.5.

Heisenbugs here they come.

Trying to come up with things that I changed since then but did not roll back
yet:

I have a qemu hook, which did the following: 

1) drop caches, 
2) compact memory 
3) create a cpuset for the host and move all tasks there to free the cores
assigned to the VM (which included a flag for memory migration, so that the
processes would have their memory moved to the non VM node) 
4) then let qemu allocate memory

Since then I changed this to move the compacting step after the moving step (my
thought was that *after* moving the memory from node 1 to node 0, there is more
free space on node 1, compaction should yield better results)

Does the error I initially got say anything about *why* the allocation failed?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-09-10 21:04 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
2020-09-10 16:21 ` bugzilla-daemon
2020-09-10 21:03 ` bugzilla-daemon [this message]
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-rMRH9f2z0d@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 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.