From nobody Sun Feb 8 22:49:35 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=1654009724; cv=none; d=zohomail.com; s=zohoarc; b=Uio1RN8zJK1kfb6NnQcD5Vbhd4txb1x3uZZTMH6qlqDncV16yZIH9LUoFHPA963C21mbjZzkyWkn2X6+IDRt+vOadv2e4rSAStZr5rL0GFqGLlqt2/hLuDZZpGJxcwlXXNkE6zEB9Kh5rHESmq6WojFpD8YHgdnGkiCSblkNnCI= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1654009724; 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=opt3akZWS2D0VDlZ2n2Tr35qAteMVUQpd04yLs/zaIo=; b=ehmInoR97Q3+AA8/7rFZ+K5jD0Xv/1e9UtdztrpUUkl6yVBcoNOJuKT5XaAdCAjOhJ5BC0x9FzDCXsxHS4rgFkYopewRQSUrqV5iQ5328JLVx9TaWLoE2SDxlsmeCJGifWfSIjxZhIKE4DfjeFawDwgh8kBtvhLtw3FR2hKHE1g= 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 165400972419785.52433712929269; Tue, 31 May 2022 08:08:44 -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-641-HyIDRBjcMdeig6P6j-jIag-1; Tue, 31 May 2022 11:08:28 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id AE8B11C3E9A0; Tue, 31 May 2022 15:07:06 +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 96C571121315; Tue, 31 May 2022 15:07:06 +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 4C2961947072; Tue, 31 May 2022 15:07:06 +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 A9160194706D for ; Tue, 31 May 2022 15:07:02 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 9AD0782882; Tue, 31 May 2022 15:07:02 +0000 (UTC) Received: from speedmetal.lan (unknown [10.40.208.21]) by smtp.corp.redhat.com (Postfix) with ESMTP id 263A81131A for ; Tue, 31 May 2022 15:07:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1654009723; 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=opt3akZWS2D0VDlZ2n2Tr35qAteMVUQpd04yLs/zaIo=; b=d7ABoBHZNT8cROrEWuCvS8/AjRgt2G6EJ9ZShjaPdtOIpywIBIMaCa/QeT4RcmWtKSwx5J vz2tukd2pP8f9KjqRwbQ2GDxriEUoJ5NlpYubUf3DzB+mHAKKt3YfLQrMi/n5xdCBA8V/E fW1mWS1n505LXSHfC+32Kk7w+XoLF/E= X-MC-Unique: HyIDRBjcMdeig6P6j-jIag-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 22/67] docs: formatdomain: Remove 'elementsVirtio' anchor Date: Tue, 31 May 2022 17:05:57 +0200 Message-Id: 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.3 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: 1654009725462100002 Content-Type: text/plain; charset="utf-8" Signed-off-by: Peter Krempa --- docs/formatdomain.rst | 24 ++++++++++-------------- 1 file changed, 10 insertions(+), 14 deletions(-) diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst index 9d3960e7ad..91517b069f 100644 --- a/docs/formatdomain.rst +++ b/docs/formatdomain.rst @@ -3127,7 +3127,7 @@ paravirtualized driver is specified via the ``disk`` = element. virtio-blk. ( :since:`Since 3.9.0` ) - The optional ``queue_size`` attribute specifies the size of each virt queue for virtio-blk. ( :since:`Since 7.8.0` ) - - For virtio disks, `Virtio-specific options <#elementsVirtio>`__ can = also + - For virtio disks, `Virtio-related options`_ can also be set. ( :since:`Since 3.5.0` ) - The optional ``metadata_cache`` subelement controls aspects related = to the format specific caching of storage image metadata. Note that this se= tting @@ -3431,7 +3431,7 @@ A directory on the host that can be accessed directly= from the guest. "loop", with a format of "raw" or "nbd" with any format. QEMU suppor= ts a type of "path" or "handle", but no formats. Virtuozzo driver support= s a type of "ploop" with a format of "ploop". - - For virtio-backed devices, `Virtio-specific options <#elementsVirtio= >`__ + - For virtio-backed devices, `Virtio-related options`_ can also be set. ( :since:`Since 3.5.0` ) - For ``virtiofs``, the ``queue`` attribute can be used to specify the= queue size (i.e. how many requests can the queue fit). ( :since:`Since 6.2= .0` ) @@ -3565,7 +3565,6 @@ control where on the bus the device will be placed: will have access to it. ``
`` is an invalid address type for all other device types. :since:`Since 6.0.0` -:anchor:`` Virtio-related options ~~~~~~~~~~~~~~~~~~~~~~ @@ -3746,7 +3745,7 @@ An optional sub-element ``driver`` can specify the dr= iver specific options: controllers must be defined each having a specific ``iothread`` value. = The ``iothread`` value must be within the range 1 to the domain iothreads v= alue. virtio options - For virtio controllers, `Virtio-specific options <#elementsVirtio>`__ c= an + For virtio controllers, `Virtio-related options`_ can also be set. ( :since:`Since 3.5.0` ) USB companion controllers have an optional sub-element ```` to spe= cify @@ -5293,7 +5292,7 @@ following attributes are available for the ``"virtio"= `` NIC driver: you know what you are doing. Proper RSS configuration depends from vcpu, tap, and vhost settings.** virtio options - For virtio interfaces, `Virtio-specific options <#elementsVirtio>`__ ca= n also + For virtio interfaces, `Virtio-related options`_ can also be set. ( :since:`Since 3.5.0` ) Offloading options for the host and guest can be configured using the foll= owing @@ -5825,8 +5824,7 @@ change the grab key combination. <#elementsVirtioTransitional>`__ for more details. The subelement ``driver`` can be used to tune the virtio options of the de= vice: -`Virtio-specific options <#elementsVirtio>`__ can also be set. ( :since:`S= ince -3.5.0` ) +`Virtio-related options`_ can also be set. ( :since:`Since 3.5.0` ) Hub devices ~~~~~~~~~~~ @@ -6247,8 +6245,7 @@ A video device. the default QEMU backend. "vhostuser" will use a separate vhost-user process backend (for ``virtio`` device). virtio options - `Virtio-specific options <#elementsVirtio>`__ can also be set ( - :since:`Since 3.5.0` ) + `Virtio-related options`_ can also be set (:since:`Since 3.5.0`) VGA configuration Control how the video devices exposed to the guest using the ``vgaco= nf`` attribute which takes the value "io", "on" or "off". At present, it'= s only @@ -7476,8 +7473,8 @@ Example: manually added device with static PCI slot 2= requested years) might be ignored. :since:`Since 1.1.1, requires QEMU 1.5` ``driver`` - For model ``virtio`` memballoon, `Virtio-specific - options <#elementsVirtio>`__ can also be set. ( :since:`Since 3.5.0` ) + For model ``virtio`` memballoon, `Virtio-related options`_ can also be = set. + ( :since:`Since 3.5.0` ) Random number generator device ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -7551,8 +7548,7 @@ Example: usage of the RNG device: The subelement ``driver`` can be used to tune the device: virtio options - `Virtio-specific options <#elementsVirtio>`__ can also be set. ( - :since:`Since 3.5.0` ) + `Virtio-related options`_ can also be set. ( :since:`Since 3.5.0` ) :anchor:`` @@ -8071,7 +8067,7 @@ attribute ``address`` of the ``cid`` element specifie= s the CID assigned to the guest. If the attribute ``auto`` is set to ``yes``, libvirt will assign a = free CID automatically on domain startup. :since:`Since 4.4.0` The optional ``driver`` element allows to specify virtio options, see -`Virtio-specific options <#elementsVirtio>`__ for more details. :since:`S= ince 7.1.0` +`Virtio-related options`_ for more details. :since:`Since 7.1.0` :: --=20 2.35.3