External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-09-30 11:25:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: fix writing of QEMU

Browse Source 
QEMU should be written all upper or all lower case.
This commit is contained in:
Philipp Hahn 2017-03-07 18:09:58 +01:00 committed by Martin Kletzander
parent 6f5687498f
commit d7dcea6f60
11 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/formatnwfilter.html.in
View File

@ -40,7 +40,7 @@
of all running virtual machines that reference this filter are updated.
<br/><br/>
Network filtering support is available <span class="since">since 0.8.1
(Qemu, KVM)</span>
(QEMU, KVM)</span>
</p>
<h2><a name="nwfconcepts">Concepts</a></h2>
@ -2064,7 +2064,7 @@ echo 3 > /proc/sys/net/netfilter/nf_conntrack_icmp_timeout
traffic you want to allow does pass.
<br/><br/>
The network filtering subsystem is currently only available on
Linux hosts and only works for Qemu and KVM type of virtual machines.
Linux hosts and only works for QEMU and KVM type of virtual machines.
On Linux
it builds upon the support for <code>ebtables</code>, <code>iptables
</code> and <code>ip6tables</code> and makes use of their features.
@ -2265,7 +2265,7 @@ echo 3 > /proc/sys/net/netfilter/nf_conntrack_icmp_timeout
to the incoming and outgoing direction. All this is related to the ftp
data traffic originating from TCP port 20 of the VM. This then leads to
the following solution
<span class="since">(since 0.8.5 (Qemu, KVM, UML))</span>:
<span class="since">(since 0.8.5 (QEMU, KVM, UML))</span>:
</p>
<pre>
&lt;filter name='test-eth0'&gt;

12
docs/storage.html.in
View File

@ -543,13 +543,13 @@
This storage driver provides a pool which contains all RBD
images in a RADOS pool. RBD (RADOS Block Device) is part
of the Ceph distributed storage project.<br/>
This backend <i>only</i> supports Qemu with RBD support. Kernel RBD
This backend <i>only</i> supports QEMU with RBD support. Kernel RBD
which exposes RBD devices as block devices in /dev is <i>not</i>
supported. RBD images created with this storage backend
can be accessed through kernel RBD if configured manually, but
this backend does not provide mapping for these images.<br/>
Images created with this backend can be attached to Qemu guests
when Qemu is build with RBD support (Since Qemu 0.14.0). The
Images created with this backend can be attached to QEMU guests
when QEMU is build with RBD support (Since QEMU 0.14.0). The
backend supports cephx authentication for communication with the
Ceph cluster. Storing the cephx authentication key is done with
the libvirt secret mechanism. The UUID in the example pool input
@ -595,7 +595,7 @@
&lt;/volume&gt;</pre>
<h3>Example disk attachment</h3>
<p>RBD images can be attached to Qemu guests when Qemu is built
<p>RBD images can be attached to QEMU guests when QEMU is built
with RBD support. Information about attaching a RBD image to a
guest can be found
at <a href="formatdomain.html#elementsDisks">format domain</a>
@ -654,7 +654,7 @@
&lt;/volume&gt;</pre>
<h3>Example disk attachment</h3>
<p>Sheepdog images can be attached to Qemu guests.
<p>Sheepdog images can be attached to QEMU guests.
Information about attaching a Sheepdog image to a
guest can be found
at the <a href="formatdomain.html#elementsDisks">format domain</a>
@ -739,7 +739,7 @@
&lt;/volume&gt;</pre>
<h3>Example disk attachment</h3>
<p>Files within a gluster volume can be attached to Qemu guests.
<p>Files within a gluster volume can be attached to QEMU guests.
Information about attaching a Gluster image to a
guest can be found
at the <a href="formatdomain.html#elementsDisks">format domain</a>

2
libvirt.spec.in
View File

@ -732,7 +732,7 @@ parted and more.
%if %{with_qemu}
%package daemon-driver-qemu
Summary: Qemu driver plugin for the libvirtd daemon
Summary: QEMU driver plugin for the libvirtd daemon
Group: Development/Libraries
Requires: libvirt-daemon = %{version}-%{release}
# There really is a hard cross-driver dependency here

2
src/cpu/cpu_s390.c
View File

