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>,
	Dominik Csapak <d.csapak@proxmox.com>,
	Hannes Duerr <h.duerr@proxmox.com>
Subject: Re: [pve-devel] [PATCH proxmx-nvidia-vgpu-helper 2/2] add script to help with the installation of the nvidia vgpu dependencies
Date: Mon, 2 Dec 2024 16:17:24 +0100	[thread overview]
Message-ID: <3a694857-74d7-418c-9812-dfa147eb17a4@proxmox.com> (raw)
In-Reply-To: <a830b1a1-1fe8-4329-b2eb-9525ff54aa25@proxmox.com>

Am 02.12.24 um 09:47 schrieb Dominik Csapak:
> What I'd have imagined is more like our 'pveceph' tool that can
> include multiple commands, even if we might only have one or two for now
> 
> so e.g.
> 
> pve-nvidia-vgpu-helper install-prerequisites

Yes, that was my idea as well, but I'd just do above for now, all else can follow,
let's not blow up the scope here for the initial implementation.

> pve-nvidia-vgpu-helper gpus list
> pve-nvidia-vgpu-helper gpus enable-sriov
> etc..

> thir
> 
> * not sure about that, but couldn't this be a rust binary?

Not sure if it wins us much here, it certainly has it's cost too, and for such
simple things it does not always balance out, like having to rebuild it on
bigger toolchain changes to profit from them and do not cause issues on major
upgrades; a interpreted language avoids that and perl is an OK choice here.
Also, Hannes already re-wrote this from bash to perl, let's not make him run in
circles. If it really becomes a problem to use perl, which I doubt, then it can
be still re-written later on, which is as much work as doing it now but then
has some actual arguments for making that worthwhile.

> i think we have everything we need already there.
> It is not a requirement for this IMHO, but personally i tend to write new things
> in rust these days.
> 
> * it would be very nice to also have some general prerequisites checked, maybe
> as a separate command or all-in-one (does not matter much imo). For example
> if iommu/vt-d/etc. is turned on and the cards are separated, if there are even
> nvidia cards installed, etc.

IMO it does matter quite a bit, installing base-line software support and doing
basic checks are very different things, I'd not couple those unconditionally.
As it's odd that one cannot prepare a host by installing the basic package set
if it IOMMU is turned off, why force a reboot there? The other way is also a bit
odd to try to install stuff if one just wants to check if they meet some basic
checks (after doing some changes to HW, kernel cmdline, ...).

So please do those in different commands, and the basic checks can be nice to have
but I'd really focus on the command to install the basic package set first.


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


      parent reply	other threads:[~2024-12-02 15:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20 11:26 [pve-devel] [PATCH proxmx-nvidia-vgpu-helper 0/2] reduce setup steps for nvidia vgpu drivers Hannes Duerr
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-12-02  8:36   ` Dominik Csapak
2024-12-02  9:45     ` Hannes Dürr
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
2024-12-02  8:47   ` Dominik Csapak
2024-12-02  9:45     ` Hannes Dürr
2024-12-02 15:17     ` 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=3a694857-74d7-418c-9812-dfa147eb17a4@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=d.csapak@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