[libvirt] [PATCH] docs: update docs for setting the QEMU BIOS file path
commit ddf2dfa1f79af0405df5ca10583764a497c7a0db provides a way to determine which bios files to use. So 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> --- docs/formatdomain.html.in | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index e851f85..93f14fa 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -128,7 +128,13 @@ <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> + domains. <span class="since">Since 0.1.0</span> + <p> + It could also be used to set the QEMU BIOS file path. + Then guest will be started with that BIOS file. + <span class="since">Since 0.9.12</span> + </p> + </dd> <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
<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
Is the sentence "only needed by Xen fully virtualized" valid even now? For example, the support for UEFI firmware has also been introduced, which can be easily used by extracting bios.bin from http://download.opensuse.org/repositories/home:/jejb1:/UEFI/openSUSE_12.2/x8... and passing its path under the <loader> option. -- Nehal J Wani
-----Original Message----- From: Nehal J Wani [mailto:nehaljw.kkd1@gmail.com] Sent: Monday, April 28, 2014 1:07 PM To: Chen, Hanxiao/陈 晗霄 Cc: libvir-list Subject: Re: [libvirt] [PATCH] docs: update docs for setting the QEMU BIOS file path
<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
Is the sentence "only needed by Xen fully virtualized" valid even now?
I'm not familiar with XEN... Anyone can help? Thanks, - Chen
For example, the support for UEFI firmware has also been introduced, which can be easily used by extracting bios.bin from http://download.opensuse.org/repositories/home:/jejb1:/UEFI/openSUSE_12.2 /x86_64/OVMF-0.1+r14742-1.1.x86_64.rpm and passing its path under the <loader> option.
-- Nehal J Wani
chenhanxiao@cn.fujitsu.com wrote:
-----Original Message----- From: Nehal J Wani [mailto:nehaljw.kkd1@gmail.com] Sent: Monday, April 28, 2014 1:07 PM To: Chen, Hanxiao/陈 晗霄 Cc: libvir-list Subject: Re: [libvirt] [PATCH] docs: update docs for setting the QEMU BIOS file path
<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
Is the sentence "only needed by Xen fully virtualized" valid even now?
I'm not familiar with XEN...
Anyone can help?
There is certainly a lot of Xen fully virtualized config with <loader>/usr/lib/xen/boot/hvmloader</loader>. But it sounds like your change makes the "only needed by" part invalid. I.e. <loader> is used by Xen fully virtualized domains as well as setting the QEMU BIOS file path for QEMU/KVM domains. Regards, Jim
-----Original Message----- From: Jim Fehlig [mailto:jfehlig@suse.com] Sent: Tuesday, April 29, 2014 12:25 PM To: Chen, Hanxiao/陈 晗霄 Cc: Nehal J Wani; libvir-list Subject: Re: [libvirt] [PATCH] docs: update docs for setting the QEMU BIOS file path
chenhanxiao@cn.fujitsu.com wrote:
-----Original Message----- From: Nehal J Wani [mailto:nehaljw.kkd1@gmail.com] Sent: Monday, April 28, 2014 1:07 PM To: Chen, Hanxiao/陈 晗霄 Cc: libvir-list Subject: Re: [libvirt] [PATCH] docs: update docs for setting the QEMU BIOS file path
<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
Is the sentence "only needed by Xen fully virtualized" valid even now?
I'm not familiar with XEN...
Anyone can help?
There is certainly a lot of Xen fully virtualized config with <loader>/usr/lib/xen/boot/hvmloader</loader>. But it sounds like your change makes the "only needed by" part invalid. I.e. <loader> is used by Xen fully virtualized domains as well as setting the QEMU BIOS file path for QEMU/KVM domains.
Thanks for your help :) - Chen
Regards, Jim
participants (4)
-
Chen Hanxiao -
chenhanxiao＠cn.fujitsu.com
-
Jim Fehlig -
Nehal J Wani