From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 941CE1FF16A for ; Wed, 14 Aug 2024 16:15:11 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id DFBB71F088; Wed, 14 Aug 2024 16:15:24 +0200 (CEST) Mime-Version: 1.0 Date: Wed, 14 Aug 2024 16:14:50 +0200 Message-Id: From: "Alexander Zeidler" To: "Proxmox VE development discussion" References: <20240606092220.1190913-1-d.csapak@proxmox.com> <20240606092220.1190913-25-d.csapak@proxmox.com> In-Reply-To: <20240606092220.1190913-25-d.csapak@proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL 0.084 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. 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] [PATCH docs v4 1/2] qm: resource mapping: add description for `mdev` option X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" On Thu Jun 6, 2024 at 11:22 AM CEST, Dominik Csapak wrote: > in a new section about additional options > > Signed-off-by: Dominik Csapak > --- > no changes > qm.adoc | 13 +++++++++++++ > 1 file changed, 13 insertions(+) > > diff --git a/qm.adoc b/qm.adoc > index 42c26db..3f4e59a 100644 > --- a/qm.adoc > +++ b/qm.adoc > @@ -1802,6 +1802,19 @@ To create mappings `Mapping.Modify` on `/mapping//` is necessary > To use these mappings, `Mapping.Use` on `/mapping//` is necessary > (in addition to the normal guest privileges to edit the configuration). > > +Additional Options > +^^^^^^^^^^^^^^^^^^ Omit the '^' line and use .Additional Options instead, to avoid: asciidoc: WARNING: qm.adoc: line 1806: section title out of sequence: expected level 3, got level 4 > + > +There are additional options when defining a cluster wide resource mapping. > +Currently there are the following options: > + > +* `mdev` (PCI): This marks the PCI device as being capable of providing "This marks the PCI device", but your 2/2 patch begins with "This marks the device", maybe add or remove the word "PCI" to stay consistent. > + `mediated devices`. When this is enabled, you can select a type when > + configuring it on the guest. If multiple PCI devices are selected for > + the mapping, the mediated device will be create on the first one where > + there are any available instances of the selected type. s/create/created/ "where there" could be avoided, e.g.: If multiple PCI devices are selected for the mapping, the mediated device will be created on the first device on which instances of the selected type are available. > + > + > Managing Virtual Machines with `qm` > ------------------------------------ > _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel