From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 953AA9B01B for ; Wed, 24 May 2023 15:47:24 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 757921EEA8 for ; Wed, 24 May 2023 15:47:24 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Wed, 24 May 2023 15:47:23 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 7ECDB46DF7 for ; Wed, 24 May 2023 15:47:23 +0200 (CEST) Message-ID: Date: Wed, 24 May 2023 15:47:22 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: pve-user@lists.proxmox.com References: Content-Language: en-US From: Dominik Csapak In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.135 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment POISEN_SPAM_PILL 0.1 Meta: its spam POISEN_SPAM_PILL_1 0.1 random spam to be learned in bayes POISEN_SPAM_PILL_3 0.1 random spam to be learned in bayes SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] Subject: Re: [PVE-User] vGPU scheduling X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2023 13:47:24 -0000 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