All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 215459] VM freezes starting with kernel 5.15
Date: Thu, 06 Jan 2022 21:12:17 +0000	[thread overview]
Message-ID: <bug-215459-28872-kAqeFxqe9P@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215459-28872@https.bugzilla.kernel.org/>

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

--- Comment #6 from th3voic3@mailbox.org ---
(In reply to Sean Christopherson from comment #4)
> The fix Maxim is referring to is commit fdba608f15e2 ("KVM: VMX: Wake vCPU
> when delivering posted IRQ even if vCPU == this vCPU").  But the buggy
> commit was introduced back in v5.8, so it's unlikely that's the issue, or at
> least that it's the only issue.  And assuming the VM in question has
> multiple vCPUs (which I'm pretty sure is true based on the config), that bug
> is unlikely to cause the entire VM to freeze; the expected symptom is that a
> vCPU isn't awakened when it should be, and while it's possible multiple
> vCPUs could get unlucky, taking down the entire VM is highly improbable. 
> That said, it's worth trying that fix, I'm just not very optimistic :-)
> 
> Assuming this is something different, the biggest relevant changes in v5.15
> are that the TDP MMU is enabled by default, and that the APIC access page
> memslot is not deleted when APICv is inhibited.
> 
> Can you try disabling the TDP MMU with APICv still enabled?  KVM allows that
> to be toggled without unloading, e.g. "echo N | sudo tee
> /sys/module/kvm/parameters/tdp_mmu", the VM just needs to be started after
> the param is toggled.

I enabled APICv again and toggled the setting and did a quick test. I tested a
couple of things that often caused freezes. So far so good. Now I've added the
toggle to my qemu hooks prepare section and will do further testing. 

Thanks for the input so far

-- 
You may reply to this email to add a comment.

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

  parent reply	other threads:[~2022-01-06 21:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 11:03 [Bug 215459] New: VM freezes starting with kernel 5.15 bugzilla-daemon
2022-01-06 11:18 ` Maxim Levitsky
2022-01-06 11:18 ` [Bug 215459] " bugzilla-daemon
2022-01-06 13:12 ` bugzilla-daemon
2022-01-06 13:43   ` Maxim Levitsky
2022-01-06 13:43 ` bugzilla-daemon
2022-01-06 18:52 ` bugzilla-daemon
2022-01-06 20:42   ` Maxim Levitsky
2022-01-06 20:42 ` bugzilla-daemon
2022-01-06 21:12 ` bugzilla-daemon [this message]
2022-01-07  8:52 ` bugzilla-daemon
2022-01-07 10:08 ` bugzilla-daemon
2022-01-10  9:30 ` bugzilla-daemon
2022-01-10 22:29   ` Maxim Levitsky
2022-01-10 22:29 ` bugzilla-daemon
2022-01-11  8:29 ` bugzilla-daemon
2023-01-27 13:11 ` 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-215459-28872-kAqeFxqe9P@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.