public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 220057] Kernel regression. Linux VMs crashing (I did not test Windows guest VMs)
Date: Fri, 02 May 2025 22:52:28 +0000	[thread overview]
Message-ID: <bug-220057-28872-1sWVB9j6gI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220057-28872@https.bugzilla.kernel.org/>

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

--- Comment #46 from Alex Williamson (alex.williamson@redhat.com) ---
Thanks for the prompt testing, I've posted the fix without the debug logging
here:

https://lore.kernel.org/all/20250502224035.3183451-1-alex.williamson@redhat.com/

Pending reviews and comments, I'll try to get it in for v6.15 for backport to
stable trees.

The VFIO_MAP_DMA failures are a VM configuration error and a byproduct that
Intel ships platforms where the CPU physical address width is different from
the IOMMU address width.  QEMU/vBIOS defines the MMIO layout relative to the
CPU address width, therefore the vCPU needs to reflect that address width
restriction.  QEMU makes this configuration available though a guest_phys_bits
option, but it doesn't appear that Proxmox provides a way to configure this. 
The result is these error logs, which indicate P2P DMA mappings are not being
created.  With the fix we're pursuing above, this should not result in a
performance/efficiency loss relative to the page table use though.

-- 
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:[~2025-05-02 22:52 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-27  0:46 [Bug 220057] New: Kernel regression. Linux VMs crashing (I did not test Windows guest VMs) bugzilla-daemon
2025-04-27  0:48 ` [Bug 220057] " bugzilla-daemon
2025-04-27  0:50 ` bugzilla-daemon
2025-04-27 23:34 ` bugzilla-daemon
2025-04-28  0:00 ` bugzilla-daemon
2025-04-28  7:18 ` bugzilla-daemon
2025-04-28  8:25 ` bugzilla-daemon
2025-04-28 15:10 ` bugzilla-daemon
2025-04-28 19:41 ` bugzilla-daemon
2025-04-28 21:11 ` bugzilla-daemon
2025-04-28 21:22 ` bugzilla-daemon
2025-04-28 21:24 ` bugzilla-daemon
2025-04-28 21:26 ` bugzilla-daemon
2025-04-28 21:39 ` bugzilla-daemon
2025-04-28 21:42 ` bugzilla-daemon
2025-04-28 21:49 ` bugzilla-daemon
2025-04-28 22:15 ` bugzilla-daemon
2025-04-28 22:27 ` bugzilla-daemon
2025-04-28 22:29 ` bugzilla-daemon
2025-04-28 22:31 ` bugzilla-daemon
2025-04-28 22:46 ` bugzilla-daemon
2025-04-28 23:05 ` bugzilla-daemon
2025-04-29  6:54 ` bugzilla-daemon
2025-04-29  8:08 ` bugzilla-daemon
2025-04-29  8:09 ` bugzilla-daemon
2025-04-29  8:14 ` bugzilla-daemon
2025-04-29 14:58 ` bugzilla-daemon
2025-04-29 15:02 ` bugzilla-daemon
2025-04-29 15:09 ` bugzilla-daemon
2025-04-29 15:15 ` bugzilla-daemon
2025-04-29 15:18 ` bugzilla-daemon
2025-04-29 15:22 ` bugzilla-daemon
2025-04-29 15:25 ` bugzilla-daemon
2025-04-29 15:35 ` bugzilla-daemon
2025-04-29 18:36 ` bugzilla-daemon
2025-04-29 20:09 ` bugzilla-daemon
2025-04-30  0:20 ` bugzilla-daemon
2025-04-30  0:41 ` bugzilla-daemon
2025-04-30  7:32 ` bugzilla-daemon
2025-04-30 22:33 ` bugzilla-daemon
2025-05-01  9:05 ` bugzilla-daemon
2025-05-01 14:42 ` bugzilla-daemon
2025-05-01 15:03 ` bugzilla-daemon
2025-05-01 15:21 ` bugzilla-daemon
2025-05-01 15:28 ` bugzilla-daemon
2025-05-02 16:12 ` bugzilla-daemon
2025-05-02 17:15 ` bugzilla-daemon
2025-05-02 22:52 ` bugzilla-daemon [this message]
2025-05-02 23:06 ` bugzilla-daemon
2025-05-06  9:47 ` bugzilla-daemon
2025-05-06  9:57 ` 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-220057-28872-1sWVB9j6gI@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