NuKVM/libvirt
3
0
Fork 0
mirror of https://github.com/libvirt/libvirt.git synced 2025-02-25 18:55:26 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs: update docs for setting the QEMU BIOS path

Browse Source 
commit ddf2dfa1f7
provided a way to determine which bios files to use.
But we need to update related docs.

disccussed at:
http://www.redhat.com/archives/libvir-list/2012-June/msg01286.html

Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
This commit is contained in:
Chen Hanxiao 2014-04-29 15:47:26 +08:00 committed by Martin Kletzander
parent 4cd508ba4f
commit 6c19f0de49
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/formatdomain.html.in
View File

@ -126,9 +126,10 @@
these. <span class="since">Since 0.0.1</span></dd> these. <span class="since">Since 0.0.1</span></dd>
<dt><code>loader</code></dt> <dt><code>loader</code></dt>
<dd>The optional <code>loader</code> tag refers to a firmware blob <dd>The optional <code>loader</code> tag refers to a firmware blob
used to assist the domain creation process. At this time, it is used to assist the domain creation process. It is used by Xen
only needed by Xen fully virtualized fully virtualized domains as well as setting the QEMU BIOS file
domains. <span class="since">Since 0.1.0</span></dd> path for QEMU/KVM domains. <span class="since">Xen since 0.1.0,
QEMU/KVM since 0.9.12</span></dd>
<dt><code>boot</code></dt> <dt><code>boot</code></dt>
<dd>The <code>dev</code> attribute takes one of the values "fd", "hd", <dd>The <code>dev</code> attribute takes one of the values "fd", "hd",
"cdrom" or "network" and is used to specify the next boot device "cdrom" or "network" and is used to specify the next boot device