mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-01-10 05:17:59 +03:00
Fix minor typos
This commit is contained in:
parent
5e010605d1
commit
5efa7f2a4b
@ -21,7 +21,7 @@
|
||||
command line tool command '<code>capabilities</code>', it dumps the XML
|
||||
associated to the current connection. </p>
|
||||
|
||||
<p>As can be seen seen in the <a href="#elementExamples">example</a>, the
|
||||
<p>As can be seen in the <a href="#elementExamples">example</a>, the
|
||||
capabilities XML consists of the <code>capabilities</code> element which
|
||||
have exactly one <code>host</code> child element to report information on
|
||||
host capabilities, and zero or more <code>guest</code> element to express
|
||||
|
@ -566,7 +566,7 @@
|
||||
|
||||
<code>order</code> allows to specify the order to add the online vcpus.
|
||||
For hypervisors/platforms that require to insert multiple vcpus at once
|
||||
the order may be be duplicated accross all vcpus that need to be
|
||||
the order may be duplicated accross all vcpus that need to be
|
||||
enabled at once. Specifying order is not necessary, vcpus are then
|
||||
added in an arbitrary order. If order info is used, it must be used for
|
||||
all online vcpus. Hypervisors may clear or update ordering information
|
||||
|
@ -13993,7 +13993,7 @@ virDomainMemorySourceDefParseXML(xmlNodePtr node,
|
||||
case VIR_DOMAIN_MEMORY_MODEL_NVDIMM:
|
||||
if (!(def->nvdimmPath = virXPathString("string(./path)", ctxt))) {
|
||||
virReportError(VIR_ERR_XML_DETAIL, "%s",
|
||||
_("path is required for model nvdimm'"));
|
||||
_("path is required for model 'nvdimm'"));
|
||||
goto cleanup;
|
||||
}
|
||||
break;
|
||||
|
@ -872,7 +872,7 @@ void qemuAgentClose(qemuAgentPtr mon)
|
||||
* VIR_DOMAIN_QEMU_AGENT_COMMAND_BLOCK(-2), this function will block forever
|
||||
* waiting for the result. The value of
|
||||
* VIR_DOMAIN_QEMU_AGENT_COMMAND_DEFAULT(-1) means use default timeout value
|
||||
* and VIR_DOMAIN_QEMU_AGENT_COMMAND_NOWAIT(0) makes this this function return
|
||||
* and VIR_DOMAIN_QEMU_AGENT_COMMAND_NOWAIT(0) makes this function return
|
||||
* immediately without waiting. Any positive value means the number of seconds
|
||||
* to wait for the result.
|
||||
*
|
||||
|
@ -1843,7 +1843,7 @@ qemuBuildDriveStr(virDomainDiskDefPtr disk,
|
||||
if (disk->error_policy == VIR_DOMAIN_DISK_ERROR_POLICY_ENOSPACE) {
|
||||
/* in the case of enospace, the option is spelled
|
||||
* differently in qemu, and it's only valid for werror,
|
||||
* not for rerror, so leave leave rerror NULL.
|
||||
* not for rerror, so leave rerror NULL.
|
||||
*/
|
||||
wpolicy = "enospc";
|
||||
} else if (!rpolicy) {
|
||||
@ -7242,7 +7242,7 @@ qemuBuildMachineCommandLine(virCommandPtr cmd,
|
||||
for (i = 0; i < def->nmems; i++) {
|
||||
if (def->mems[i]->model == VIR_DOMAIN_MEMORY_MODEL_NVDIMM) {
|
||||
virReportError(VIR_ERR_CONFIG_UNSUPPORTED, "%s",
|
||||
_("nvdimm not is not available "
|
||||
_("nvdimm is not available "
|
||||
"with this QEMU binary"));
|
||||
return -1;
|
||||
}
|
||||
|
@ -8717,7 +8717,7 @@ qemuDomainGetStorageSourceByDevstr(const char *devstr,
|
||||
|
||||
if (!disk) {
|
||||
virReportError(VIR_ERR_INVALID_ARG,
|
||||
_("failed to find disk '%s"), target);
|
||||
_("failed to find disk '%s'"), target);
|
||||
goto cleanup;
|
||||
}
|
||||
|
||||
|
@ -555,7 +555,7 @@ qemuInterfaceBridgeConnect(virDomainDefPtr def,
|
||||
/* libvirt is managing the FDB of the bridge this device
|
||||
* is attaching to, so we need to turn off learning and
|
||||
* unicast_flood on the device to prevent the kernel from
|
||||
* adding any FDB entries for it. We will add add an fdb
|
||||
* adding any FDB entries for it. We will add an fdb
|
||||
* entry ourselves (during qemuInterfaceStartDevices(),
|
||||
* using the MAC address from the interface config.
|
||||
*/
|
||||
|
@ -1466,7 +1466,7 @@ qemuMonitorJSONExtractCPUInfo(virJSONValuePtr data,
|
||||
* extract results does not produce an error as libvirt can continue without
|
||||
* this information.
|
||||
*
|
||||
* Returns 0 on success success, -1 on a fatal error (oom ...) and -2 if the
|
||||
* Returns 0 on success, -1 on a fatal error (oom ...) and -2 if the
|
||||
* query failed gracefully.
|
||||
*/
|
||||
int
|
||||
|
Loading…
Reference in New Issue
Block a user