From nobody Tue Apr 30 02:56:31 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 216.205.24.124 as permitted sender) client-ip=216.205.24.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 216.205.24.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=1601647988; cv=none; d=zohomail.com; s=zohoarc; b=EiMSc83yb+Thy91vmYDgPkC6oQozdCeuNPw0ZLN4pzXgJxzehnwM0FrRC8iW34dAKd7EJgFuIUJuvzXmGGYDX1X0Df3FgtLQVMhuexyI+/kzRJ5V440cyf8sIZrMNsPrX0kuUnsQ0skz9PBpmQrENSH3CZqrormeGxnYGIFD4vA= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1601647988; 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=YSV0odiUMBMf5h49XrSSerU0KeREmYX4+K2L+TNvZCs=; b=Di57h+1qZbWNApR2d0zNhpI6yFacXSXKySdeV6GqsmjTx7Zhv7O4+XknXu7aeCMpHOI2MUdwgUR3L0YoQDisn+rcNFHLosTUeqqGVm+UAUHsps7co7uPQGKoBKIwFEfVwNvFrbwy5aFUq0kTH7k1jIjlw3meh2jksL6DYzGjh5k= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 216.205.24.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) header.from= Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mx.zohomail.com with SMTPS id 1601647988684727.2415957395559; Fri, 2 Oct 2020 07:13:08 -0700 (PDT) Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-595-NO1yCqGVMcq22D6ZSjNdBQ-1; Fri, 02 Oct 2020 10:13:04 -0400 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 423F81019630; Fri, 2 Oct 2020 14:12:58 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A199A60BE2; Fri, 2 Oct 2020 14:12:57 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id B04B144A56; Fri, 2 Oct 2020 14:12:56 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 092ECt7u025547 for ; Fri, 2 Oct 2020 10:12:55 -0400 Received: by smtp.corp.redhat.com (Postfix) id 521C273678; Fri, 2 Oct 2020 14:12:55 +0000 (UTC) Received: from localhost.localdomain.com (ovpn-114-9.ams2.redhat.com [10.36.114.9]) by smtp.corp.redhat.com (Postfix) with ESMTP id 86A4960DA0; Fri, 2 Oct 2020 14:12:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1601647987; 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=YSV0odiUMBMf5h49XrSSerU0KeREmYX4+K2L+TNvZCs=; b=fO9vdLF5owjiUUE2D/HOjeIAETtt4TBKhfc9MId1aGQD9rEPHpAfUaUs9FhDuZh0W33j56 sdsyj1Ggl8o0juPv8rwySGlOTayiN3vtEGuaUtjfBCH+aX+8v+K2kVnESIyRRSXxeWre1Q LJRUOXcRZafB+pt+FQWyRSF/YmCog0U= X-MC-Unique: NO1yCqGVMcq22D6ZSjNdBQ-1 From: =?UTF-8?q?Daniel=20P=2E=20Berrang=C3=A9?= To: libvir-list@redhat.com Subject: [libvirt PATCH 1/5] docs: fix misc spelling errors reported by codespell Date: Fri, 2 Oct 2020 15:12:45 +0100 Message-Id: <20201002141249.2378101-2-berrange@redhat.com> In-Reply-To: <20201002141249.2378101-1-berrange@redhat.com> References: <20201002141249.2378101-1-berrange@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-loop: libvir-list@redhat.com X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 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-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) Signed-off-by: Daniel P. Berrang=C3=A9 Reviewed-by: Peter Krempa --- NEWS.rst | 8 ++++---- docs/auth.html.in | 2 +- docs/daemons.rst | 4 ++-- docs/drvesx.html.in | 6 +++--- docs/drvxen.html.in | 2 +- docs/format.html.in | 2 +- docs/formatdomain.rst | 6 +++--- docs/formatdomaincaps.html.in | 2 +- docs/formatnetwork.html.in | 4 ++-- docs/formatnode.html.in | 2 +- docs/formatstorage.html.in | 2 +- docs/formatstoragecaps.html.in | 2 +- docs/hooks.html.in | 4 ++-- docs/kbase/backing_chains.rst | 2 +- docs/kbase/debuglogs.rst | 6 +++--- docs/kbase/kvm-realtime.rst | 2 +- docs/kbase/migrationinternals.rst | 2 +- docs/kbase/rpm-deployment.rst | 2 +- docs/logos/README | 2 +- docs/manpages/virsh.rst | 2 +- docs/manpages/virt-login-shell.rst | 8 ++++---- docs/schemas/basictypes.rng | 2 +- docs/schemas/domaincommon.rng | 2 +- docs/securityprocess.html.in | 2 +- docs/strategy.html.in | 2 +- docs/uri.html.in | 2 +- 26 files changed, 41 insertions(+), 41 deletions(-) diff --git a/NEWS.rst b/NEWS.rst index de46cac8c5..18b8e615a6 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -457,7 +457,7 @@ v6.3.0 (2020-05-05) libvirt can now set the "hotplug" option for pcie-root-ports and pcie-switch-downstream-ports, which can be used to disable hotplug/unp= lug of devices from these ports (default behavior is for these controllers= to - accept all hotplug/unplug attempts, but this is often undesireable). + accept all hotplug/unplug attempts, but this is often undesirable). =20 * vbox: added support for version 6.0 and 6.1 APIs =20 @@ -941,7 +941,7 @@ v5.10.0 (2019-12-02) =20 * Forcibly create nodes in domain's namespace =20 - The QEMU driver starts a domain in a namepsace with private ``/dev`` a= nd + The QEMU driver starts a domain in a namespace with private ``/dev`` a= nd creates only those nodes there which the domain is configured to have. However, it may have happened that if a node changed its minor number = this change wasn't propagated to the namespace. @@ -1244,7 +1244,7 @@ v5.6.0 (2019-08-05) =20 * network: Allow passing arbitrary options to dnsmasq =20 - This works similarly to the existing support for passing arbitary opti= ons + This works similarly to the existing support for passing arbitrary opt= ions to QEMU, and just like that feature it comes with no support guarantee= s. =20 * **Removed features** @@ -2258,7 +2258,7 @@ v4.4.0 (2018-06-04) =20 * **Improvements** =20 - * qemu: Add suport for OpenGL rendering with SDL + * qemu: Add support for OpenGL rendering with SDL =20 Domains using SDL as a graphics backend will now be able to use OpenGL accelerated rendering. diff --git a/docs/auth.html.in b/docs/auth.html.in index 9964313776..9b940a8598 100644 --- a/docs/auth.html.in +++ b/docs/auth.html.in @@ -277,7 +277,7 @@ to turn on SASL auth in these listeners.

