libvirt can now set the "hotplug" option for pcie-root-ports and
pcie-switch-downstream-ports, which can be used to disable hotplug/unplug
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).
* vbox: added support for version 6.0 and 6.1 APIs
* Forcibly create nodes in domain's namespace
- The QEMU driver starts a domain in a namepsace with private ``/dev`` and
+ The QEMU driver starts a domain in a namespace with private ``/dev`` and
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.
* network: Allow passing arbitrary options to dnsmasq
- This works similarly to the existing support for passing arbitary options
+ This works similarly to the existing support for passing arbitrary options
to QEMU, and just like that feature it comes with no support guarantees.
* **Removed features**
* **Improvements**
- * qemu: Add suport for OpenGL rendering with SDL
+ * qemu: Add support for OpenGL rendering with SDL
Domains using SDL as a graphics backend will now be able to use OpenGL
accelerated rendering.
<p>
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 <code>/etc/sasl2/libvirt.conf</code> to set the <code>mech_list</code>
+editing <code>/etc/sasl2/libvirt.conf</code> to set the <code>mech_list</code>
parameter to <code>scram-sha-1</code>.
</p>
<p>
data on those pipes to log files, while enforcing a maximum file size and
performing log rollover at the size limit.
-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 updates
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 ``SIGUSR1``
will be held for as long as there is a QEMU process running with the disk
open.
-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
using the CA certificate pool installed on your client computer. With
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 to your
+ Those are signed by a CA certificate that is typically not known to your
client computer and libvirt will report an error like this one:
</p>
<pre>
</p>
- <h2><a id="xmlspecial">Specialties in the domain XML config</a></h2>
+ <h2><a id="xmlspecial">Specialities in the domain XML config</a></h2>
<p>
- There are several specialties in the domain XML config for ESX domains.
+ There are several specialities in the domain XML config for ESX domains.
</p>
<h3><a id="restrictions">Restrictions</a></h3>
<code><xen:commandline></code> describing each argument passed to
the device model when starting the domain.
</p>
- <p>The following example illustrates passing agruments to the QEMU device
+ <p>The following example illustrates passing arguments to the QEMU device
model that define a floppy drive, which Xen does not support through its
public APIs:
</p>
<p>
The <code>virt-xml-validate</code> tool provides a simple command line
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 element
in the input document. Thus it merely requires the XML document filename
to be passed on the command line
``name``
The content of the ``name`` element provides a short name for the virtual
- 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 used to
form the filename for storing the persistent configuration file.
:since:`Since 0.0.1`
``vcpusched``, ``iothreadsched`` and ``emulatorsched``
The optional ``vcpusched``, ``iothreadsched`` and ``emulatorsched`` elements
specify the scheduler type (values ``batch``, ``idle``, ``fifo``, ``rr``) for
- particular vCPU, IOThread and emulator threads respecively. For ``vcpusched``
+ particular vCPU, IOThread and emulator threads respectively. For ``vcpusched``
and ``iothreadsched`` the attributes ``vcpus`` and ``iothreads`` select which
vCPUs/IOThreads this setting applies to, leaving them out sets the default.
The element ``emulatorsched`` does not have that attribute. Valid ``vcpus``
^^^^^^^^^^^^^^^^^^^^^^^^^^^
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 wholly
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).
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.
</p>
<dt><code>name</code></dt>
<dd>The content of the <code>name</code> 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. <span class="since">Since 0.3.0</span></dd>
above) which you can use at will.</p>
<p>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 <tt>/etc/gai.conf</tt> with values
device's sysfs directory) the capability element will also
have an attribute named <code>maxCount</code> which is the
maximum number of SRIOV VFs supported by this device, which
- could be higher than the number of VFs that are curently
+ could be higher than the number of VFs that are currently
active <span class="since">since 1.3.0</span>; in this case,
even if there are currently no active VFs the
virtual_functions capabililty will still be shown.
which of the scsi_host adapters for the provided PCI address
should be used. The value is determine by contents of the
<code>unique_id</code> file for the specific scsi_host adapter.
- 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
<code>find -H /sys/class/scsi_host/host*/unique_id |
xargs grep '[0-9]'</code>. Optionally, the
</storagepoolCapabilities>
</pre>
- <p>The following section decribes subelements of the
+ <p>The following section describes subelements of the
<code>poolOptions</code> and <code>volOptions</code> subelements </p>:
<dl>
<code>/etc/libvirt/hooks/qemu.d/</code>. 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 identical
to copying the input XML without changing it.
In case any script returns failure common process will be aborted,
<code>/etc/libvirt/hooks/libxl.d/</code>. 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 identical
to copying the input XML without changing it.
In case any script returns failure common process will be aborted,
- ``backing file`` is present AND is correct/trusted
Note that the last criterion may require manual inspection and thus should not
-be scripted unless the trust for the image can be expressed programatically.
+be scripted unless the trust for the image can be expressed programmatically.
Also note that the above steps may need to be repeated recursively for any
subsequent backing images.
of the filters below may not log enough information for filing a proper libvirt
bug. Usually it's better to log more than less.
-Targetted logging for debugging QEMU VMs
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Targeted logging for debugging QEMU VMs
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Specifying only some sections allows for a targetted filter configuration which
+Specifying only some sections allows for a targeted filter configuration which
works on all versions and is sufficient for most cases.
::
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.html#elementsCPUTuning>`_:
::
any host;
* '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.
Migration protocol
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.
- logo-square-powered.svg
- A variant of the square logo for use by 3rd party applications, to advertize
+ A variant of the square logo for use by 3rd party applications, to advertise
their use of libvirt.
Bitmap sizes: 64, 128, 192, 256 px square
Create a checkpoint for domain *domain* with the properties specified
in *xmlfile* describing a <domaincheckpoint> 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.
<!--such as dnsmasq to assign a specific IP address (and optionally a -->
<!--name to an interface. The applicable standards are RFC3315 and -->
<!--RFC6355. These standards actually require the duid to be fixed for -->
- <!--the hardward device and applicable to all network interfaces on -->
+ <!--the hardware device and applicable to all network interfaces on -->
<!--that device. It is not clear that any software currently enforces -->
<!--this requirement although it could be implemented manually. -->
<!--====================================================================-->
<!--
System information specification:
- Placeholder for system specific informations likes the ones
+ Placeholder for system specific information likes the ones
contained in the SMBIOS area.
Only a limited subset of entries can be modified there, so we
fully enumerate each case here.
the various vendors who distribute libvirt. The team is responsible
for analysing incoming reports from users to identify whether a
security problem exists and its severity. It then works to produce
- a fix for all official stable branches of libvirt and co-ordinate
+ a fix for all official stable branches of libvirt and coordinate
embargo dates between vendors to allow simultaneous release of the
fix by all affected parties.
</p>
<dt>C</dt>
<dd>Large parts of the core libvirt library, daemons, and helper tools
will continue to make use in the C language. Integration of other
- languages will be an incremental, targetted process where they can
+ languages will be an incremental, targeted process where they can
bring the greatest benefit.</dd>
<dt>Rust / Go</dt>
<dd>Parts of the core libvirt library, daemons and helper tools are to
</td>
<td> tls </td>
<td>
- A vaid GNUTLS priority string
+ A valid GNUTLS priority string
</td>
</tr>
<tr>
projects / thirdparty / libvirt.git / commitdiff
