diff --git a/docs/formatcaps.html.in b/docs/formatcaps.html.in index dcbf35a9dcad230d1ae3aa5dfe671f02ac22ca92..a4297cefa1ce1e32e53dc4c7f7e7a5efda14768e 100644 --- a/docs/formatcaps.html.in +++ b/docs/formatcaps.html.in @@ -55,6 +55,7 @@ BIOS you will see
</arch> <features> <cpuselection/> + <deviceboot/> </features> </guest> ... diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index dad268d0b3cb7720bccab3fa3eec56b956c4f7de..3afea8deaee85ece90b59ec3ebf96f2a3abd4392 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -103,8 +103,11 @@dev
attribute takes one of the values "fd", "hd",
"cdrom" or "network" and is used to specify the next boot device
to consider. The boot
element can be repeated multiple
- times to setup a priority list of boot devices to try in turn.
- Since 0.1.3
+ times to setup a priority list of boot devices to try in turn. The
+ boot
element cannot be used if per-device boot elements
+ are used (see disks and
+ network interfaces sections below.
+ Since 0.1.3, per-device boot since 0.8.8
bootmenu
boot
order
+ attribute determines the order in which devices will be tried during
+ boot sequence. The per-device boot
elements cannot be
+ used together with general boot elements in
+ BIOS bootloader section.
+ Since 0.8.8
+ encryption
+ ... + <devices> + <interface type='network'> + <source network='default'/> + <target dev='vnet1'/> + <boot order='1'/> + </interface> + </devices> + ...+ +
+ For hypervisors which support this, you can set exact NIC which should
+ be used for network boot. The order
attribute determines
+ the order in which devices will be tried during boot sequence. The
+ per-device boot
elements cannot be used together with
+ general boot elements in
+ BIOS bootloader section.
+ Since 0.8.8
+
diff --git a/docs/schemas/domain.rng b/docs/schemas/domain.rng
index a79ca6a0153b87263325b00a07e79f0be603a16a..9b977b5d8cb7a040a5ba8835f72d71f91539b444 100644
--- a/docs/schemas/domain.rng
+++ b/docs/schemas/domain.rng
@@ -121,9 +121,9 @@