Since the libvirt SASL config file defaults to using GSSAPI (Kerberos), a config change is required to enable plain password auth. This is done by -editting /etc/sasl2/libvirt.conf to set the mech_list +editing /etc/sasl2/libvirt.conf to set the mech_list parameter to scram-sha-1.

diff --git a/docs/daemons.rst b/docs/daemons.rst index e0b95105e4..2cd6b47c2a 100644 --- a/docs/daemons.rst +++ b/docs/daemons.rst @@ -512,7 +512,7 @@ other end of which are owned by the ``virtlogd`` daemon= . It will then write data on those pipes to log files, while enforcing a maximum file size and performing log rollover at the size limit. =20 -Since the daemon holds open anoymous pipe file descriptors, it must never = be +Since the daemon holds open anonymous pipe file descriptors, it must never= be stopped while any QEMU virtual machines are running. To enable software up= dates to be applied, the daemon is capable of re-executing itself while keeping = all file descriptors open. This can be triggered by sending the daemon ``SIGUS= R1`` @@ -605,7 +605,7 @@ images and devices serving as backing storage for virtu= al disks. The locks will be held for as long as there is a QEMU process running with the disk open. =20 -To ensure continuity of locking, the daemon holds open anoymous file +To ensure continuity of locking, the daemon holds open anonymous file descriptors, it must never be stopped while any QEMU virtual machines are running. To enable software updates to be applied, the daemon is capable of re-executing itself while keeping all file descriptors open. This can be diff --git a/docs/drvesx.html.in b/docs/drvesx.html.in index 3acb7e5c51..c56da16f57 100644 --- a/docs/drvesx.html.in +++ b/docs/drvesx.html.in @@ -221,7 +221,7 @@ vpx://example-vcenter.com/folder1/dc1/folder2/example-e= sx.com using the CA certificate pool installed on your client computer. W= ith an out-of-the-box installed ESX server this won't work, because a = newly installed ESX server uses auto-generated self-signed certificates. - Those are singed by a CA certificate that is typically not known t= o your + Those are signed by a CA certificate that is typically not known t= o your client computer and libvirt will report an error like this one: 

@@ -322,9 +322,9 @@ error: invalid argument in libvirt was built without th=
e 'esx' driver
     

=20
=20
-    
Specialties in the domain XML config

+    
Specialities in the domain XML config

     

-        There are several specialties in the domain XML config for ESX dom=
ains.
+        There are several specialities in the domain XML config for ESX do=
mains.
     

=20
     
Restrictions

