Fix some typos

Signed-off-by: Tim Wiederhake <twiederh@redhat.com>
This commit is contained in:
Tim Wiederhake 2023-03-09 14:09:16 +01:00
parent 3138e204b2
commit bc77182ea4
7 changed files with 11 additions and 11 deletions

View File

@ -258,7 +258,7 @@ v8.10.0 (2022-12-01)
* Support for SGX EPC (enclave page cache) * Support for SGX EPC (enclave page cache)
Users can add a ``<memory model='sgx-epc'>`` device to lauch a VM with Users can add a ``<memory model='sgx-epc'>`` device to launch a VM with
``Intel Software Guard Extensions``. ``Intel Software Guard Extensions``.
* Support migration of vTPM state of QEMU vms on shared storage * Support migration of vTPM state of QEMU vms on shared storage
@ -295,7 +295,7 @@ v8.10.0 (2022-12-01)
* RPM packaging changes * RPM packaging changes
- add optional dependancy of ``libvirt-daemon`` on ``libvirt-client`` - add optional dependency of ``libvirt-daemon`` on ``libvirt-client``
The ``libvirt-guests.`` tool requires the ``virsh`` client to work The ``libvirt-guests.`` tool requires the ``virsh`` client to work
properly, but we don't want to require the installation of the daemon properly, but we don't want to require the installation of the daemon
@ -321,7 +321,7 @@ v8.10.0 (2022-12-01)
* Allow incoming connections to guests on routed networks w/firewalld * Allow incoming connections to guests on routed networks w/firewalld
A change in handling of implicit rules in ``firewalld 1.0.0`` broke A change in handling of implicit rules in ``firewalld 1.0.0`` broke
incomming connections to VMs when using ``routed`` network. This is fixed incoming connections to VMs when using ``routed`` network. This is fixed
by adding a new ``libvirt-routed`` zone configured to once again allow by adding a new ``libvirt-routed`` zone configured to once again allow
incoming sessions to guests on routed networks. incoming sessions to guests on routed networks.

View File

@ -7576,7 +7576,7 @@ feature is planned for a future version of libvirt.
Having multiple watchdogs is usually not something very common, but be aware Having multiple watchdogs is usually not something very common, but be aware
that this might happen, for example, when an implicit watchdog device is added that this might happen, for example, when an implicit watchdog device is added
as part of another device. For example whe iTCO watchdog being part of the ich9 as part of another device. For example the iTCO watchdog being part of the ich9
southbridge, which is used with the q35 machine type. :since:`Since 9.1.0` southbridge, which is used with the q35 machine type. :since:`Since 9.1.0`
:: ::

View File

@ -460,7 +460,7 @@ With it launched, it is possible to query the launch measurement::
sev-build-id : 15 sev-build-id : 15
sev-policy : 3 sev-policy : 3
The techiques required to validate the measurement reported are beyond the The techniques required to validate the measurement reported are beyond the
scope of this document. Fortunately, libvirt provides a tool that can be used scope of this document. Fortunately, libvirt provides a tool that can be used
to perform this validation:: to perform this validation::

View File

@ -21,7 +21,7 @@
# #
# NOTE: This directly references specific structures and places in the # NOTE: This directly references specific structures and places in the
# kernel source code. It is expected that this example will need to be # kernel source code. It is expected that this example will need to be
# editted to match the kernel you intend to run it against. # edited to match the kernel you intend to run it against.
# #
# The captured VMSA will be printed to the console in hex format, # The captured VMSA will be printed to the console in hex format,
# and can be converted to the required binary format by feeding # and can be converted to the required binary format by feeding
@ -42,8 +42,8 @@ function dump_vmsa(addr:long) {
} }
# This line number will need to be updated for the specific kernel # This line number will need to be updated for the specific kernel
# version that is being probed. The line that needs to be targetted # version that is being probed. The line that needs to be targeted
# is the one beween the call to clflush_cache_range(...) and the # is the one between the call to clflush_cache_range(...) and the
# call to sev_issue_cmd(kvm, SEV_CMD_LAUNCH_UPDATE...). # call to sev_issue_cmd(kvm, SEV_CMD_LAUNCH_UPDATE...).
# #
# Line 635 is correct for Linux v6.3 # Line 635 is correct for Linux v6.3

View File

@ -98,7 +98,7 @@ qemuFDPassNew(const char *prefix,
/** /**
* qemuFDPassNewPassed: * qemuFDPassNewPassed:
* @fdSetID: ID of an FDset which was allready passed to qemu * @fdSetID: ID of an FDset which was already passed to qemu
* *
* Create qemuFDPass pointing to an already passed FD. Useful to use with * Create qemuFDPass pointing to an already passed FD. Useful to use with
* qemuFDPassTransferMonitorRollback, when restoring after restart. * qemuFDPassTransferMonitorRollback, when restoring after restart.

View File

@ -330,7 +330,7 @@ virStorageSourceChainLookup(virStorageSource *chain,
* *
* Looks up a storage source definition corresponding to @base in @chain. * Looks up a storage source definition corresponding to @base in @chain.
* *
* Returns virStorageSource withing chain or NULL if not found. * Returns virStorageSource within chain or NULL if not found.
*/ */
virStorageSource * virStorageSource *
virStorageSourceChainLookupBySource(virStorageSource *chain, virStorageSourceChainLookupBySource(virStorageSource *chain,

View File

@ -476,7 +476,7 @@ qemuTestCapsCacheInsertImpl(virFileCache *cache,
size_t i; size_t i;
if (virQEMUCapsGetArch(caps) != VIR_ARCH_NONE) { if (virQEMUCapsGetArch(caps) != VIR_ARCH_NONE) {
/* all tests using real caps or arcitecture are expected to call: /* all tests using real caps or architecture are expected to call:
* *
* virFileCacheClear(driver.qemuCapsCache); * virFileCacheClear(driver.qemuCapsCache);
* *