case the boot fails (according to BIOS). The value is in milliseconds with
maximum of ``65535`` and special value ``-1`` disables the reboot.
-:anchor:`<a id="elementsOSBootloader"/>`
-
Host bootloader
~~~~~~~~~~~~~~~
The optional ``bootloader_args`` element allows command line arguments to be
passed to the bootloader. :since:`Since 0.2.3`
-:anchor:`<a id="elementsOSKernel"/>`
-
Direct kernel boot
~~~~~~~~~~~~~~~~~~
``write_iops_sec``
Write I/O operations per second limit. :since:`Since 1.2.2`
-:anchor:`<a id="resPartition"/>`
-
Resource partitioning
---------------------
``ignore``
Keep the domain running as if nothing happened.
-:anchor:`<a id="elementsPowerManagement"/>`
-
Power Management
----------------
tb-cache The size of translation block cache size an integer (a multiple of MiB) :since:`8.0.0`
=========== ============================================== =================================================== ==============
-:anchor:`<a id="elementsTime"/>`
-
Time keeping
------------
The ``present`` attribute can be "yes" or "no" to specify whether a
particular timer is available to the guest.
-:anchor:`<a id="elementsPerf"/>`
-
Performance monitoring events
-----------------------------
disk's hardware sector size which can be relevant for the alignment of
disk data.
-:anchor:`<a id="elementsFilesystems"/>`
-
Filesystems
~~~~~~~~~~~
</devices>
...
-:anchor:`<a id="elementsLease"/>`
-
Device leases
~~~~~~~~~~~~~
Host device assignment
~~~~~~~~~~~~~~~~~~~~~~
-:anchor:`<a id="elementsHostDevSubsys"/>`
-
USB / PCI / SCSI devices
^^^^^^^^^^^^^^^^^^^^^^^^
Note: Although ``shareable`` was introduced :since:`in 1.0.6` , it did not
work as as expected until :since:`1.2.2` .
-:anchor:`<a id="elementsHostDevCaps"/>`
-
Block / character devices
^^^^^^^^^^^^^^^^^^^^^^^^^
used. For network interfaces, the name of the interface is provided in the
"interface" element.
-:anchor:`<a id="elementsRedir"/>`
-
Redirected devices
~~~~~~~~~~~~~~~~~~
``-1`` can be used to allow any value for them. ``allow`` attribute is
mandatory, 'yes' means allow, 'no' for deny.
-:anchor:`<a id="elementsSmartcard"/>`
-
Smartcard devices
~~~~~~~~~~~~~~~~~
in PCI addresses assigned to the device. This value is required to be unique
across all devices and be between 1 and (16*1024-1).
-:anchor:`<a id="elementsNICSVirtual"/>`
-
Virtual network
^^^^^^^^^^^^^^^
</devices>
...
-:anchor:`<a id="elementsNICSBridge"/>`
-
Bridge to LAN
^^^^^^^^^^^^^
</devices>
...
-:anchor:`<a id="elementsNICSSlirp"/>`
-
Userspace SLIRP stack
^^^^^^^^^^^^^^^^^^^^^
</devices>
...
-:anchor:`<a id="elementsNICSEthernet"/>`
-
Generic ethernet connection
^^^^^^^^^^^^^^^^^^^^^^^^^^^
</devices>
...
-:anchor:`<a id="elementsNICSHostdev"/>`
-
PCI Passthrough
^^^^^^^^^^^^^^^
</devices>
...
-:anchor:`<a id="elementsNICSVDPA"/>`
-
vDPA devices
^^^^^^^^^^^^
</devices>
...
-:anchor:`<a id="elementsTeaming"/>`
-
Teaming a virtio/hostdev NIC pair
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
that the virtio device remains connected to the same network segment before and
after migration.
-:anchor:`<a id="elementsNICSMulticast"/>`
-
Multicast tunnel
^^^^^^^^^^^^^^^^
</devices>
...
-:anchor:`<a id="elementsNICSTCP"/>`
-
TCP tunnel
^^^^^^^^^^
</devices>
...
-:anchor:`<a id="elementsNICSUDP"/>`
-
UDP unicast tunnel
^^^^^^^^^^^^^^^^^^
</devices>
...
-:anchor:`<a id="elementsNICSModel"/>`
-
Setting the NIC model
^^^^^^^^^^^^^^^^^^^^^
See `Virtio transitional devices <#elementsVirtioTransitional>`__ for more
details.
-:anchor:`<a id="elementsDriverBackendOptions"/>`
-
Setting NIC driver-specific options
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
options. By default, the supported offloads are enabled by QEMU.
:since:`Since 1.2.9 (QEMU only)`
-:anchor:`<a id="elementsBackendOptions"/>`
-
Setting network backend-specific options
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
</devices>
...
-:anchor:`<a id="elementsNICSBoot"/>`
-
Specifying boot order
^^^^^^^^^^^^^^^^^^^^^
together with general boot elements in `BIOS bootloader <#elementsOSBIOS>`__
section. :since:`Since 0.8.8`
-:anchor:`<a id="elementsNICSROM"/>`
-
Interface ROM BIOS configuration
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
BIOS. This can be useful to provide an alternative boot ROM for a network
device. :since:`Since 0.9.10 (QEMU and KVM only)` .
-:anchor:`<a id="elementDomain"/>`
-
Setting up a network backend in a driver domain
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
``isolated='yes'``, even the isolated guests will be able to communicate with
it.)
-:anchor:`<a id="elementLink"/>`
-
Modifying virtual link state
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
which accepts a non-negative integer that specifies the maximum number of
packets that will be received before an interrupt. :since:`Since 3.3.0`
-:anchor:`<a id="ipconfig"/>`
-
IP configuration
^^^^^^^^^^^^^^^^
``no``) and ``timeout`` which specifies the amount of seconds after which
hypervisor tries to reconnect.
-:anchor:`<a id="elementNwfilter"/>`
-
Traffic filtering with NWFilter
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
`nwfilter <formatnwfilter.html#usage-of-variables-in-filters>`__ docs for info
on parameters.
-:anchor:`<a id="elementsInput"/>`
-
Input devices
~~~~~~~~~~~~~
`Virtio-specific options <#elementsVirtio>`__ can also be set. ( :since:`Since
3.5.0` )
-:anchor:`<a id="elementsHub"/>`
-
Hub devices
~~~~~~~~~~~
attribute is valid only for ``connect`` mode. :since:`Since 3.7.0 (QEMU driver
only)` .
-:anchor:`<a id="elementsCharGuestInterface"/>`
-
Guest interface
^^^^^^^^^^^^^^^
A character device presents itself to the guest as one of the following types.
-:anchor:`<a id="elementCharParallel"/>`
-
Parallel port
'''''''''''''
For the relationship between serial ports and consoles, `see
below <#elementCharSerialAndConsole>`__.
-:anchor:`<a id="elementCharConsole"/>`
-
Console
'''''''
will be treated the same and will result in a single emulated serial console
being available to the guest.
-:anchor:`<a id="elementCharChannel"/>`
-
Channel
'''''''
A character device presents itself to the host as one of the following types.
-:anchor:`<a id="elementsCharSTDIO"/>`
-
Domain logfile
''''''''''''''
</devices>
...
-:anchor:`<a id="elementsCharFle"/>`
-
Device logfile
''''''''''''''
</devices>
...
-:anchor:`<a id="elementsCharVC"/>`
-
Virtual console
'''''''''''''''
</devices>
...
-:anchor:`<a id="elementsCharNull"/>`
-
Null device
'''''''''''
</devices>
...
-:anchor:`<a id="elementsCharPTY"/>`
-
Pseudo TTY
''''''''''
</devices>
...
-:anchor:`<a id="elementsCharPipe"/>`
-
Named pipe
''''''''''
</devices>
...
-:anchor:`<a id="elementsCharTCP"/>`
-
TCP client/server
'''''''''''''''''
</devices>
...
-:anchor:`<a id="elementsCharUDP"/>`
-
UDP network console
'''''''''''''''''''
</devices>
...
-:anchor:`<a id="elementsCharUNIX"/>`
-
UNIX domain socket client/server
''''''''''''''''''''''''''''''''
</devices>
...
-:anchor:`<a id="elementsCharSpiceport"/>`
-
Spice channel
'''''''''''''
</devices>
...
-:anchor:`<a id="elementsNmdm"/>`
-
Nmdm device
'''''''''''
Slave device of the pair, that is passed to the clients for connection to the
guest console. Device is specified by a fully qualified path.
-:anchor:`<a id="elementsSound"/>`
-
Sound devices
~~~~~~~~~~~~~
:since:`Since 7.2.0, qemu`
-:anchor:`<a id="elementsWatchdog"/>`
-
Watchdog device
~~~~~~~~~~~~~~~
Note 2: the directory to save dump files can be configured by
``auto_dump_path`` in file /etc/libvirt/qemu.conf.
-:anchor:`<a id="elementsMemBalloon"/>`
-
Memory balloon device
~~~~~~~~~~~~~~~~~~~~~
For model ``virtio`` memballoon, `Virtio-specific
options <#elementsVirtio>`__ can also be set. ( :since:`Since 3.5.0` )
-:anchor:`<a id="elementsRng"/>`
-
Random number generator device
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
encrypted. The ``secret`` must reference a secret object that holds the
passphrase from which the encryption key will be derived.
-:anchor:`<a id="elementsNVRAM"/>`
-
NVRAM device
~~~~~~~~~~~~
``reg``
Device address
-:anchor:`<a id="elementsPanic"/>`
-
panic device
~~~~~~~~~~~~
specify an address, and doing so is forbidden altogether for s390, pseries
and hyperv models.
-:anchor:`<a id="elementsShmem"/>`
-
Shared memory device
~~~~~~~~~~~~~~~~~~~~
session blob defined in the SEV API spec. See SEV spec LAUNCH_START section
for the session blob format.
-:anchor:`<a id="examples"/>`
-
Example configs
===============
projects / thirdparty / libvirt.git / commitdiff
