all lists on 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 pve-nvidia-vgpu-helper v2 4/4] debian: add and install nvidia-vgpu systemd template unit file
Date: Wed, 22 Jan 2025 14:14:12 +0100	[thread overview]
Message-ID: <fa1425a5-c8c8-4bed-814f-25169759e5e4@proxmox.com> (raw)
In-Reply-To: <01858afc-d11e-4890-9fd2-30643c607e82@proxmox.com>

Am 21.01.25 um 11:36 schrieb Dominik Csapak:
> On 1/21/25 11:04, Hannes Duerr wrote:
>> diff --git a/debian/nvidia-vgpud@.service b/debian/nvidia-vgpud@.service
>> new file mode 100644
>> index 0000000..b3c1220
>> --- /dev/null
>> +++ b/debian/nvidia-vgpud@.service
>
> mhmm not sure if it's so good to reuse the exiting name of the nvidia service
> for this. also not sure how systemd likes it if there is a service 'foo.service'
> and a template 'foo@.service' (though my guess would be that it's not that big of an issue)
> 
> i'd like to seee a distinct name for this (maybe even with pve prefix) like:
> 
> pve-nvidia-sriov@.service
> 
> Then it's clear where it comes from and what it's for (vgpud is an nvidia daemon
> that does not really has anything to do with what this does)
> Or do you have any objections to that?
> 
> also, would it make sense to add a
> 
> ---
> ConditionPathExists=/usr/lib/nvidia/sriov-manage
> ---
> 
> too?
> 
> otherwise users that enable it accidentally or too early run into an ugly error
> (though that can be desired too)

An option might be to replace the ExecStartPre "sleep 5" with an actual pre-start
command provided by the helper that ensures that everything is setup correctly
and prints telling errors otherwise. That can then also handle any sleep that is
required, maybe in a more time-efficient way – like loop and check for the required
condition with shorter sleeps in-between, the wiki also mentions that this might
need to be adapted depending on the setup/HW.

Anyway, it would be good to get an actual commit message, it can be short but
could describe what this does and why a sleep is required in the first place,
also mentioning that this was taken over from the wiki [0] could be nice to
know.

https://pve.proxmox.com/mediawiki/index.php?title=NVIDIA_vGPU_on_Proxmox_VE&oldid=12125#Enabling_SR-IOV


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

  parent reply	other threads:[~2025-01-22 13:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21 10:04 [pve-devel] [PATCH manager/nvidia-vgpu-helper v2 0/5] reduce setup steps for nvidia vgpu drivers Hannes Duerr
2025-01-21 10:04 ` [pve-devel] [PATCH pve-nvidia-vgpu-helper v2 1/4] create a debian package to make the installation of Nvidia vGPU drivers more convenient Hannes Duerr
2025-01-21 10:04 ` [pve-devel] [PATCH pve-nvidia-vgpu-helper v2 2/4] debian/control: add dependency for helper script Hannes Duerr
2025-01-21 10:04 ` [pve-devel] [PATCH pve-nvidia-vgpu-helper v2 3/4] add pve-nvidia-vgpu-helper and Makefile to make dependency installtion more convenient Hannes Duerr
2025-01-21 10:47   ` Dominik Csapak
2025-01-21 15:36     ` Thomas Lamprecht
2025-01-21 16:12       ` Hannes Dürr
2025-01-22 15:23         ` Hannes Dürr
2025-01-22 16:04           ` Thomas Lamprecht
2025-01-23 12:38             ` Hannes Dürr
2025-01-21 10:04 ` [pve-devel] [PATCH pve-nvidia-vgpu-helper v2 4/4] debian: add and install nvidia-vgpu systemd template unit file Hannes Duerr
2025-01-21 10:36   ` Dominik Csapak
2025-01-21 11:58     ` Hannes Dürr
2025-01-22 13:14     ` Thomas Lamprecht [this message]
2025-01-21 10:04 ` [pve-devel] [PATCH pve-manager v2 1/1] debian/control: add pve-nvidia-vgpu-helper as dependency 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=fa1425a5-c8c8-4bed-814f-25169759e5e4@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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal