From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>,
agraf@suse.de, rth@twiddle.net, david@redhat.com,
thuth@redhat.com, qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] s390: Fix virtio-scsi IPL quirks
Date: Fri, 6 Apr 2018 14:34:17 +0200 [thread overview]
Message-ID: <20180406143417.4f829607.cohuck@redhat.com> (raw)
In-Reply-To: <f766fb2e-f5b9-c117-fc2a-b51c485d6742@de.ibm.com>
On Fri, 6 Apr 2018 14:30:45 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> On 04/05/2018 05:07 PM, Viktor Mihajlovski wrote:
> > IPL from virtio-scsi currently uses a non-standard parameter
> > type definition to pass boot parameters from QEMU to the
> > BIOS.
> >
> > There are two potential issues with this approach:
> > o If the guest operating systems requests a re-ipl of type CCW
> > where the boot device is a virtio-scsi HBA, this goes unnoticed
> > by QEMU. The BIOS will detect that it's IPLing from a SCSI
> > device, but it will boot the first LUN found, which might not
> > be the one used for the initial boot.
> > o The guest operating system can be confused by an unknown
> > IPL parameter block type. If the OS hasn't previously used
> > diag308 to store the IPL info but is changed to do so, a
> > user-observable change in behavior will happen.
> >
> > The following patches address the issues above.
> >
> > Viktor Mihajlovski (3):
> > s390: Refactor IPL parameter block generation
> > s390: Ensure IPL from SCSI works as expected
> > s390: Do not pass inofficial IPL type to the guest
> >
> > hw/s390x/ipl.c | 112 ++++++++++++++++++++++++++++++++-------------
> > pc-bios/s390-ccw/bootmap.c | 7 +++
> > pc-bios/s390-ccw/iplb.h | 15 +++++-
> > 3 files changed, 100 insertions(+), 34 deletions(-)
> >
>
> Test looks good so far.
OK, I'll queue this to s390-fixes, then. I won't send a pull request
before Monday, so there's still a chance to fix this should problems
show up.
Thanks for testing!
prev parent reply other threads:[~2018-04-06 12:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 15:07 [Qemu-devel] [PATCH 0/3] s390: Fix virtio-scsi IPL quirks Viktor Mihajlovski
2018-04-05 15:07 ` [Qemu-devel] [PATCH 1/3] s390: Refactor IPL parameter block generation Viktor Mihajlovski
2018-04-05 16:21 ` Farhan Ali
2018-04-06 7:52 ` Thomas Huth
2018-04-06 9:34 ` Cornelia Huck
2018-04-05 15:07 ` [Qemu-devel] [PATCH 2/3] s390: Ensure IPL from SCSI works as expected Viktor Mihajlovski
2018-04-05 16:54 ` Farhan Ali
2018-04-06 8:37 ` Thomas Huth
2018-04-05 15:07 ` [Qemu-devel] [PATCH 3/3] s390: Do not pass inofficial IPL type to the guest Viktor Mihajlovski
2018-04-05 15:11 ` David Hildenbrand
2018-04-05 15:16 ` Viktor VM Mihajlovski
2018-04-06 9:28 ` Thomas Huth
2018-04-06 9:42 ` Cornelia Huck
2018-04-06 10:43 ` Viktor VM Mihajlovski
2018-04-06 10:56 ` Christian Borntraeger
2018-04-06 9:47 ` [Qemu-devel] [PATCH 0/3] s390: Fix virtio-scsi IPL quirks Cornelia Huck
2018-04-06 12:30 ` Christian Borntraeger
2018-04-06 12:34 ` 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=20180406143417.4f829607.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=mihajlov@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--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).