* [Qemu-devel] [PATCH] docs: Add a note about mixing bootindex with "-boot order"
@ 2017-02-28 17:40 Thomas Huth
2017-02-28 18:41 ` Eric Blake
2017-02-28 20:55 ` Laszlo Ersek
0 siblings, 2 replies; 3+ messages in thread
From: Thomas Huth @ 2017-02-28 17:40 UTC (permalink / raw)
To: qemu-devel
Cc: Paolo Bonzini, qemu-trivial, Alexey Kardashevskiy, Laszlo Ersek,
Eric Blake
Occasionally the users try to mix the bootindex properties with the
"-boot order" parameter - and this likely does not give the expected
results. So let's add a proper statement that these two concepts
should not be used together.
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
docs/bootindex.txt | 9 +++++++++
qemu-options.hx | 5 ++++-
2 files changed, 13 insertions(+), 1 deletion(-)
diff --git a/docs/bootindex.txt b/docs/bootindex.txt
index f84fac7..9e0ac07 100644
--- a/docs/bootindex.txt
+++ b/docs/bootindex.txt
@@ -41,3 +41,12 @@ has three bootable devices target1, target3, target5 connected to it,
the option ROM will have a boot method for each of them, but it is not
possible to map from boot method back to a specific target. This is a
shortcoming of the PC BIOS boot specification.
+
+== Mixing bootindex and boot order parameters ==
+
+Note that it does not make sense to use the bootindex property together
+with the "-boot order=..." (or "-boot once=...") parameter. The guest
+firmware implementations normally either support the one or the other,
+but not both parameters at the same time. Mixing them will result in
+undefined behavior, and thus the guest firmware will likely not boot
+from the expected devices.
diff --git a/qemu-options.hx b/qemu-options.hx
index bf458f8..aa11420 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -234,7 +234,10 @@ drive letters depend on the target architecture. The x86 PC uses: a, b
(floppy 1 and 2), c (first hard disk), d (first CD-ROM), n-p (Etherboot
from network adapter 1-4), hard disk boot is the default. To apply a
particular boot order only on the first startup, specify it via
-@option{once}.
+@option{once}. Note that the @option{order} or @option{once} parameter
+should not be used together with the @option{bootindex} property of
+devices, since the firmware implementations normally do not support both
+at the same time.
Interactive boot menus/prompts can be enabled via @option{menu=on} as far
as firmware/BIOS supports them. The default is non-interactive boot.
--
1.8.3.1
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] [PATCH] docs: Add a note about mixing bootindex with "-boot order"
2017-02-28 17:40 [Qemu-devel] [PATCH] docs: Add a note about mixing bootindex with "-boot order" Thomas Huth
@ 2017-02-28 18:41 ` Eric Blake
2017-02-28 20:55 ` Laszlo Ersek
1 sibling, 0 replies; 3+ messages in thread
From: Eric Blake @ 2017-02-28 18:41 UTC (permalink / raw)
To: Thomas Huth, qemu-devel
Cc: Paolo Bonzini, qemu-trivial, Alexey Kardashevskiy, Laszlo Ersek
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
On 02/28/2017 11:40 AM, Thomas Huth wrote:
> Occasionally the users try to mix the bootindex properties with the
> "-boot order" parameter - and this likely does not give the expected
> results. So let's add a proper statement that these two concepts
> should not be used together.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> docs/bootindex.txt | 9 +++++++++
> qemu-options.hx | 5 ++++-
> 2 files changed, 13 insertions(+), 1 deletion(-)
>
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] [PATCH] docs: Add a note about mixing bootindex with "-boot order"
2017-02-28 17:40 [Qemu-devel] [PATCH] docs: Add a note about mixing bootindex with "-boot order" Thomas Huth
2017-02-28 18:41 ` Eric Blake
@ 2017-02-28 20:55 ` Laszlo Ersek
1 sibling, 0 replies; 3+ messages in thread
From: Laszlo Ersek @ 2017-02-28 20:55 UTC (permalink / raw)
To: Thomas Huth, qemu-devel
Cc: Paolo Bonzini, qemu-trivial, Alexey Kardashevskiy, Eric Blake
On 02/28/17 18:40, Thomas Huth wrote:
> Occasionally the users try to mix the bootindex properties with the
> "-boot order" parameter - and this likely does not give the expected
> results. So let's add a proper statement that these two concepts
> should not be used together.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> docs/bootindex.txt | 9 +++++++++
Wow, a document from 2011!
commit 466b58648a7b2ba7edb280b585e0b0c26e3be31e
Author: Gleb Natapov <gleb@redhat.com>
Date: Sun Jan 30 12:29:19 2011 +0200
Add boot index documentation.
So cool. I didn't know this existed.
> qemu-options.hx | 5 ++++-
> 2 files changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/docs/bootindex.txt b/docs/bootindex.txt
> index f84fac7..9e0ac07 100644
> --- a/docs/bootindex.txt
> +++ b/docs/bootindex.txt
> @@ -41,3 +41,12 @@ has three bootable devices target1, target3, target5 connected to it,
> the option ROM will have a boot method for each of them, but it is not
> possible to map from boot method back to a specific target. This is a
> shortcoming of the PC BIOS boot specification.
> +
> +== Mixing bootindex and boot order parameters ==
> +
> +Note that it does not make sense to use the bootindex property together
> +with the "-boot order=..." (or "-boot once=...") parameter. The guest
> +firmware implementations normally either support the one or the other,
> +but not both parameters at the same time. Mixing them will result in
> +undefined behavior, and thus the guest firmware will likely not boot
> +from the expected devices.
> diff --git a/qemu-options.hx b/qemu-options.hx
> index bf458f8..aa11420 100644
> --- a/qemu-options.hx
> +++ b/qemu-options.hx
> @@ -234,7 +234,10 @@ drive letters depend on the target architecture. The x86 PC uses: a, b
> (floppy 1 and 2), c (first hard disk), d (first CD-ROM), n-p (Etherboot
> from network adapter 1-4), hard disk boot is the default. To apply a
> particular boot order only on the first startup, specify it via
> -@option{once}.
> +@option{once}. Note that the @option{order} or @option{once} parameter
> +should not be used together with the @option{bootindex} property of
> +devices, since the firmware implementations normally do not support both
> +at the same time.
>
> Interactive boot menus/prompts can be enabled via @option{menu=on} as far
> as firmware/BIOS supports them. The default is non-interactive boot.
>
Awesome. Thank you for this.
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-02-28 20:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-02-28 17:40 [Qemu-devel] [PATCH] docs: Add a note about mixing bootindex with "-boot order" Thomas Huth
2017-02-28 18:41 ` Eric Blake
2017-02-28 20:55 ` Laszlo Ersek
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.