From: Glauber Costa <glommer@redhat.com>
To: kvm@vger.kernel.org
Cc: aliguori@us.ibm.com, mtosatti@redhat.com, qemu-devel@nongnu.org,
avi@redhat.com
Subject: [Qemu-devel] [PATCH 1/2] document bootindex option
Date: Tue, 12 Apr 2011 14:23:56 -0300 [thread overview]
Message-ID: <1302629037-16084-2-git-send-email-glommer@redhat.com> (raw)
In-Reply-To: <1302629037-16084-1-git-send-email-glommer@redhat.com>
bootindex option was added to -option-rom switch, but never documented.
Signed-off-by: Glauber Costa <glommer@redhat.com>
---
qemu-options.hx | 11 +++++++++--
1 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index 18f54d2..96927cc 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -2079,13 +2079,20 @@ to cope with initialization race conditions.
ETEXI
DEF("option-rom", HAS_ARG, QEMU_OPTION_option_rom, \
- "-option-rom rom load a file, rom, into the option ROM space\n",
+ "-option-rom rom[,bootindex=idx] load a file, rom, into the option ROM space\n",
QEMU_ARCH_ALL)
STEXI
-@item -option-rom @var{file}
+@item -option-rom @var{file}[,bootindex=@var{bootindex}]
@findex -option-rom
Load the contents of @var{file} as an option ROM.
This option is useful to load things like EtherBoot.
+
+@table @option
+@item bootindex=@var{bootindex}
+Defines which boot index the option rom will be given in boot entry vectors,
+allowing fine-grained selection of devices boot order.
+@end table
+
ETEXI
DEF("clock", HAS_ARG, QEMU_OPTION_clock, \
--
1.7.4
next prev parent reply other threads:[~2011-04-12 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 17:23 [Qemu-devel] [PATCH 0/2] allow fw_dir to be specified in the option-rom switch Glauber Costa
2011-04-12 17:23 ` Glauber Costa [this message]
2011-04-12 17:23 ` [Qemu-devel] [PATCH 2/2] add fw_dir option to " Glauber Costa
2011-04-12 17:40 ` Anthony Liguori
2011-04-12 18:13 ` Glauber Costa
2011-04-12 18:31 ` Anthony Liguori
2011-04-12 18:47 ` Glauber Costa
2011-04-12 19:19 ` Anthony Liguori
2011-04-13 0:20 ` Glauber Costa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1302629037-16084-2-git-send-email-glommer@redhat.com \
--to=glommer@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).