From nobody Sun May 5 15:34:47 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zoho.com: domain of gnu.org designates 208.118.235.17 as permitted sender) client-ip=208.118.235.17; envelope-from=qemu-devel-bounces+importer=patchew.org@nongnu.org; helo=lists.gnu.org; Authentication-Results: mx.zoho.com; spf=pass (zoho.com: domain of gnu.org designates 208.118.235.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org; Return-Path: Received: from lists.gnu.org (lists.gnu.org [208.118.235.17]) by mx.zohomail.com with SMTPS id 1488304029727510.92998159217814; Tue, 28 Feb 2017 09:47:09 -0800 (PST) Received: from localhost ([::1]:35955 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cilrg-0001C6-BF for importer@patchew.org; Tue, 28 Feb 2017 12:47:08 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50334) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cilks-0004Fa-78 for qemu-devel@nongnu.org; Tue, 28 Feb 2017 12:40:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cilkr-0005bR-Fl for qemu-devel@nongnu.org; Tue, 28 Feb 2017 12:40:06 -0500 Received: from mx1.redhat.com ([209.132.183.28]:50770) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cilkr-0005b7-AP; Tue, 28 Feb 2017 12:40:05 -0500 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 70BD0369C3; Tue, 28 Feb 2017 17:40:05 +0000 (UTC) Received: from thh440s.redhat.com (ovpn-116-200.ams2.redhat.com [10.36.116.200]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id v1SHe1n4022735; Tue, 28 Feb 2017 12:40:02 -0500 From: Thomas Huth To: qemu-devel@nongnu.org Date: Tue, 28 Feb 2017 18:40:01 +0100 Message-Id: <1488303601-23741-1-git-send-email-thuth@redhat.com> X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Tue, 28 Feb 2017 17:40:05 +0000 (UTC) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.132.183.28 Subject: [Qemu-devel] [PATCH] docs: Add a note about mixing bootindex with "-boot order" X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: qemu-trivial@nongnu.org, Paolo Bonzini , Laszlo Ersek , Alexey Kardashevskiy Errors-To: qemu-devel-bounces+importer=patchew.org@nongnu.org Sender: "Qemu-devel" X-ZohoMail: RSF_0 Z_629925259 SPT_0 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" 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 Reviewed-by: Eric Blake Reviewed-by: Laszlo Ersek --- 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 con= nected 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. + +=3D=3D Mixing bootindex and boot order parameters =3D=3D + +Note that it does not make sense to use the bootindex property together +with the "-boot order=3D..." (or "-boot once=3D...") 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 x= 86 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. =20 Interactive boot menus/prompts can be enabled via @option{menu=3Don} as far as firmware/BIOS supports them. The default is non-interactive boot. --=20 1.8.3.1