From: Markus Frank <m.frank@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH qemu-server] fix #3784: Parameter for guest vIOMMU
Date: Fri, 25 Feb 2022 13:00:28 +0100 [thread overview]
Message-ID: <20220225120028.1768349-1-m.frank@proxmox.com> (raw)
added a Parameter for vIOMMU so nobody has to use a github-script
or change the kvm command on every vm boot.
The args parameter doesn't work because the -device parameter(kvm)
with intel-iommu has to be placed before the other arguments.
Signed-off-by: Markus Frank <m.frank@proxmox.com>
---
PVE/QemuServer.pm | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index 42f0fbd..a09dd2e 100644
--- a/PVE/QemuServer.pm
+++ b/PVE/QemuServer.pm
@@ -647,6 +647,12 @@ EODESCR
." remove disk operations.",
default => 0,
},
+ viommu => {
+ optional => 1,
+ type => 'boolean',
+ description => "enable guest vIOMMU",
+ default => 0,
+ },
bios => {
optional => 1,
type => 'string',
@@ -3427,6 +3433,9 @@ sub config_to_command {
my $winversion = windows_version($ostype);
my $kvm = $conf->{kvm};
my $nodename = nodename();
+ my $viommu = $conf->{viommu};
+
+ push @$devices, '-device', 'intel-iommu,intremap=on,caching-mode=on' if $viommu;
my $arch = get_vm_arch($conf);
my $kvm_binary = get_command_for_arch($arch);
@@ -4021,6 +4030,8 @@ sub config_to_command {
}
push @$machineFlags, "type=${machine_type_min}";
+ push @$machineFlags, 'accel=kvm,kernel-irqchip=split' if $viommu;
+
push @$cmd, @$devices;
push @$cmd, '-rtc', join(',', @$rtcFlags) if scalar(@$rtcFlags);
push @$cmd, '-machine', join(',', @$machineFlags) if scalar(@$machineFlags);
--
2.30.2
next reply other threads:[~2022-02-25 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 12:00 Markus Frank [this message]
2022-03-16 17:03 ` 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=20220225120028.1768349-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.