From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 209333] New: VM not starting anymore with 5.8.8 - lots of page faults
Date: Sun, 20 Sep 2020 08:37:16 +0000 [thread overview]
Message-ID: <bug-209333-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=209333
Bug ID: 209333
Summary: VM not starting anymore with 5.8.8 - lots of page
faults
Product: Virtualization
Version: unspecified
Kernel Version: 5.8.8
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: kernel@martin.schrodt.org
Regression: No
Host system is a Threadripper 1920x on a X399 Motherboard.
I have a VM here, that I pass through a Samsung 960 EVO SSD.
> 08:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD
> Controller SM961/PM961
The VM starts up and works fine with Kernel 5.8.7, and when I start the VM with
a 5.8.8 kernel, libvirt/QEMU say the VM is started, but it doesn't come up, and
I see lots and lots of these in dmesg:
> AMD-Vi: Event logged [IO_PAGE_FAULT device=08:00.0 domain=0x002c
> address=0xfffffffdf8000000 flags=0x0008]
Now, one thing to mention is that the VM uses AMD AVIC to directly deliver
interrupts to the VM.
There are 2 IOMMU related changes in the 5.8.8 changelog that seem likely for
the layman that I am, both by Suravee Suthikulpanit from AMD:
iommu/amd: Use cmpxchg_double() when updating 128-bit IRTE
iommu/amd: Restore IRTE.RemapEn bit after programming IRTE
I observe the same behaviour with 5.8.10.
Happy to provide more info if needed!
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2020-09-20 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 8:37 bugzilla-daemon [this message]
2020-09-20 8:38 ` [Bug 209333] VM not starting anymore with 5.8.8 - lots of page faults bugzilla-daemon
2020-09-20 8:39 ` bugzilla-daemon
2020-09-21 10:00 ` bugzilla-daemon
2020-09-25 16:06 ` 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-209333-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