From: Markus Frank <m.frank@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH qemu-server/docs/manager v8 0/4] vIOMMU-Feature #3784
Date: Wed, 24 Jan 2024 10:49:14 +0100 [thread overview]
Message-ID: <20240124094918.260222-1-m.frank@proxmox.com> (raw)
overall change in v8:
* rebase to master
I was able to clarify any ambiguity regarding vIOMMU:
https://lists.gnu.org/archive/html/qemu-devel/2023-10/msg02370.html
The iommu_platform parameter could be made an optional parameter for VirtIO
devices to add more isolation (with the downside of making them less performant)
in a follow-up patch series.
qemu-server:
v8:
* removed kvm variable since the check does not exist anymore
v7:
* changed viommu to string and added virtio-iommu implementation
* seperated "machine as property-string" patch from "fix #3784" patch
* moved format definition/parsing/printing to QemuServer::Machine
* merged test-cases into "fix #3784" patch
* removed kvm check, since it does not prevent vIOMMU from working
(only nested virtualization requires kvm & host cpu)
v6:
* added helper function for machine config validation
* replaced old standard option for "pve-qemu-machine" to new property string
v5:
* set $kvm to 1 if is_native, so that api kvm check works.
v4:
* added kvm/q35 checks in API
* reused pve-qemu-machine
v3:
* replaced old machine type with property-string with viommu-parameter
v2:
* moved viommu-parameter inside of machine_fmt and added it the new
parameter machine_properties
new Config -> machine_properties: viommu=1,etc
* check if kvm and q35 are set
Markus Frank (2):
machine as property-string
fix #3784: Parameter for guest vIOMMU + test-cases
PVE/API2/Qemu.pm | 11 ++++-
PVE/QemuConfig.pm | 3 +-
PVE/QemuServer.pm | 28 +++++++-----
PVE/QemuServer/Machine.pm | 57 ++++++++++++++++++++++++-
test/cfg2cmd/q35-viommu-intel.conf | 1 +
test/cfg2cmd/q35-viommu-intel.conf.cmd | 23 ++++++++++
test/cfg2cmd/q35-viommu-virtio.conf | 1 +
test/cfg2cmd/q35-viommu-virtio.conf.cmd | 23 ++++++++++
8 files changed, 132 insertions(+), 15 deletions(-)
create mode 100644 test/cfg2cmd/q35-viommu-intel.conf
create mode 100644 test/cfg2cmd/q35-viommu-intel.conf.cmd
create mode 100644 test/cfg2cmd/q35-viommu-virtio.conf
create mode 100644 test/cfg2cmd/q35-viommu-virtio.conf.cmd
docs:
v8:
* added general explaination of vIOMMU
* removed kvm/host as requirements
v7:
* added virtio-iommu documentation
* changed and seperated requirements
v6:
* changed capitalization and rephrased the text a bit.
v5:
* changed Host and VM Requirements
Markus Frank (1):
added vIOMMU documentation
qm-pci-passthrough.adoc | 51 +++++++++++++++++++++++++++++++++++++++++
qm.adoc | 1 +
2 files changed, 52 insertions(+)
manager:
v7:
* changed viommu checkbox to ComboBox to select either none, intel or VirtIO
v6:
* replaced '=== "1"' check with PVE.Parser.parseBoolean
* replaced hidden kvm ui with view property
* a few style changes
v5:
* added check if kvm is undefined or null
v4:
* check if kvm is enabled
* added kvm+q35 hint
Markus Frank (1):
ui: MachineEdit with viommu ComboBox
www/manager6/qemu/MachineEdit.js | 45 ++++++++++++++++++++++++++++++++
1 file changed, 45 insertions(+)
--
2.39.2
next reply other threads:[~2024-01-24 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 9:49 Markus Frank [this message]
2024-01-24 9:49 ` [pve-devel] [PATCH qemu-server v8 1/4] machine as property-string Markus Frank
2024-04-11 8:20 ` [pve-devel] applied: " Thomas Lamprecht
2024-01-24 9:49 ` [pve-devel] [PATCH qemu-server v8 2/4] fix #3784: Parameter for guest vIOMMU + test-cases Markus Frank
2024-04-11 8:30 ` Thomas Lamprecht
2024-01-24 9:49 ` [pve-devel] [PATCH docs v8 3/4] added vIOMMU documentation Markus Frank
2024-01-24 9:49 ` [pve-devel] [PATCH manager v8 4/4] ui: MachineEdit with viommu ComboBox Markus Frank
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=20240124094918.260222-1-m.frank@proxmox.com \
--to=m.frank@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.