From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 218259] High latency in KVM guests
Date: Thu, 14 Dec 2023 07:14:57 +0000 [thread overview]
Message-ID: <bug-218259-28872-UltznLAvHS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218259-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218259
--- Comment #2 from Joern Heissler (kernelbugs2012@joern-heissler.de) ---
Hi,
1. KSM is already disabled. Didn't try to enable it.
2. NUMA autobalancing was enabled on the host (value 1), not in the guest. When
disabled, I can't see the issue anymore.
3. tdp_mmu was "Y", disabling it seems to make no difference.
So might be related to NUMA. On older kernels, the flag is 1 as well.
There's one difference in the kernel messages that I hadn't noticed before. The
newer one prints "pci_bus 0000:7f: Unknown NUMA node; performance will be
reduced" (same with ff again). The older ones don't. No idea what this means,
if it's important, and can't find info on the web regarding it.
I think the kernel is preemptible:
"uname -a" shows: "Linux vm123 6.1.0-15-amd64 #1 SMP PREEMPT_DYNAMIC Debian
6.1.66-1 (2023-12-09) x86_64 GNU/Linux"
"grep -i" on the config shows:
CONFIG_PREEMPT_BUILD=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_COUNT=y
CONFIG_PREEMPTION=y
CONFIG_PREEMPT_DYNAMIC=y
CONFIG_PREEMPT_RCU=y
CONFIG_HAVE_PREEMPT_DYNAMIC=y
CONFIG_HAVE_PREEMPT_DYNAMIC_CALL=y
CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_DRM_I915_PREEMPT_TIMEOUT=640
# CONFIG_DEBUG_PREEMPT is not set
# CONFIG_PREEMPT_TRACER is not set
# CONFIG_PREEMPTIRQ_DELAY_TEST is not set
Attaching output of "dmesg" and "lspci -v". Perhaps there's something useful in
there.
--
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 prev parent reply other threads:[~2023-12-14 7:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 16:37 [Bug 218259] New: High latency in KVM guests bugzilla-daemon
2023-12-13 16:54 ` Sean Christopherson
2023-12-13 16:54 ` [Bug 218259] " bugzilla-daemon
2023-12-14 7:14 ` bugzilla-daemon [this message]
2023-12-18 17:07 ` Sean Christopherson
2023-12-14 7:15 ` bugzilla-daemon
2023-12-14 7:16 ` bugzilla-daemon
2023-12-18 17:07 ` bugzilla-daemon
2024-01-11 15:55 ` Sean Christopherson
2023-12-19 14:09 ` bugzilla-daemon
2023-12-19 15:16 ` Sean Christopherson
2023-12-19 15:16 ` bugzilla-daemon
2024-01-11 15:55 ` bugzilla-daemon
2024-01-16 13:29 ` bugzilla-daemon
2024-01-17 1:05 ` Sean Christopherson
2024-01-17 1:05 ` bugzilla-daemon
2024-01-17 14:04 ` bugzilla-daemon
2024-11-05 0:27 ` 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-218259-28872-UltznLAvHS@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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