From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-vgpu-helper] add 'nova' and 'nova_core' to the modules blacklist
Date: Tue, 7 Apr 2026 13:59:22 +0200 [thread overview]
Message-ID: <20260407120102.2520237-1-d.csapak@proxmox.com> (raw)
in newer kernels (such as 7.0), nova gets automatically loaded for some
nvidia gpus. Since this is incompatible with the vGPU host driver, also
blacklist those on the setup step.
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
i also thought about adding a second parameter for nova, or renaming it
to better fit (e.g. --no-block-intree-drivers) but left it as is, so
that possible script that execute it won't be tripped up.
If wanted i can of course rename it.
src/pve-nvidia-vgpu-helper | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/src/pve-nvidia-vgpu-helper b/src/pve-nvidia-vgpu-helper
index 1102f3d..4cd6170 100755
--- a/src/pve-nvidia-vgpu-helper
+++ b/src/pve-nvidia-vgpu-helper
@@ -29,7 +29,8 @@ my sub print_usage_and_exit {
USAGE: pve-nvidia-vgpu-helper [OPTIONS]
Commands:
setup Install dependencies and ensure the node is ready for using NVIDIA vGPU.
- --no-block-nouveau Do not add modprobe.d config entry to block loading the 'nouveau' module.
+ --no-block-nouveau Do not add modprobe.d config entry to block loading the 'nouveau' and
+ 'nova' module.
General Options:
--help This output.
@@ -64,13 +65,19 @@ my sub apt_install {
## Commands
+my $block_nouveau_nova = <<EOF;
+blacklist nouveau
+blacklist nova
+blacklist nova_core
+EOF
+
my sub do_setup {
if ($no_block_nouveau) {
- print "Skipping creation of modprobe.d config to block 'nouveau' module as requested\n";
+ print "Skipping creation of modprobe.d config to block 'nouveau' and 'nova' modules as requested\n";
} elsif (! -e "/etc/modprobe.d/block-nouveau.conf") {
- print "Adding modprobe config to block loading of the 'nouveau' module.\n";
+ print "Adding modprobe config to block loading of the 'nouveau' and 'nova' module.\n";
mkdir('/etc/modprobe.d') or $!{EEXIST} or die "failed to create '/etc/modprobe.d' - $!\n";
- PVE::SysFSTools::file_write("/etc/modprobe.d/block-nouveau.conf", "blacklist nouveau\n")
+ PVE::SysFSTools::file_write("/etc/modprobe.d/block-nouveau.conf", $block_nouveau_nova)
|| die "failed to create block-nouveau.conf - $!\n";
syslog('info', "Added modprobe config to block loading of the 'nouveau' module.");
--
2.47.3
next reply other threads:[~2026-04-07 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 11:59 Dominik Csapak [this message]
2026-04-07 13:25 ` applied: " 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=20260407120102.2520237-1-d.csapak@proxmox.com \
--to=d.csapak@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