From: Dominik Csapak <d.csapak@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Hannes Duerr <h.duerr@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager/nvidia-vgpu-helper v3 0/6] reduce setup steps for nvidia vgpu drivers
Date: Wed, 29 Jan 2025 14:12:35 +0100 [thread overview]
Message-ID: <d7836c5c-3c82-4fd9-8e7a-f2665bd1bdf4@proxmox.com> (raw)
In-Reply-To: <775f73c4-4bea-4745-a6ae-04b3e2ba95fa@proxmox.com>
On 1/29/25 14:08, Dominik Csapak wrote:
> Looks mostly good and tested fine, but still a two comments:
>
> * IMHO patch 5/5 could be squashed into 3/5 (no need add code that gets changed immediately
> afterwards)
>
> * did you read thomas message for the service file last time around?
> https://lore.proxmox.com/pve-devel/fa1425a5-c8c8-4bed-814f-25169759e5e4@proxmox.com/
>
> patch 4/5 does not have a commit message, so this would be good
> and as thomas said the sleep 5 could be replaced by a short script that
> checks the actual condition (IIRC if the correct nvidia daemon is loaded,
> I would have to check if you need that info
>
> (not sure if these are blockers though from @Thomas' side)
>
>
actually, i just found an issue with the newer kernel detection:
i installed `proxmox-kernel-6.11` and ran the tool
it prompted me to install:
proxmox-headers-6.11.11-1-pve
Would you like to install them now (y/n)?
but if we only install this package, the next 6.11 update will not get the correct headers,
we instead have to install the package 'proxmox-headers-6.11'
so we only should ever look at the 'x.yy' of the kernel, otherwise users
ran into an issue later on
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-01-29 13:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 14:41 Hannes Duerr
2025-01-24 14:41 ` [pve-devel] [PATCH pve-nvidia-vgpu-helper v3 1/5] create a debian package to make the installation of Nvidia vGPU drivers more convenient Hannes Duerr
2025-01-24 14:41 ` [pve-devel] [PATCH pve-nvidia-vgpu-helper v3 2/5] debian/control: add dependency for helper script Hannes Duerr
2025-01-24 14:41 ` [pve-devel] [PATCH pve-nvidia-vgpu-helper v3 3/5] add pve-nvidia-vgpu-helper and Makefile to make dependency installtion more convenient Hannes Duerr
2025-01-24 14:41 ` [pve-devel] [PATCH pve-nvidia-vgpu-helper v3 4/5] debian: add and install pve-nvidia-sriov systemd template unit file Hannes Duerr
2025-01-24 14:41 ` [pve-devel] [PATCH pve-nvidia-vgpu-helper v3 5/5] script: install headers for running and newer kernel version only Hannes Duerr
2025-01-24 14:41 ` [pve-devel] [PATCH pve-manager v3 1/1] debian/control: add pve-nvidia-vgpu-helper as dependency Hannes Duerr
2025-01-29 13:08 ` [pve-devel] [PATCH manager/nvidia-vgpu-helper v3 0/6] reduce setup steps for nvidia vgpu drivers Dominik Csapak
2025-01-29 13:12 ` Dominik Csapak [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=d7836c5c-3c82-4fd9-8e7a-f2665bd1bdf4@proxmox.com \
--to=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.