public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Hannes Duerr <h.duerr@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH manager/nvidia-vgpu-helper v5 0/5] reduce setup steps for nvidia vgpu drivers
Date: Tue, 18 Feb 2025 14:50:27 +0100	[thread overview]
Message-ID: <ecd77acb-18eb-4210-872e-37b9c1e892b8@proxmox.com> (raw)
In-Reply-To: <20250213081516.16266-1-h.duerr@proxmox.com>

Am 13.02.25 um 09:15 schrieb Hannes Duerr:
> Changes in v5:
> in commits
> 
> Changes in v4:
> in commits
> 
> Changes in v3:
> * install headers for every installed kernel version by default
> * additionally add patch to only install headers for running kernel
>   version and newer ones, this requires the new dependency
>   "libdpkg-perl"
> * remove unnecessary intrusive "Dpkg:Options::=--force-confnew"
> * rename systemd template unit to "pve-nvidia-sriov@.service"
> * check if path "/usr/lib/nvidia/sriov-manage" exists in systemd
>   template unit
> 
> 
> Changes in v2:
> * patches contain all changes to build new repository
> * make pve-manager depend on this package instead of the other way around
> * install the script to /usr/bin/
> * rename the script to pve-nvidia-vgpu-helper because it is only
>   relevant for PVE(the repository should therefore also be renamed
>   when created)
> 
> The aim of the repository is to reduce the necessary installation
> steps for the Nvidia VGPU drivers [0]. The package installs a 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
> 
> pve-nvidia-vgpu-helper:
> 
> Hannes Duerr (4):
>   create a debian package to make the installation of Nvidia vGPU
>     drivers more convenient
>   debian/control: add dependency for helper script
>   add pve-nvidia-vgpu-helper and Makefile to make dependency
>     installation more convenient
>   debian: add and install pve-nvidia-sriov systemd template unit file
> 
> 
> pve-manager:
> 
> Hannes Duerr (1):
>   debian/control: add pve-nvidia-vgpu-helper as dependency
> 
>  debian/control | 1 +
>  1 file changed, 1 insertion(+)
> 
> 
> Summary over all repositories:
>   1 files changed, 1 insertions(+), 0 deletions(-)
> 


applied series, thanks!

With a few follow-ups as mentioned off-list, I tried to have some description
and reasoning in the commit message, if something is not clear we can talk
directly about it.

Note that for now I also downgraded the dependency from an unconditional one
to a recommends one; this will still pull it in on upgrade for default
installations.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      parent reply	other threads:[~2025-02-18 13:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13  8:15 [pve-devel] " Hannes Duerr
2025-02-13  8:15 ` [pve-devel] [PATCH pve-nvidia-vgpu-helper v5 1/4] create a debian package to make the installation of Nvidia vGPU drivers more convenient Hannes Duerr
2025-02-13  8:15 ` [pve-devel] [PATCH pve-nvidia-vgpu-helper v5 2/4] debian/control: add dependency for helper script Hannes Duerr
2025-02-13  8:15 ` [pve-devel] [PATCH pve-nvidia-vgpu-helper v5 3/4] add pve-nvidia-vgpu-helper and Makefile to make dependency installation more convenient Hannes Duerr
2025-02-13  8:15 ` [pve-devel] [PATCH pve-nvidia-vgpu-helper v5 4/4] debian: add and install pve-nvidia-sriov systemd template unit file Hannes Duerr
2025-02-13  8:15 ` [pve-devel] [PATCH pve-manager v5 1/1] debian/control: add pve-nvidia-vgpu-helper as dependency Hannes Duerr
2025-02-18 13:50 ` Thomas Lamprecht [this message]

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=ecd77acb-18eb-4210-872e-37b9c1e892b8@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal