From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Subject: [PULL 17/21] hw/arm/boot: Report error if there is no fw_cfg device in the machine
Date: Mon, 2 Aug 2021 12:58:08 +0100 [thread overview]
Message-ID: <20210802115812.10731-18-peter.maydell@linaro.org> (raw)
In-Reply-To: <20210802115812.10731-1-peter.maydell@linaro.org>
If the user provides both a BIOS/firmware image and also a guest
kernel filename, arm_setup_firmware_boot() will pass the
kernel image to the firmware via the fw_cfg device. However we
weren't checking whether there really was a fw_cfg device present,
and if there wasn't we would crash.
This crash can be provoked with a command line such as
qemu-system-aarch64 -M raspi3 -kernel /dev/null -bios /dev/null -display none
It is currently only possible on the raspi3 machine, because unless
the machine sets info->firmware_loaded we won't call
arm_setup_firmware_boot(), and the only machines which set that are:
* virt (has a fw-cfg device)
* sbsa-ref (checks itself for kernel_filename && firmware_loaded)
* raspi3 (crashes)
But this is an unfortunate beartrap to leave for future machine
model implementors, so we should handle this situation in boot.c.
Check in arm_setup_firmware_boot() whether the fw-cfg device exists
before trying to load files into it, and if it doesn't exist then
exit with a hopefully helpful error message.
Because we now handle this check in a machine-agnostic way, we
can remove the check from sbsa-ref.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/503
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-id: 20210726163351.32086-1-peter.maydell@linaro.org
---
hw/arm/boot.c | 9 +++++++++
hw/arm/sbsa-ref.c | 7 -------
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/hw/arm/boot.c b/hw/arm/boot.c
index d7b059225e6..57efb61ee41 100644
--- a/hw/arm/boot.c
+++ b/hw/arm/boot.c
@@ -1243,6 +1243,15 @@ static void arm_setup_firmware_boot(ARMCPU *cpu, struct arm_boot_info *info)
bool try_decompressing_kernel;
fw_cfg = fw_cfg_find();
+
+ if (!fw_cfg) {
+ error_report("This machine type does not support loading both "
+ "a guest firmware/BIOS image and a guest kernel at "
+ "the same time. You should change your QEMU command "
+ "line to specify one or the other, but not both.");
+ exit(1);
+ }
+
try_decompressing_kernel = arm_feature(&cpu->env,
ARM_FEATURE_AARCH64);
diff --git a/hw/arm/sbsa-ref.c b/hw/arm/sbsa-ref.c
index 43c19b49234..c1629df6031 100644
--- a/hw/arm/sbsa-ref.c
+++ b/hw/arm/sbsa-ref.c
@@ -691,13 +691,6 @@ static void sbsa_ref_init(MachineState *machine)
firmware_loaded = sbsa_firmware_init(sms, sysmem, secure_sysmem);
- if (machine->kernel_filename && firmware_loaded) {
- error_report("sbsa-ref: No fw_cfg device on this machine, "
- "so -kernel option is not supported when firmware loaded, "
- "please load OS from hard disk instead");
- exit(1);
- }
-
/*
* This machine has EL3 enabled, external firmware should supply PSCI
* implementation, so the QEMU's internal PSCI is disabled.
--
2.20.1
next prev parent reply other threads:[~2021-08-02 12:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 11:57 [PULL 00/21] target-arm queue Peter Maydell
2021-08-02 11:57 ` [PULL 01/21] docs: Add documentation of Arm 'mainstone' board Peter Maydell
2021-08-02 11:57 ` [PULL 02/21] docs: Add documentation of Arm 'kzm' board Peter Maydell
2021-08-02 11:57 ` [PULL 03/21] docs: Add documentation of Arm 'imx25-pdk' board Peter Maydell
2021-08-02 11:57 ` [PULL 04/21] MAINTAINERS: Don't list Andrzej Zaborowski for various components Peter Maydell
2021-08-02 11:57 ` [PULL 05/21] docs: Remove stale TODO comments about license and version Peter Maydell
2021-08-02 11:57 ` [PULL 06/21] docs: Move licence/copyright from HTML output to rST comments Peter Maydell
2021-08-02 11:57 ` [PULL 07/21] docs/devel/build-system.rst: Format literals correctly Peter Maydell
2021-08-02 11:57 ` [PULL 08/21] docs/devel/build-system.rst: Correct typo in example code Peter Maydell
2021-08-02 11:58 ` [PULL 09/21] docs/devel/ebpf_rss.rst: Format literals correctly Peter Maydell
2021-08-02 11:58 ` [PULL 10/21] docs/devel/migration.rst: " Peter Maydell
2021-08-02 11:58 ` [PULL 11/21] docs/devel: " Peter Maydell
2021-08-02 11:58 ` [PULL 12/21] docs/system/s390x/protvirt.rst: " Peter Maydell
2021-08-02 11:58 ` [PULL 13/21] docs/system/arm/cpu-features.rst: " Peter Maydell
2021-08-02 11:58 ` [PULL 14/21] docs: " Peter Maydell
2021-08-02 11:58 ` [PULL 15/21] docs/about/removed-features: Fix markup error Peter Maydell
2021-08-02 11:58 ` [PULL 16/21] docs/tools/virtiofsd.rst: Delete stray backtick Peter Maydell
2021-08-02 11:58 ` Peter Maydell [this message]
2021-08-02 11:58 ` [PULL 18/21] docs: Move bootindex.txt into system section and rstify Peter Maydell
2021-08-02 11:58 ` [PULL 19/21] docs: Move the protocol part of barrier.txt into interop Peter Maydell
2021-08-02 11:58 ` [PULL 20/21] ui/input-barrier: Move TODOs from barrier.txt to a comment Peter Maydell
2021-08-02 11:58 ` [PULL 21/21] docs: Move user-facing barrier docs into system manual Peter Maydell
2021-08-02 13:51 ` [PULL 00/21] target-arm queue Peter Maydell
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=20210802115812.10731-18-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--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).