From: Hannes Duerr <h.duerr@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH proxmx-nvidia-vgpu-helper 0/2] reduce setup steps for nvidia vgpu drivers
Date: Wed, 20 Nov 2024 12:26:08 +0100 [thread overview]
Message-ID: <20241120112610.160234-1-h.duerr@proxmox.com> (raw)
The patches apply to the repository proxmox-nvidia-vgpu-helper which
is currently only available in my staff folder
`staff/h.duerr/proxmox-nvidia-vgpu-helper`. The aim of the repository
is to reduce the necessary installation steps for the Nvidia VGPU
drivers [0]. The repository contains an install script which can be
used to check and install necessary dependencies and a systemd
template service which can be used to configure the SR-IOV per pci-id
Part of the changes would later be the adjustment of the wiki page
[0] https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE
Hannes Duerr (2):
debian/control: adjust description and dependency to new purpose
add script to help with the installation of the nvidia vgpu
dependencies
debian/control | 11 +++---
pve-install-nvidia-vgpu-deps | 66 ++++++++++++++++++++++++++++++++++++
2 files changed, 71 insertions(+), 6 deletions(-)
create mode 100755 pve-install-nvidia-vgpu-deps
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-11-20 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 11:26 Hannes Duerr [this message]
2024-11-20 11:26 ` [pve-devel] [PATCH proxmx-nvidia-vgpu-helper 1/2] debian/control: adjust description and pve-manager dependency Hannes Duerr
2024-11-20 11:26 ` [pve-devel] [PATCH proxmx-nvidia-vgpu-helper 2/2] add script to help with the installation of the nvidia vgpu dependencies Hannes Duerr
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=20241120112610.160234-1-h.duerr@proxmox.com \
--to=h.duerr@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