From: Thomas Huth <thuth@redhat.com>
To: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
David Hildenbrand <david@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] hw/s390x/ipl: Bail out if the network bootloader can not be found
Date: Tue, 27 Feb 2018 11:27:46 +0100 [thread overview]
Message-ID: <c2e86ee8-e86a-3e02-71c6-66f45ce153d7@redhat.com> (raw)
In-Reply-To: <d638aa33-2102-e6a4-d79a-05591693de07@linux.vnet.ibm.com>
On 27.02.2018 11:16, Viktor Mihajlovski wrote:
> On 27.02.2018 11:05, Thomas Huth wrote:
>> If QEMU fails to load 's390-netboot.img', the guest firmware currently
>> loops forever and just floods the console with "Network boot device
>> detected" messages. The code in ipl.c apparently already tried to stop
>> the VM with vm_stop() in this case, but this is in vain since the run
>> state is later reset due to a call to vm_start() from vl.c again.
>> To avoid the ugly firmware loop, let's simply exit QEMU directly instead
>> since it just does not make sense to continue if the required firmware
>> image can not be loaded. While we're at it, also add the file name of
>> the netboot binary to the error message, so that the user has a better
>> hint about what is missing.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> hw/s390x/ipl.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/hw/s390x/ipl.c b/hw/s390x/ipl.c
>> index 0d06fc1..ff8308e 100644
>> --- a/hw/s390x/ipl.c
>> +++ b/hw/s390x/ipl.c
>> @@ -322,7 +322,8 @@ static int load_netboot_image(Error **errp)
>>
>> netboot_filename = qemu_find_file(QEMU_FILE_TYPE_BIOS, ipl->netboot_fw);
>> if (netboot_filename == NULL) {
>> - error_setg(errp, "Could not find network bootloader");
>> + error_setg(errp, "Could not find network bootloader '%s'",> + ipl->netboot_fw);
>> goto unref_mr;
>> }
>>
>> @@ -416,7 +417,7 @@ void s390_ipl_prepare_cpu(S390CPU *cpu)
>> if (ipl->netboot) {
>> if (load_netboot_image(&err) < 0) {
>> error_report_err(err);
>> - vm_stop(RUN_STATE_INTERNAL_ERROR);
> Should we print something like 'exiting' or 'terminating' here, to make
> clear that the situation is terminal?
No, we normally don't print out "exiting" or "terminating" in such a
case. For example:
hw/alpha/dp264.c: error_report("could not load palcode '%s'", palcode_filename);
hw/alpha/dp264.c: exit(1);
hw/arm/boot.c: error_report("failed to load \"%s\"", image_name);
hw/arm/boot.c: exit(1);
hw/mips/mips_jazz.c: error_report("Could not load MIPS bios '%s'", bios_name);
hw/mips/mips_jazz.c: exit(1);
hw/ppc/spapr.c: error_report("Could not load LPAR rtas '%s'", filename);
hw/ppc/spapr.c: exit(1);
etc.
Thomas
next prev parent reply other threads:[~2018-02-27 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 10:05 [Qemu-devel] [PATCH] hw/s390x/ipl: Bail out if the network bootloader can not be found Thomas Huth
2018-02-27 10:06 ` David Hildenbrand
2018-02-27 10:16 ` Viktor Mihajlovski
2018-02-27 10:27 ` Thomas Huth [this message]
2018-02-27 17:26 ` Farhan Ali
2018-02-27 19:11 ` Thomas Huth
2018-02-27 21:59 ` Farhan Ali
2018-03-02 9:08 ` Cornelia Huck
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=c2e86ee8-e86a-3e02-71c6-66f45ce153d7@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=mihajlov@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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).