@ -38,7 +38,7 @@ virCPUs390Compare(virCPUDefPtr host ATTRIBUTE_UNUSED,
virCPUDefPtr cpu ATTRIBUTE_UNUSED,
bool failMessages ATTRIBUTE_UNUSED)
{
/* s390 relies on Qemu to perform all runability checking. Return
/* s390 relies on QEMU to perform all runability checking. Return
* VIR_CPU_COMPARE_IDENTICAL to bypass Libvirt checking.
*/
return VIR_CPU_COMPARE_IDENTICAL;

2
src/qemu/MIGRATION.txt
View File

@ -1,7 +1,7 @@
QEMU Migration Phases
=====================
Qemu supports only migration protocols 2 and 3 (1 was lacking too many
QEMU supports only migration protocols 2 and 3 (1 was lacking too many
steps). Repeating the protocol sequences from libvirt.c:
Sequence v2:

2
src/qemu/THREADS.txt
View File

@ -51,7 +51,7 @@ There are a number of locks on various objects
Since virDomainObjPtr lock must not be held during sleeps, the job
conditions provide additional protection for code making updates.
Qemu driver uses two kinds of job conditions: asynchronous and
QEMU driver uses two kinds of job conditions: asynchronous and
normal.
Asynchronous job condition is used for long running jobs (such as

4
src/qemu/qemu.conf
View File

@ -366,7 +366,7 @@
# "/dev/infiniband/uverbs0"
# The default format for Qemu/KVM guest save images is raw; that is, the
# The default format for QEMU/KVM guest save images is raw; that is, the
# memory from the domain is dumped out directly to a file. If you have
# guests with a large amount of memory, however, this can take up quite
# a bit of space. If you would like to compress the images while they
@ -646,7 +646,7 @@
#
#stdio_handler = "logd"
# Qemu gluster libgfapi log level, debug levels are 0-9, with 9 being the
# QEMU gluster libgfapi log level, debug levels are 0-9, with 9 being the
# most verbose, and 0 representing no debugging output.
#
# The current logging levels defined in the gluster GFAPI are:

2
src/qemu/qemu_command.c
View File

@ -1299,7 +1299,7 @@ qemuCheckCCWS390AddressSupport(const virDomainDef *def,
}
/* Qemu 1.2 and later have a binary flag -enable-fips that must be
/* QEMU 1.2 and later have a binary flag -enable-fips that must be
* used for VNC auth to obey FIPS settings; but the flag only
* exists on Linux, and with no way to probe for it via QMP. Our
* solution: if FIPS mode is required, then unconditionally use

2
src/qemu/qemu_domain.h
View File

@ -43,7 +43,7 @@
VIR_DOMAIN_XML_UPDATE_CPU)
# if ULONG_MAX == 4294967295
/* Qemu has a 64-bit limit, but we are limited by our historical choice of
/* QEMU has a 64-bit limit, but we are limited by our historical choice of
* representing bandwidth in a long instead of a 64-bit int. */
# define QEMU_DOMAIN_MIG_BANDWIDTH_MAX ULONG_MAX
# else

6
src/qemu/qemu_monitor.c
View File

@ -953,7 +953,7 @@ qemuMonitorClose(qemuMonitorPtr mon)
virErrorPtr err = virSaveLastError();
virReportError(VIR_ERR_OPERATION_FAILED, "%s",
_("Qemu monitor was closed"));
_("QEMU monitor was closed"));
virCopyLastError(&mon->lastError);
if (err) {
virSetError(err);
@ -3493,7 +3493,7 @@ qemuMonitorVMStatusToPausedReason(const char *status)
return VIR_DOMAIN_PAUSED_UNKNOWN;
if ((st = qemuMonitorVMStatusTypeFromString(status)) < 0) {
VIR_WARN("Qemu reported unknown VM status: '%s'", status);
VIR_WARN("QEMU reported unknown VM status: '%s'", status);
return VIR_DOMAIN_PAUSED_UNKNOWN;
}
@ -3516,7 +3516,7 @@ qemuMonitorVMStatusToPausedReason(const char *status)
return VIR_DOMAIN_PAUSED_USER;
case QEMU_MONITOR_VM_STATUS_RUNNING:
VIR_WARN("Qemu reports the guest is paused but status is 'running'");
VIR_WARN("QEMU reports the guest is paused but status is 'running'");
return VIR_DOMAIN_PAUSED_UNKNOWN;
case QEMU_MONITOR_VM_STATUS_SAVE_VM:

2
src/qemu/qemu_parse_command.c
View File

@ -417,7 +417,7 @@ qemuParseKeywords(const char *str,
endmark = start;
do {
/* Qemu accepts ',,' as an escape for a literal comma;
/* QEMU accepts ',,' as an escape for a literal comma;
* skip past those here while searching for the end of the
* value, then strip them down below */
endmark = strchr(endmark, ',');