From: Thomas Huth <thuth@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Guenter Roeck <linux@roeck-us.net>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-s390@vger.kernel.org, Vasily Gorbik <gor@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>,
qemu-s390x <qemu-s390x@nongnu.org>
Subject: Re: [Qemu-devel] [qemu-s390x] s390 qemu boot failure in -next
Date: Mon, 25 Jun 2018 10:27:26 +0200 [thread overview]
Message-ID: <7416298e-8f8a-fa1a-759f-da6526eab6ca@redhat.com> (raw)
In-Reply-To: <947bbba3-dcd0-7f5b-1d92-b41be764c2f5@de.ibm.com>
On 25.06.2018 10:02, Christian Borntraeger wrote:
>
>
> On 06/25/2018 09:27 AM, Christian Borntraeger wrote:
>> Also adding QEMU.
>>
>> On 06/25/2018 09:10 AM, Christian Borntraeger wrote:
>>>
>>>
>>> On 06/22/2018 09:47 PM, Guenter Roeck wrote:
>>>> Hi,
>>>>
>>>> starting with commit 's390/boot: make head.S and als.c be part of the
>>>> decompressor only' in -next, s390 immages no longer boot in qemu.
>>>> As far as I can see, the reason is that the command line is no longer
>>>> passed from qemu to the kernel, which results in a panic because the
>>>> root file system can not be mounted.
>>>>
>>>> Was this change made on purpose ? If so, is there a way to get qemu
>>>> back to working ?
>>>
>>> Certainly not on purpose.
>>>
>>> Vasily, I can reproduce this with KVM and an external kernel boot of the vmlinux file (the elf file)
>>>
>>> e.g.
>>>
>>> qemu-system-s390 -enable-kvm -nographic -kernel vmlinux -append "this string no longer is command line"
>>>
>>> The compressed image (bzImage) seems to work fine though.
>>>
>>> This seems to be an unfortunate side effect of QEMUs ways to "guess" its Linux (checking for start
>>> address 0x10000, which is no longer true for the vmlinux file). With the pure vmlinux elf file
>>> the load address is 0x100000 as there is no unpacker.
>>>
>>> Guenter, can you check if arch/s390/boot/bzImage works for you as a workaround?
>>
>> Something like this in QEMU
>>
>> diff --git a/hw/s390x/ipl.c b/hw/s390x/ipl.c
>> index f278036fa7..14153ce880 100644
>> --- a/hw/s390x/ipl.c
>> +++ b/hw/s390x/ipl.c
>> @@ -187,11 +187,13 @@ static void s390_ipl_realize(DeviceState *dev, Error **errp)
>> */
>> if (pentry == KERN_IMAGE_START || pentry == 0x800) {
>> ipl->start_addr = KERN_IMAGE_START;
>> - /* Overwrite parameters in the kernel image, which are "rom" */
>> - strcpy(rom_ptr(KERN_PARM_AREA), ipl->cmdline);
>> } else {
>> ipl->start_addr = pentry;
>> }
>> + if (ipl->cmdline) {
>> + /* If there is a command line, put it in the right place */
>> + strcpy(rom_ptr(KERN_PARM_AREA), ipl->cmdline);
You definitely need to check for rom_ptr() != NULL first before calling
strcpy. Otherwise QEMU segfaults in case the user tried to load a kernel
to a different location.
See also:
https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg04227.html
Thomas
next prev parent reply other threads:[~2018-06-25 8:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180622194736.GA5794@roeck-us.net>
[not found] ` <126ac556-0602-b927-58f5-cb5f65a5e0ec@de.ibm.com>
2018-06-25 7:27 ` [Qemu-devel] s390 qemu boot failure in -next Christian Borntraeger
2018-06-25 8:02 ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2018-06-25 8:08 ` Cornelia Huck
2018-06-25 8:27 ` Thomas Huth [this message]
2018-06-25 8:05 ` [Qemu-devel] " Cornelia Huck
2018-06-25 8:29 ` Christian Borntraeger
2018-06-26 8:29 ` Cornelia Huck
2018-06-26 8:54 ` Christian Borntraeger
2018-06-25 8:36 ` Vasily Gorbik
2018-06-25 8:49 ` Cornelia Huck
2018-06-25 12:26 ` Christian Borntraeger
2018-06-25 13:35 ` Guenter Roeck
2018-06-25 15:09 ` Vasily Gorbik
2018-06-25 15:09 ` [Qemu-devel] [PATCH] s390/boot: block uncompressed vmlinux booting attempts Vasily Gorbik
2018-06-25 19:40 ` Guenter Roeck
2018-06-26 7:30 ` Christian Borntraeger
2018-06-26 8:24 ` Cornelia Huck
2018-06-26 5:32 ` [Qemu-devel] s390 qemu boot failure in -next Georgi Guninski
2018-06-26 5:40 ` Thomas Huth
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=7416298e-8f8a-fa1a-759f-da6526eab6ca@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=schwidefsky@de.ibm.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).