From nobody Sun Feb 8 22:49:37 2026 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) client-ip=170.10.129.124; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-124.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1654009705; cv=none; d=zohomail.com; s=zohoarc; b=SZynfX5Jej2XojTVRpbWWXX6IJqis/4FPKNfF8qSTjpQvk+ObU5PsjQ2znNNqn5emhgXR/KKGaoBbozrKfBHCLhmhxlgjFBvoWyOtd1XXXh0iyMPMAfRKEycXMwj5EA+v50DZjrtJioXXIj4urmfTgCRhimZYNvgEZ0R6J4xMMA= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1654009705; h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=aRRvlgP+IhXqbOVAopY7mfzDY5u//4nVhkH7OoV8psA=; b=cSEDr6eBx5ruKOHrh1njQ6DQhGcfh3JL5t1IWi8U2JrbbgDyh+ZDK7TfV3DcnvTWLB2NaokmBZobDiASM/BYcd0HLfeCkhKAdDMCimA1mbGzRNN8iYrTL4lf3FxDErBRvNFlTce4+Aj6HXI2VR/ejsRJOIUUmfDnfY4LE4aM98I= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.zohomail.com with SMTPS id 1654009705859348.7757555497817; Tue, 31 May 2022 08:08:25 -0700 (PDT) Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-645-OwSZrtb4McCE_9LJ_4QTGA-1; Tue, 31 May 2022 11:08:15 -0400 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 0D1F23C60554; Tue, 31 May 2022 15:07:16 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (unknown [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id DD9892026D07; Tue, 31 May 2022 15:07:15 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 394F31947B87; Tue, 31 May 2022 15:07:15 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id F41D8194707E for ; Tue, 31 May 2022 15:07:05 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id E2D7F1131A; Tue, 31 May 2022 15:07:05 +0000 (UTC) Received: from speedmetal.lan (unknown [10.40.208.21]) by smtp.corp.redhat.com (Postfix) with ESMTP id 6F6875F245 for ; Tue, 31 May 2022 15:07:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1654009704; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=aRRvlgP+IhXqbOVAopY7mfzDY5u//4nVhkH7OoV8psA=; b=eVnCZ+Cm77xeAvxAB6VRPE3gdCt/NRXgzSS858bw4PXExZ26p6BSYM1Zm5Mj3zJZDUzmFl AInh9EFqDoYc4OMYeei0VS4ITOLileMpka4lG7vsw9EkcPpRKdxdiu2lX+/dqbJJNhKQcf z9aU7zrFuxESvqPegKqwFyCqWsJssfA= X-MC-Unique: OwSZrtb4McCE_9LJ_4QTGA-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 26/67] docs: formatdomain: Remove 'elementsNICS' anchor Date: Tue, 31 May 2022 17:06:01 +0200 Message-Id: <2dca974532af3f338ca398522e6df5870726cefd.1654008136.git.pkrempa@redhat.com> In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libvir-list-bounces@redhat.com Sender: "libvir-list" X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=libvir-list-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1654009707261100001 Content-Type: text/plain; charset="utf-8" The one local link addition prompted rewrapping of the whole paragraph. Signed-off-by: Peter Krempa --- docs/formatdomain.rst | 11 +++++------ docs/formatnetwork.rst | 4 ++-- docs/formatnetworkport.rst | 2 +- 3 files changed, 8 insertions(+), 9 deletions(-) diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst index 65197d6e3d..3618b1212a 100644 --- a/docs/formatdomain.rst +++ b/docs/formatdomain.rst @@ -239,11 +239,11 @@ harddisk, cdrom, network) determining where to obtain= /find the boot image. (the sorted list is vda, vdb, hda, hdc). Similar domain with hdc, vda, = vdb, and hda disks will boot from hda (sorted disks are: hda, hdc, vda, vdb)= . It can be tricky to configure in the desired way, which is why per-device = boot - elements (see `Hard drives, floppy disks, CDROMs`_, `network - interfaces <#elementsNICS>`__, and `Host device assignment`_ - sections below) were introduced and they are the preferred way providin= g full - control over booting order. The ``boot`` element and per-device boot el= ements - are mutually exclusive. :since:`Since 0.1.3, per-device boot since 0.8.= 8` + elements (see `Hard drives, floppy disks, CDROMs`_, `Network interfaces= `_, + and `Host device assignment`_ sections below) were introduced and they = are + the preferred way providing full control over booting order. + The ``boot`` element and per-device boot elements are mutually exclusiv= e. + :since:`Since 0.1.3, per-device boot since 0.8.8` ``smbios`` How to populate SMBIOS information visible in the guest. The ``mode`` attribute must be specified, and is either "emulate" (let the hypervisor @@ -4441,7 +4441,6 @@ Each mode supports an optional sub-element ```` (See `Device Addresses` which fine-tunes the correlation between the smartcard and a ccid bus cont= roller. For now, qemu only supports at most one smartcard, with an address of bus= =3D0 slot=3D0. -:anchor:`` Network interfaces ~~~~~~~~~~~~~~~~~~ diff --git a/docs/formatnetwork.rst b/docs/formatnetwork.rst index d6550f6df9..d956178e56 100644 --- a/docs/formatnetwork.rst +++ b/docs/formatnetwork.rst @@ -61,7 +61,7 @@ The first elements provide basic metadata about the virtu= al network. The optional parameter ``trustGuestRxFilters`` can be used to set that attribute of the same name for each domain interface connected to this network ( :since:`since 1.2.10` ). See the `Network - interfaces `__ section of the domain XML + interfaces `__ section of the dom= ain XML documentation for more details. Note that an explicit setting of this attribute in a portgroup or the individual domain interface will overri= de the setting in the network. @@ -616,7 +616,7 @@ starting. portgroups also support the optional parameter ``trustGuestRxFilters`` whi= ch can be used to set that attribute of the same name for each domain interface u= sing this portgroup ( :since:`since 1.2.10` ). See the `Network -interfaces `__ section of the domain XML +interfaces `__ section of the domain= XML documentation for more details. Note that an explicit setting of this attr= ibute in the portgroup overrides the network-wide setting, and an explicit setti= ng in the individual domain interface will override the setting in the portgroup. diff --git a/docs/formatnetworkport.rst b/docs/formatnetworkport.rst index 6f1a24a52c..394c65c2b7 100644 --- a/docs/formatnetworkport.rst +++ b/docs/formatnetworkport.rst @@ -98,7 +98,7 @@ The following elements are common to one or more of the p= lug types listed later ``virtualport`` The ``virtualport`` element describes metadata that needs to be provide= d to the underlying network subsystem. It is described in the domain XML - `interface documentation `__. + `interface documentation `__. Plugs ~~~~~ --=20 2.35.3