From nobody Mon Feb 9 06:49:18 2026 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 1489508524839162.40221036641753; Tue, 14 Mar 2017 09:22:04 -0700 (PDT) Received: from localhost ([::1]:60570 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cnpCx-0005We-GK for importer@patchew.org; Tue, 14 Mar 2017 12:21:59 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36561) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cnp9Z-0003OJ-Ar for qemu-devel@nongnu.org; Tue, 14 Mar 2017 12:18:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cnp9X-0006XE-Tc for qemu-devel@nongnu.org; Tue, 14 Mar 2017 12:18:29 -0400 Received: from mail-wm0-x242.google.com ([2a00:1450:400c:c09::242]:36125) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cnp9X-0006Wb-Mn for qemu-devel@nongnu.org; Tue, 14 Mar 2017 12:18:27 -0400 Received: by mail-wm0-x242.google.com with SMTP id v190so582762wme.3 for ; Tue, 14 Mar 2017 09:18:27 -0700 (PDT) Received: from 640k.lan (94-39-132-181.adsl-ull.clienti.tiscali.it. [94.39.132.181]) by smtp.gmail.com with ESMTPSA id k195sm408197wmd.7.2017.03.14.09.18.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Mar 2017 09:18:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:subject:date:message-id:in-reply-to:references; bh=r/PEAKOC44AoQ0DY0vimW/x2F3mtfUk84+JzdDf8JkM=; b=G6mHrxzsQ9S/8iZXE41hn1OsGMurlVystsFJHiRWoRzXmrR6bRFCQdOgQ1vQ9PbqtS VX8hTbvNCT9MUCOwuYfyEz2XtzkX3hRzQ87CA2sT38VweQhqImxdfHQhyhqusDNdU80l rwiv/edSsBl07LsH5BgRLFqANAfrO0EpVmXooeFmiiBy9Gsxfk2sAos/23heC905gSXT 3zKb0ZXixxRnEpZ7Yfjs6W9lesrvPmMjtdk1gp4JyX0UbQy77N2sWla8uBR85+0WldzR ZrS3P5U/n9FPBxjnqa7R8OFiuz/Ypg6/71dfKAYU36p/OFbbT+d5Ih2vMmfYgbtE9iXz fjuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:date:message-id :in-reply-to:references; bh=r/PEAKOC44AoQ0DY0vimW/x2F3mtfUk84+JzdDf8JkM=; b=YHJMSu/iXsuTpg0qCvrZSts1xfi+52RVoxwM5N5I2aBuuWzn0sFxQh5QdPPYTY8zsH rZQI2xRNS54AxvQUFIC2Zrcg4m0EhyIoCF6wwr0TI9Wni4iyPI+xWesOQ7QegzOQimkt EYqRF3Up7E3M1BdkTlvTZFopb3I3DW+LiQqL6nPrfOxY6MuAmRQavXsmK4MdbLjz1ngI LYB1+94PbNojk/nTs+5eC9G6G1bKx85LoPmUmH+ZZfsT99q9jhpoffi+E9FKQ7YSrnJ3 HdLLgN2n5qxzIj/Op6GFQDs6+kKNOh6ohu8BAbxoOWEoT/Ztyb2Py9E6ZNm/GMNzYll9 uIyg== X-Gm-Message-State: AFeK/H0ROQZTzBrkTpFI18fnk0qRJXJJF2nwkavVcrqbPsi51K/oShNcbhzTPiQh82L24Q== X-Received: by 10.28.187.213 with SMTP id l204mr14912025wmf.104.1489508306646; Tue, 14 Mar 2017 09:18:26 -0700 (PDT) From: Paolo Bonzini To: qemu-devel@nongnu.org Date: Tue, 14 Mar 2017 17:18:04 +0100 Message-Id: <1489508300-48184-3-git-send-email-pbonzini@redhat.com> X-Mailer: git-send-email 1.8.3.1 In-Reply-To: <1489508300-48184-1-git-send-email-pbonzini@redhat.com> References: <1489508300-48184-1-git-send-email-pbonzini@redhat.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:400c:c09::242 Subject: [Qemu-devel] [PULL 02/18] 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: Thomas Huth 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" From: Thomas Huth 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 Message-Id: <1488303601-23741-1-git-send-email-thuth@redhat.com> Reviewed-by: Eric Blake Reviewed-by: Laszlo Ersek Signed-off-by: Paolo Bonzini --- 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..b9a8ba1 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 8dd8ee3..99af8ed 100644 --- a/qemu-options.hx +++ b/qemu-options.hx @@ -252,7 +252,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