From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 215459] New: VM freezes starting with kernel 5.15
Date: Thu, 06 Jan 2022 11:03:50 +0000 [thread overview]
Message-ID: <bug-215459-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215459
Bug ID: 215459
Summary: VM freezes starting with kernel 5.15
Product: Virtualization
Version: unspecified
Kernel Version: 5.15.*
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: th3voic3@mailbox.org
Regression: No
Created attachment 300234
--> https://bugzilla.kernel.org/attachment.cgi?id=300234&action=edit
qemu.hook and libvirt xml
Hi,
starting with kernel 5.15 I'm experiencing freezes in my VFIO Windows 10 VM.
Downgrading to 5.14.16 fixes the issue.
I can't find any error messages in dmesg when this happens and comparing the
dmesg output between 5.14.16 and 5.15.7 didn't show any differences.
Additional info:
* 5.15.x
* I'm attaching my libvirt config and my /etc/libvirt/hooks/qemu
* My specs are:
** i7-10700k
** ASUS z490-A PRIME Motherboard
** 64 GB RAM
** Passthrough Card: NVIDIA 2070 Super
** Host is using the integrated Graphics chip
Steps to reproduce:
Boot any 5.15 kernel and start the VM and after some time (no specific trigger
as far as I can see) the VM freezes.
After some testing the solution seems to be:
I read about this:
20210713142023.106183-9-mlevitsk@redhat.com/#24319635">
https://patchwork.kernel.org/project/kvm/patch/20210713142023.106183-9-mlevitsk@redhat.com/#24319635
And so I checked
cat /sys/module/kvm_intel/parameters/enable_apicv
which returns Y to me by default.
So I added
options kvm_intel enable_apicv=0
to /etc/modprobe.d/kvm.conf
cat /sys/module/kvm_intel/parameters/enable_apicv
now returns N
So far I haven't encountered any freezes.
The confusing part is that APICv shouldn't be available with my CPU
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-01-06 11:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 11:03 bugzilla-daemon [this message]
2022-01-06 11:18 ` [Bug 215459] New: VM freezes starting with kernel 5.15 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
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@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;
as well as URLs for NNTP newsgroup(s).