On Tue, Apr 29, 2014 at 03:47:26PM +0800, Chen Hanxiao wrote:
commit ddf2dfa1f79af0405df5ca10583764a497c7a0db provide a way to determine which bios files to use.
s/provide/provided/
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 <chenhanx...@cn.fujitsu.com> --- v2: updated description by Jim's comments. docs/formatdomain.html.in | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index b9bbcc9..e4bd87e 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -126,9 +126,9 @@ these. <span class="since">Since 0.0.1</span></dd> <dt><code>loader</code></dt> <dd>The optional <code>loader</code> tag refers to a firmware blob - used to assist the domain creation process. At this time, it is - only needed by Xen fully virtualized - domains. <span class="since">Since 0.1.0</span></dd> + 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. <span class="since">Since 0.9.12</span></dd>
I'd like to keep the "Since 0.1.0" there for the Xen part, so I added it back there and pushed, feel free to object. Martin
<dt><code>boot</code></dt>
<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
--
1.9.0
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
signature.asc
Description: Digital signature
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