diff --git a/docs/drvxen.html.in b/docs/drvxen.html.in
index 45a9329fcf..da94952e42 100644
--- a/docs/drvxen.html.in
+++ b/docs/drvxen.html.in
@@ -154,7 +154,7 @@ vif =3D [ "mac=3D00:16:3e:60:36:ba,bridge=3Dvirbr0,scri=
pt=3Dvif-bridge,vifname=3Dvif5.0" ]
       <xen:commandline> describing each argument passed=
 to
       the device model when starting the domain.
     

-    
The following example illustrates passing agruments to the QEMU dev=
ice
+    
The following example illustrates passing arguments to the QEMU dev=
ice
       model that define a floppy drive, which Xen does not support through=
 its
       public APIs:
     

diff --git a/docs/format.html.in b/docs/format.html.in
index d013528fe0..1d2456de6f 100644
--- a/docs/format.html.in
+++ b/docs/format.html.in
@@ -35,7 +35,7 @@
     

       The virt-xml-validate tool provides a simple command li=
ne
       for validating XML documents prior to giving them to libvirt. It uses
-      the locally instaled RNG schema documents. It will auto-detect which
+      the locally installed RNG schema documents. It will auto-detect which
       schema to use for validation based on the name of the top level elem=
ent
       in the input document. Thus it merely requires the XML document file=
name
       to be passed on the command line
diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst
index f3cf9e1fb3..0930d09c5e 100644
--- a/docs/formatdomain.rst
+++ b/docs/formatdomain.rst
@@ -45,7 +45,7 @@ General metadata
=20
 ``name``
    The content of the ``name`` element provides a short name for the virtu=
al
-   machine. This name should consist only of alpha-numeric characters and =
is
+   machine. This name should consist only of alphanumeric characters and is
    required to be unique within the scope of a single host. It is often us=
ed to
    form the filename for storing the persistent configuration file.
    :since:`Since 0.0.1`
@@ -804,7 +804,7 @@ CPU Tuning
 ``vcpusched``, ``iothreadsched`` and ``emulatorsched``
    The optional ``vcpusched``, ``iothreadsched`` and ``emulatorsched`` ele=
ments
    specify the scheduler type (values ``batch``, ``idle``, ``fifo``, ``rr`=
`) for
-   particular vCPU, IOThread and emulator threads respecively. For ``vcpus=
ched``
+   particular vCPU, IOThread and emulator threads respectively. For ``vcpu=
sched``
    and ``iothreadsched`` the attributes ``vcpus`` and ``iothreads`` select=
 which
    vCPUs/IOThreads this setting applies to, leaving them out sets the defa=
ult.
    The element ``emulatorsched`` does not have that attribute. Valid ``vcp=
us``
@@ -4422,7 +4422,7 @@ Generic ethernet connection
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
=20
 Provides a means to use a new or existing tap device (or veth device pair,
-depening on the needs of the hypervisor driver) that is partially or wholly
+depending on the needs of the hypervisor driver) that is partially or whol=
ly
 setup external to libvirt (either prior to the guest starting, or while the
 guest is being started via an optional script specified in the config).
=20
diff --git a/docs/formatdomaincaps.html.in b/docs/formatdomaincaps.html.in
index 1506f79818..65ab5574d3 100644
--- a/docs/formatdomaincaps.html.in
+++ b/docs/formatdomaincaps.html.in
@@ -152,7 +152,7 @@
       values for which a firmware "descriptor file" exists on the host.
       Firmware descriptor file is a small JSON document that describes
       details about a given BIOS or UEFI binary on the host, e.g. the
-      fimware binary path, its architecture, supported machine types,
+      firmware binary path, its architecture, supported machine types,
       NVRAM template, etc. This ensures that the reported values won't
       cause a failure on guest boot.
     

diff --git a/docs/formatnetwork.html.in b/docs/formatnetwork.html.in
index 94a4cab4d1..f26909bec8 100644
--- a/docs/formatnetwork.html.in
+++ b/docs/formatnetwork.html.in
@@ -48,7 +48,7 @@
       
name

       
The content of the name element provides
         a short name for the virtual network. This name should
-        consist only of alpha-numeric characters and is required
+        consist only of alphanumeric characters and is required
         to be unique within the scope of a single host. It is
         used to form the filename for storing the persistent
         configuration file. Since 0.3.0

@@ -1249,7 +1249,7 @@
     above) which you can use at will.

=20
     
Many operating systems will not consider these addresses as
-    preferential to IPv4, due to some practial history of these
+    preferential to IPv4, due to some practical history of these
     addresses being present but unroutable and causing networking
     issues.  On many Linux distributions, you may need to
     override /etc/gai.conf with values
