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>
Subject: [pve-devel] applied: [PATCH manager stable-7] pve7to8: add check for nvidia-vgpu-mgr
Date: Mon, 12 Jun 2023 17:15:07 +0200	[thread overview]
Message-ID: <505a9e96-538c-1804-99ec-6dd1b5ae8e46@proxmox.com> (raw)
In-Reply-To: <20230612100053.1944194-1-d.csapak@proxmox.com>

Am 12/06/2023 um 12:00 schrieb Dominik Csapak:
> Currently the nvidia vgpu host driver (15.2) does not support kernels >
> 6.0 and thus will not work with bookworm based releases for now.
> 
> Fail when the service is running, and warn if it only exists, but is
> disabled/stopped (in case a user installed it sometime but did not need
> it and disabled it).
> 
> In any case, link to the known issues section in the upgrade guide
> (which we can update to contain up-to-date information).
> 
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> I opted to not parse more specific information about the driver (like
> version, etc.) since it increases the complexity of the check but
> without any real upside currently. If there is some future version that
> supports it, we can update that to only warn/error for not supported
> versions.
> 
> I'll add the section to the upgrade guide shortly
> 
>  PVE/CLI/pve7to8.pm | 22 ++++++++++++++++++++++
>  1 file changed, 22 insertions(+)
> 
>

applied, thanks!

But I made some follow-ups:

- fix typo and factor common message into single variable

- pass the suppress_stderr param from get_systemd_unit_state to avoid an ugly message
  for unaffected systems, i.e. like:
  "Failed to get unit file state for nvidia-vgpu-mgr.service: No such file or directory"

- downgraded the failure again to a warning, reversing my initial recommendation to you,
  mostly due to future proofing for the case where NVIDIA fixes this, as in that case we'd
  need to tell users that they should ignore a failure, which is not good – my bad for not
  thinking of this earlier.




      reply	other threads:[~2023-06-12 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 10:00 [pve-devel] " Dominik Csapak
2023-06-12 15:15 ` 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=505a9e96-538c-1804-99ec-6dd1b5ae8e46@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=d.csapak@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