From 1f2f055bc3d0eb4b8e6dd3fcff23ff9744f7b84c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ville=20Skytt=C3=A4?= connect_driver
attribute
is LXC
and the domain_name
- attribute is demo
, and match on a action
+ attribute is demo
, and match on an action
name of org.libvirt.api.domain.getattr
. Using
the javascript rules format, this ends up written as
Used to enumerate a set of object available to an given +
Used to enumerate a set of object available to a given hypervisor connection such as:
start --console domname-
NB: An bootloader configured to require user interaction will prevent +
NB: A bootloader configured to require user interaction will prevent
the domain from starting (and thus virsh console
or start
--console
from functioning) until the user interacts with it manually on
the VM host. Because users typically do not have access to the VM host,
diff --git a/docs/drvesx.html.in b/docs/drvesx.html.in
index 417aca4d79..901d65958a 100644
--- a/docs/drvesx.html.in
+++ b/docs/drvesx.html.in
@@ -437,7 +437,7 @@ ethernet0.checkMACAddress = "false"
auto
.vmdk
file and use it. Autodetection fails when a
SCSI controller has multiple disks attached and the SCSI controller
diff --git a/docs/drvlxc.html.in b/docs/drvlxc.html.in
index 44c49609d9..6ee9ee8646 100644
--- a/docs/drvlxc.html.in
+++ b/docs/drvlxc.html.in
@@ -429,7 +429,7 @@ be considered secure against exploits of the host OS. The sVirt SELinux
driver provides a way to secure containers even when the "user" namespace
is not used. The cost is that writing a policy to allow execution of
arbitrary OS is not practical. The SELinux sVirt policy is typically
-tailored to work with an simpler application confinement use case,
+tailored to work with a simpler application confinement use case,
as provided by the "libvirt-sandbox" project.
diff --git a/docs/errors.html.in b/docs/errors.html.in
index 8f4f7d4323..ea4272822f 100644
--- a/docs/errors.html.in
+++ b/docs/errors.html.in
@@ -29,7 +29,7 @@ set specifically to a connection with
call it with the error informationorder
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 duplicated accross all vcpus that need to be
+ the order may be duplicated across 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
@@ -4058,7 +4058,7 @@
pcie-switch-upstream-port, and of course for this to work
properly, you will need to decrease the pcie-expander-bus'
busNr accordingly so that there are enough unused bus
- numbers above it to accomodate giving out one bus number for
+ numbers above it to accommodate giving out one bus number for
the upstream-port and one for each downstream-port (in
addition to the pcie-root-port and the pcie-expander-bus
itself).
@@ -4212,7 +4212,7 @@
profileid
(in case the switch is 802.1Qbh) and
+ a profileid
(in case the switch is 802.1Qbh) and
an interfaceid
(in case the switch is Open vSwitch)
(you may also omit the other attributes, such as managerid,
typeid, or profileid, to be filled in from the
@@ -6174,7 +6174,7 @@ qemu-kvm -net nic,model=? /dev/null
set to an empty string, then VNC access is disabled. The
keymap
attribute specifies the keymap to use. It is
possible to set a limit on the validity of the password by giving
- an timestamp passwdValidTo='2010-04-09T15:51:00'
+ a timestamp passwdValidTo='2010-04-09T15:51:00'
assumed to be in UTC. The connected
attribute allows
control of connected client during password changes. VNC accepts
keep
value only since 0.9.3.
@@ -6216,7 +6216,7 @@ qemu-kvm -net nic,model=? /dev/null
passwd
attribute is set to an empty string, then
SPICE access is disabled. The keymap
attribute
specifies the keymap to use. It is possible to set a limit on
- the validity of the password by giving an timestamp
+ the validity of the password by giving a timestamp
passwdValidTo='2010-04-09T15:51:00'
assumed to be
in UTC.
diff --git a/docs/formatdomaincaps.html.in b/docs/formatdomaincaps.html.in
index 6bfcaf61ca..027e115645 100644
--- a/docs/formatdomaincaps.html.in
+++ b/docs/formatdomaincaps.html.in
@@ -81,7 +81,7 @@
Before any devices capability occurs, there might be a info on domain +
Before any devices capability occurs, there might be info on domain wide capabilities, e.g. virtual CPUs:
diff --git a/docs/internals/rpc.html.in b/docs/internals/rpc.html.in index fca9cb784e..048192f818 100644 --- a/docs/internals/rpc.html.in +++ b/docs/internals/rpc.html.in @@ -133,7 +133,7 @@
serial
/etc/libvirt/qemu-sanlock.conf
There is one mandatory parameter that needs to be set,
- the host_id
. This is a integer between
+ the host_id
. This is an integer between
1 and 2000, which must be set to a unique
value on each host running virtual machines.
diff --git a/docs/news.xml b/docs/news.xml
index d67d5a73d0..80181415c6 100644
--- a/docs/news.xml
+++ b/docs/news.xml
@@ -1206,7 +1206,7 @@
vgaconf
attribute was added to video
's
driver
element. Possible values are: on
,
- off
, and io
. It controlls the way how
+ off
, and io
. It controls the way how
bhyve exposes video devices to its guests; various guest OSes might
require different settings to boot properly.