diff --git a/docs/formatnode.html.in b/docs/formatnode.html.in
index 4c7de50a0b..594427468b 100644
--- a/docs/formatnode.html.in
+++ b/docs/formatnode.html.in
@@ -145,7 +145,7 @@
                     device's sysfs directory) the capability element will =
also
                     have an attribute named maxCount which is=
 the
                     maximum number of SRIOV VFs supported by this device, =
which
-                    could be higher than the number of VFs that are curent=
ly
+                    could be higher than the number of VFs that are curren=
tly
                     active since 1.3.0; in th=
is case,
                     even if there are currently no active VFs the
                     virtual_functions capabililty will still be shown.
diff --git a/docs/formatstorage.html.in b/docs/formatstorage.html.in
index 8eee7ccf9e..cac44503da 100644
--- a/docs/formatstorage.html.in
+++ b/docs/formatstorage.html.in
@@ -356,7 +356,7 @@
                 which of the scsi_host adapters for the provided PCI addre=
ss
                 should be used. The value is determine by contents of the
                 unique_id file for the specific scsi_host ada=
pter.
-                For a PCI address of "0000:00:1f:2", the unique identifer =
files
+                For a PCI address of "0000:00:1f:2", the unique identifier=
 files
                 can be found using the command
                 find -H /sys/class/scsi_host/host*/unique_id |
                 xargs grep '[0-9]'. Optionally, the
diff --git a/docs/formatstoragecaps.html.in b/docs/formatstoragecaps.html.in
index d8a1cacd96..900303aef7 100644
--- a/docs/formatstoragecaps.html.in
+++ b/docs/formatstoragecaps.html.in
@@ -64,7 +64,7 @@
 </storagepoolCapabilities>
=20 -

The following section decribes subelements of the +

The following section describes subelements of the poolOptions and volOptions subelements

