From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Markus Frank <m.frank@proxmox.com>
Subject: [pve-devel] applied: Re: [PATCH qemu-server v9 1/3] fix #3784: config: Parameter for guest vIOMMU + test-cases
Date: Thu, 11 Apr 2024 16:44:23 +0200 [thread overview]
Message-ID: <ba21f955-dcfb-4192-acf9-be21f44d7001@proxmox.com> (raw)
In-Reply-To: <20240411104822.832432-2-m.frank@proxmox.com>
On 11/04/2024 12:48, Markus Frank wrote:
> vIOMMU enables the option to passthrough pci devices to L2 VMs
> in L1 VMs via Nested Virtualisation and adds an extra isolation.
>
> Uses the new property-string from the "config: define machine schema
> as property-string"-commit to add the viommu option to the machine
> parameter.
>
> Currently there are two vIOMMU implementation in QEMU to choose:
> intel or virtio
>
> Virtio-iommu is more recent but less used in production than intel-iommu.
>
> The assert_valid_machine_property function prevents using intel-iommu with
> i440fx.
>
> Signed-off-by: Markus Frank <m.frank@proxmox.com>
> ---
> PVE/API2/Qemu.pm | 2 ++
> PVE/QemuServer.pm | 12 +++++++++++
> PVE/QemuServer/Machine.pm | 17 ++++++++++++++-
> test/cfg2cmd/i440fx-viommu-intel.conf | 2 ++
> test/cfg2cmd/i440fx-viommu-virtio.conf | 1 +
> test/cfg2cmd/i440fx-viommu-virtio.conf.cmd | 25 ++++++++++++++++++++++
> 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 ++++++++++++++++++++
> 10 files changed, 106 insertions(+), 1 deletion(-)
> create mode 100644 test/cfg2cmd/i440fx-viommu-intel.conf
> create mode 100644 test/cfg2cmd/i440fx-viommu-virtio.conf
> create mode 100644 test/cfg2cmd/i440fx-viommu-virtio.conf.cmd
> 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
>
>
applied, thanks!
next prev parent reply other threads:[~2024-04-11 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 10:48 [pve-devel] [PATCH qemu-server/docs/manager v9 0/3] vIOMMU-Feature #3784 Markus Frank
2024-04-11 10:48 ` [pve-devel] [PATCH qemu-server v9 1/3] fix #3784: config: Parameter for guest vIOMMU + test-cases Markus Frank
2024-04-11 14:44 ` Thomas Lamprecht [this message]
2024-04-11 10:48 ` [pve-devel] [PATCH docs v9 2/3] add vIOMMU documentation Markus Frank
2024-04-11 14:47 ` [pve-devel] applied: " Thomas Lamprecht
2024-04-11 10:48 ` [pve-devel] [PATCH manager v9 3/3] ui: machine: add viommu ComboBox Markus Frank
2024-04-11 15:13 ` Thomas Lamprecht
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=ba21f955-dcfb-4192-acf9-be21f44d7001@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox