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 367E770FD5 for <pve-devel@lists.proxmox.com>; Thu, 23 Jun 2022 10:37:48 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 2CF9F23727 for <pve-devel@lists.proxmox.com>; Thu, 23 Jun 2022 10:37:48 +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) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 98E8E2371C for <pve-devel@lists.proxmox.com>; Thu, 23 Jun 2022 10:37:47 +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 63F1143C6A; Thu, 23 Jun 2022 10:37:47 +0200 (CEST) Message-ID: <c7f216ed-369e-6cc4-dec0-d72bae0e00c6@proxmox.com> Date: Thu, 23 Jun 2022 10:37:46 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.0 To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>, "DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com> References: <dd3a9ffa9a66f7a7d8c5cd383f080eb5d3f7076c.camel@groupe-cyllene.com> Content-Language: en-US From: Dominik Csapak <d.csapak@proxmox.com> In-Reply-To: <dd3a9ffa9a66f7a7d8c5cd383f080eb5d3f7076c.camel@groupe-cyllene.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.101 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.001 Looks like a legit reply (A) 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-devel] last training week student feedback/request X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Thu, 23 Jun 2022 08:37:48 -0000 On 6/23/22 10:25, DERUMIER, Alexandre wrote: > Hi, > > I just finished my proxmox training week, > > here some student requests/feedback: Hi, i just answer the points where i'm currently involved, so someone else might answer to the other ones ;) [snip] > 2) > Another student have a need with pci passthrough, cluster with > multiples nodes with multiple pci cards. > He's using HA and have 1 or 2 backups nodes with a lot of cards, > to be able to failover 10 others servers. > > The problem is that on the backups nodes, the pci address of the cards > are not always the same than production nodes. > So Ha can't work. > > I think it could be great to add some kind of "shared local device > pool" at datacenter level, where we could define > > pci: poolname > node1:pciaddress > node2:pciaddress > > usb: poolname > node1:usbport > node2:usbport > > > so we could dynamicaly choose the correct pci address when restarting > the vm. > > Permissions could be added too, maybe a migratable option when mdev > live migration support will be ready, ... i was working on that last year, but got hold up with other stuff, but i'm planning to picking this up again this/next week my solution looked very similar to yours, with additional fields to uniquely identify the card (to prevent accidental pass-through when the address changes fore example) permissions are also planned there... > > > 3) > Related to 2), another student have a need of live migraton with nvidia > card with mdev. > I'm currently trying to test to see if it's possible, as they are some > experimental vfio option to enable it, but it doesn't seem to be ready. > would be cool, i'd like to have some vgpu capable cards to test here, but so far no luck (also access/support to/of the vgpu driver from nvidia is probably the bigger problem AFAICS) kind regards Dominik