From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <d.csapak@proxmox.com> 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 58F119B6FB for <pve-user@lists.proxmox.com>; Thu, 25 May 2023 09:54:25 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 314892770A for <pve-user@lists.proxmox.com>; Thu, 25 May 2023 09:53:55 +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 <pve-user@lists.proxmox.com>; Thu, 25 May 2023 09:53:54 +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 3AECE4706B for <pve-user@lists.proxmox.com>; Thu, 25 May 2023 09:53:54 +0200 (CEST) Message-ID: <44a4c34c-6b17-6b1e-b54b-3b0dff7c3d59@proxmox.com> Date: Thu, 25 May 2023 09:53:53 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: pve-user@lists.proxmox.com References: <mailman.190.1684933430.348.pve-user@lists.proxmox.com> <c75cc8dc-3f50-f69a-8db2-ecd1b45e4715@proxmox.com> <mailman.193.1684936457.348.pve-user@lists.proxmox.com> <mailman.222.1684948008.348.pve-user@lists.proxmox.com> <0e48cb4a-7fa0-2bd7-9d4e-f18ab8e03d20@proxmox.com> <mailman.252.1685000179.348.pve-user@lists.proxmox.com> From: Dominik Csapak <d.csapak@proxmox.com> In-Reply-To: <mailman.252.1685000179.348.pve-user@lists.proxmox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.015 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 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 - 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 <pve-user.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-user/> List-Post: <mailto:pve-user@lists.proxmox.com> List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Thu, 25 May 2023 07:54:25 -0000 On 5/25/23 09:36, Eneko Lacunza via pve-user wrote: > Hi Dominik, > > > El 25/5/23 a las 9:24, Dominik Csapak escribió: >> >>> 2.12.0 (qemu-kvm-2.12.0-64.el8.2.27782638) >>> * Microsoft Windows Server with Hyper-V 2019 Datacenter edition >>> * Red Hat Enterprise Linux Kernel-based Virtual Machine (KVM) 9.0 and 9.1 >>> * Red Hat Virtualization 4.3 >>> * Ubuntu Hypervisor 22.04 >>> * VMware vSphere Hypervisor (ESXi) 7.0.1, 7.0.2, and 7.0.3 >>> >>> Is there any effort planned or on the way to have Proxmox added to the above list? >> >> We'd generally like to be on the supported hypervisor list, but currently >> none of our efforts to contact NVIDIA regarding this were successful, >> but i hope we can solve this sometime in the future... > > I can try to report this via customer request to nvidia, where should I refer them to? You can refer them directly to me (d.csapak@proxmox.com) or our office mail (office@proxmox.com). Maybe it helps if the request comes also from the customer side. > >> >>> >>> As Ubuntu 22.04 is in it and the Proxmox kernel is derived from it, the technical effort may not >>> be so large. >> >> Yes, their current Linux KVM package (15.2) should work with our 5.15 kernel, >> it's what i use here locally to test, e.g. [0] > > We had varying success with 5.15 kernels, some versions work but others do not (refused to work > after kernel upgrade and had to pin older kernel). Maybe it would be worth to keep a list of known > to work/known not to work kernels? Normally i have my tests running with each update of the 5.15 kernel and i did not see any special problems there. The only recent thing was that we had to change how we clean up the mediated devices for their newer versions [0] Note that i only test the latest supported GRID version though (Currently 15.2) Regards Dominik 0: https://git.proxmox.com/?p=qemu-server.git;a=commit;h=49c51a60db7f12d7fe2073b755d18b4d9b628fbd