From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] vGPU scheduling
Date: Wed, 24 May 2023 15:47:22 +0200 [thread overview]
Message-ID: <c75cc8dc-3f50-f69a-8db2-ecd1b45e4715@proxmox.com> (raw)
In-Reply-To: <mailman.190.1684933430.348.pve-user@lists.proxmox.com>
On 5/24/23 15:03, Eneko Lacunza via pve-user wrote:
> Hi,
Hi,
>
> We're looking to move a PoC in a customer to full-scale production.
>
> Proxmox/Ceph cluster will be for VDI, and some VMs will use vGPU.
>
> I'd like to know if vGPU status is being exposed right now (as of 7.4) for each node through API, as
> it is done for RAM/CPU, and if not, about any plans to implement that so that a scheduler (in our
> case that should be UDS Enterprise VDI manager) can choose a node with free vGPUs to deploy VDIs.
what exactly do you mean with vGPU status?
there currently is no api to see which pci devices are in use of a vm
(though that could be done per node, not really for mediated devices though)
there is the /nodes/NODENAME/hardware/pci api call which shows what devices exist
and if they have mdev (mediated device) capability (e.g. NVIDIA GRID vGPU)
for those cards there also exists the api call
/nodes/NODENAME/hardware/pci/PCIID/mdev
which gives a list of mdev types and how many are available of them
does that help?
if you have more specific requirements (or i misunderstood you), please
open a bug/feature request on https://bugzilla.proxmox.com
>
> Thanks
Kind Regards
Dominik
next parent reply other threads:[~2023-05-24 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.190.1684933430.348.pve-user@lists.proxmox.com>
2023-05-24 13:47 ` Dominik Csapak [this message]
2023-05-25 7:32 ` DERUMIER, Alexandre
2023-05-25 7:43 ` Dominik Csapak
2023-05-25 9:03 ` Thomas Lamprecht
2024-05-31 7:59 ` Eneko Lacunza via pve-user
[not found] ` <cbb9c11d-5b8e-4f1a-98dd-b3e1cf4be45c@binovo.es>
2024-05-31 8:08 ` Dominik Csapak
[not found] ` <mailman.193.1684936457.348.pve-user@lists.proxmox.com>
[not found] ` <mailman.222.1684948008.348.pve-user@lists.proxmox.com>
[not found] ` <0e48cb4a-7fa0-2bd7-9d4e-f18ab8e03d20@proxmox.com>
[not found] ` <mailman.252.1685000179.348.pve-user@lists.proxmox.com>
2023-05-25 7:53 ` Dominik Csapak
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=c75cc8dc-3f50-f69a-8db2-ecd1b45e4715@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pve-user@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