diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index 1b496c3459e27e8187d9b9daad72b0c311e8d55c..7ceb1fa63df5c458d0cff40213ed657bd68efc74 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -126,7 +126,8 @@ provides details on allowed values for these. Since 0.0.1
loader
loader
tag refers to a firmware blob
+ loader
tag refers to a firmware blob,
+ which is specified by absolute path,
used to assist the domain creation process. It is used by Xen
fully virtualized domains as well as setting the QEMU BIOS file
path for QEMU/KVM domains. Xen since 0.1.0,
@@ -142,10 +143,10 @@
pflash
.nvram
qemu.conf
. If needed, the template
+ some variables. In the host, this is represented as a file and the
+ absolute path to the file is stored in this element. Moreover, when the
+ domain is started up libvirt copies so called master NVRAM store file
+ defined in qemu.conf
. If needed, the template
attribute can be used to per domain override map of master NVRAM stores
from the config file. Note, that for transient domains if the NVRAM file
has been created by libvirt it is left behind and it is management
@@ -971,7 +972,7 @@
resource partitions, potentially with nesting of said partitions.
The resource
element groups together configuration
related to resource partitioning. It currently supports a child
- element partition
whose content defines the path
+ element partition
whose content defines the absolute path
of the resource partition in which to place the domain. If no
partition is listed, then the domain will be placed in a default
partition. It is the responsibility of the app/admin to ensure
@@ -1954,8 +1955,8 @@
type='block'
since 0.0.3dev
attribute specifies the path to the
- host device to serve as the disk.
+ The dev
attribute specifies the fully-qualified path
+ to the host device to serve as the disk.
type='dir'
since 0.7.5file
attribute is used to point to a binary file
+ file
attribute contains an absolute path to a binary file
to be presented to the guest as the device's ROM BIOS. This
can be useful, for example, to provide a PXE boot ROM for a
virtual function of an sr-iov capable ethernet device (which
@@ -3285,7 +3286,8 @@
Block / character devices from the host can be passed through
to the guest using the hostdev
element. This is
- only possible with container based virtualization.
+ only possible with container based virtualization. Devices are specified
+ by a fully qualified path.
since after 1.0.1 for LXC:
master
slave
This backend type requires exclusive access to a TPM device on
the host.
- An example for such a device is /dev/tpm0. The filename is
- specified as path attribute of the source
element.
+ An example for such a device is /dev/tpm0. The fully qualified file
+ name is specified by path attribute of the source
element.
If no file name is specified then /dev/tpm0 is automatically used.
server
element can be used to configure a server
socket the device is supposed to connect to. The optional
- path
attribute specifies the path to the unix socket and
- defaults to /var/lib/libvirt/shmem/$shmem-$name-sock
.
+ path
attribute specifies the absolute path to the unix socket
+ and defaults to /var/lib/libvirt/shmem/$shmem-$name-sock
.
msi
path
/dev/
may seem
like the logical choice, however, devices nodes there are not
guaranteed stable across reboots, since they are allocated on