From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH common/qemu-server v2 0/5] fix issues with viommu+vfio passthrough in #6608, #6378
Date: Tue, 2 Sep 2025 13:21:56 +0200 [thread overview]
Message-ID: <20250902112307.124706-1-d.kral@proxmox.com> (raw)
This exposes the intel-iommu and virtio-iommu's aw-bits option through
the machine conf property string to users to properly set the aw-bits
for the vIOMMU. This allows intel-iommu users to override the new
default value of 48 for host IOMMUs that have a maximum guest address
width less than 48 bits (e.g. 39, 41, or 46 bits for Intel
consumer-grade CPUs). Else they get the fatal error on startup:
vfio 0000:XX:YY.Z: Failed to set vIOMMU: aw-bits 48 > host aw-bits 39
Additionally, qemu-server #1, qemu-server #2-4 add warnings about the
above (qemu-server #4) and another error that users run into:
kvm: vfio_container_dma_map(0x5c9222494280, 0x380000000000, 0x10000, 0x78075ee70000) = -22 (Invalid argument)
See qemu-server #3 for more information for the latter.
pve-common.git:
Daniel Kral (1):
procfs: cpuinfo: expose x86_phys_bits and x86_virt_bits values
src/PVE/ProcFSTools.pm | 5 +++++
1 file changed, 5 insertions(+)
qemu-server.git:
Daniel Kral (4):
fix #6608: expose viommu driver aw-bits option
cpu config: factor out gathering common cpu properties
fix #6378 (continued): warn intel-iommu users about iommu and host aw
bits mismatch
machine: warn intel-iommu users about too large address width
src/PVE/QemuServer.pm | 16 ++-
src/PVE/QemuServer/CPUConfig.pm | 100 ++++++++++--------
src/PVE/QemuServer/Machine.pm | 50 ++++++++-
.../cfg2cmd/q35-viommu-intel-aw-bits.conf | 2 +
.../cfg2cmd/q35-viommu-intel-aw-bits.conf.cmd | 25 +++++
.../q35-viommu-intel-exceeding-aw-bits.conf | 4 +
...35-viommu-intel-exceeding-aw-bits.conf.cmd | 25 +++++
.../cfg2cmd/q35-viommu-virtio-aw-bits.conf | 2 +
.../q35-viommu-virtio-aw-bits.conf.cmd | 25 +++++
src/test/run_config2command_tests.pl | 8 ++
10 files changed, 208 insertions(+), 49 deletions(-)
create mode 100644 src/test/cfg2cmd/q35-viommu-intel-aw-bits.conf
create mode 100644 src/test/cfg2cmd/q35-viommu-intel-aw-bits.conf.cmd
create mode 100644 src/test/cfg2cmd/q35-viommu-intel-exceeding-aw-bits.conf
create mode 100644 src/test/cfg2cmd/q35-viommu-intel-exceeding-aw-bits.conf.cmd
create mode 100644 src/test/cfg2cmd/q35-viommu-virtio-aw-bits.conf
create mode 100644 src/test/cfg2cmd/q35-viommu-virtio-aw-bits.conf.cmd
Summary over all repositories:
11 files changed, 213 insertions(+), 49 deletions(-)
--
Generated by git-murpp 0.8.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-09-02 11:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 11:21 Daniel Kral [this message]
2025-09-02 11:21 ` [pve-devel] [PATCH common v2 1/1] procfs: cpuinfo: expose x86_phys_bits and x86_virt_bits values Daniel Kral
2025-09-05 9:10 ` Fiona Ebner
2025-09-05 11:47 ` Daniel Kral
2025-09-02 11:21 ` [pve-devel] [PATCH qemu-server v2 1/4] fix #6608: expose viommu driver aw-bits option Daniel Kral
2025-09-05 10:07 ` Fiona Ebner
2025-09-05 11:45 ` Daniel Kral
2025-09-05 12:00 ` Fiona Ebner
2025-09-05 14:18 ` Daniel Kral
2025-09-02 11:21 ` [pve-devel] [PATCH qemu-server v2 2/4] cpu config: factor out gathering common cpu properties Daniel Kral
2025-09-05 10:32 ` Fiona Ebner
2025-09-02 11:22 ` [pve-devel] [RFC qemu-server v2 3/4] fix #6378 (continued): warn intel-iommu users about iommu and host aw bits mismatch Daniel Kral
2025-09-02 11:26 ` Daniel Kral
2025-09-05 10:50 ` Fiona Ebner
2025-09-05 11:38 ` Daniel Kral
2025-09-05 12:52 ` Fiona Ebner
2025-09-02 11:22 ` [pve-devel] [RFC qemu-server v2 4/4] machine: warn intel-iommu users about too large address width Daniel Kral
2025-09-05 10:55 ` Fiona Ebner
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=20250902112307.124706-1-d.kral@proxmox.com \
--to=d.kral@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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