: =20
diff --git a/docs/hooks.html.in b/docs/hooks.html.in index a38ba05522..bbbc414dc4 100644 --- a/docs/hooks.html.in +++ b/docs/hooks.html.in @@ -203,7 +203,7 @@ /etc/libvirt/hooks/qemu.d/. They are executed in alphabetical order after main script. In this case each script also acts as filter and can modify the domain XML and print it out on - its standart output. This script output is passed to standard input + its standard output. This script output is passed to standard input next script in order. Empty output from any script is also identic= al to copying the input XML without changing it. In case any script returns failure common process will be aborted, @@ -296,7 +296,7 @@ /etc/libvirt/hooks/libxl.d/. They are executed in alphabetical order after main script. In this case each script also acts as filter and can modify the domain XML and print it out on - its standart output. This script output is passed to standard input + its standard output. This script output is passed to standard input next script in order. Empty output from any script is also identic= al to copying the input XML without changing it. In case any script returns failure common process will be aborted, diff --git a/docs/kbase/backing_chains.rst b/docs/kbase/backing_chains.rst index c3de37f4d1..89920a61b1 100644 --- a/docs/kbase/backing_chains.rst +++ b/docs/kbase/backing_chains.rst @@ -186,7 +186,7 @@ of the following criteria is met: - ``backing file`` is present AND is correct/trusted =20 Note that the last criterion may require manual inspection and thus should= not -be scripted unless the trust for the image can be expressed programaticall= y. +be scripted unless the trust for the image can be expressed programmatical= ly. =20 Also note that the above steps may need to be repeated recursively for any subsequent backing images. diff --git a/docs/kbase/debuglogs.rst b/docs/kbase/debuglogs.rst index 956ebc6af9..7945cf8bed 100644 --- a/docs/kbase/debuglogs.rst +++ b/docs/kbase/debuglogs.rst @@ -163,10 +163,10 @@ explicitly stated, these work on libvirt 4.4.0 and la= ter. Please note that some of the filters below may not log enough information for filing a proper li= bvirt bug. Usually it's better to log more than less. =20 -Targetted logging for debugging QEMU VMs -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Targeted logging for debugging QEMU VMs +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ =20 -Specifying only some sections allows for a targetted filter configuration = which +Specifying only some sections allows for a targeted filter configuration w= hich works on all versions and is sufficient for most cases. =20 :: diff --git a/docs/kbase/kvm-realtime.rst b/docs/kbase/kvm-realtime.rst index 2e1541cb4d..476e581a2a 100644 --- a/docs/kbase/kvm-realtime.rst +++ b/docs/kbase/kvm-realtime.rst @@ -137,7 +137,7 @@ do not include any CPU affinity at this stage: =20 The guest CPUs now need to be placed individually. In this case, they will= all be put within the same host socket, such that they can be exposed as core -siblings. This is achieved using the `CPU tunning config <../formatdomain.= html#elementsCPUTuning>`_: +siblings. This is achieved using the `CPU tuning config <../formatdomain.h= tml#elementsCPUTuning>`_: =20 :: =20 diff --git a/docs/kbase/migrationinternals.rst b/docs/kbase/migrationintern= als.rst index 29bda0443b..2e187936a7 100644 --- a/docs/kbase/migrationinternals.rst +++ b/docs/kbase/migrationinternals.rst @@ -25,7 +25,7 @@ In this document, unless stated otherwise, these conventi= ons are followed: any host; =20 * 'regular migration' refers to any migration operation where the libvirt - client co-ordinates the communication between the libvirtd instances in + client coordinates the communication between the libvirtd instances in the source and destination hosts. =20 Migration protocol diff --git a/docs/kbase/rpm-deployment.rst b/docs/kbase/rpm-deployment.rst index 8f1584d7ea..568cf5b3eb 100644 --- a/docs/kbase/rpm-deployment.rst +++ b/docs/kbase/rpm-deployment.rst @@ -384,7 +384,7 @@ set of hypervisor packages too. =20 Since this installs every possible libvirt feature for the virtualization driver in question, the on-disk footprint is quite large. The in-memory -footprint of the daemons is also relatively large since alot of code is +footprint of the daemons is also relatively large since a lot of code is loaded. =20 =20 diff --git a/docs/logos/README b/docs/logos/README index 888ba18798..64dee41ec8 100644 --- a/docs/logos/README +++ b/docs/logos/README @@ -38,7 +38,7 @@ format: =20 - logo-square-powered.svg =20 - A variant of the square logo for use by 3rd party applications, to adve= rtize + A variant of the square logo for use by 3rd party applications, to adve= rtise their use of libvirt. =20 Bitmap sizes: 64, 128, 192, 256 px square diff --git a/docs/manpages/virsh.rst b/docs/manpages/virsh.rst index ebf4f16cf7..9ac379a4b8 100644 --- a/docs/manpages/virsh.rst +++ b/docs/manpages/virsh.rst @@ -7142,7 +7142,7 @@ checkpoint-create Create a checkpoint for domain *domain* with the properties specified in *xmlfile* describing a top-level element. The format of the input XML file will be validated against an internal RNG -schema (idential to using the virt-xml-validate(1) tool). If +schema (identical to using the virt-xml-validate(1) tool). If *xmlfile* is completely omitted, then libvirt will create a checkpoint with a name based on the current time. =20 diff --git a/docs/manpages/virt-login-shell.rst b/docs/manpages/virt-login-= shell.rst index 3833a3e912..1e95d5d2b4 100644 --- a/docs/manpages/virt-login-shell.rst +++ b/docs/manpages/virt-login-shell.rst @@ -29,7 +29,7 @@ configured in ``/etc/libvirt/virt-login-shell.conf``. =20 The basic structure of most ``virt-login-shell`` usage is: =20 -.. code-block:: +.. code-block:: shell =20 virt-login-shell =20 @@ -58,7 +58,7 @@ By default, ``virt-login-shell`` will execute the ``/bin/= sh`` program for the user. You can modify this behaviour by defining the shell variable in ``/etc/libvirt/virt-login-shell.conf``. e.g. =20 -.. code-block:: +.. code-block:: shell =20 shell =3D [ "/bin/bash" ] =20 @@ -68,7 +68,7 @@ detect the shell from ``/etc/password`` inside the contai= ner. This should only be done if the container has a separate ``/etc`` directory from the host, otherwise it will end up recursively invoking ``virt-login-shell``. e.g. =20 -.. code-block:: +.. code-block:: shell =20 auto_shell =3D 1 =20 @@ -77,7 +77,7 @@ By default no users are allowed to use virt-login-shell, = if you want to allow certain users to use virt-login-shell, you need to modify the allowed_users variable in /etc/libvirt/virt-login-shell.conf. e.g. =20 -.. code-block:: +.. code-block:: shell =20 allowed_users =3D [ "tom", "dick", "harry" ] =20 diff --git a/docs/schemas/basictypes.rng b/docs/schemas/basictypes.rng index 79d96451f1..33b554f8d1 100644 --- a/docs/schemas/basictypes.rng +++ b/docs/schemas/basictypes.rng @@ -167,7 +167,7 @@ - + diff --git a/docs/schemas/domaincommon.rng b/docs/schemas/domaincommon.rng index 4b7e460148..316d93fb69 100644 --- a/docs/schemas/domaincommon.rng +++ b/docs/schemas/domaincommon.rng @@ -5580,7 +5580,7 @@ =20