From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
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: Fri, 2 Mar 2018 10:08:23 +0100 [thread overview]
Message-ID: <20180302100823.15ece9ee.cohuck@redhat.com> (raw)
In-Reply-To: <1519725913-24852-1-git-send-email-thuth@redhat.com>
On Tue, 27 Feb 2018 11:05:13 +0100
Thomas Huth <thuth@redhat.com> 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(-)
Thanks, applied.
prev parent reply other threads:[~2018-03-02 9:08 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
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 [this message]
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=20180302100823.15ece9ee.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
/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).