On 8/10/20 12:29 PM, Cornelia Huck wrote: > On Mon, 10 Aug 2020 12:20:53 +0200 > Philippe Mathieu-Daudé <phi...@redhat.com> wrote: > >> On 8/10/20 12:18 PM, Cornelia Huck wrote: >>> On Thu, 6 Aug 2020 17:05:07 +0200 >>> Thomas Huth <th...@redhat.com> wrote: >>> >>>> Booting on s390x is a little bit different compared to other architectures. >>>> Let's add some information for people who are not yet used to this. >>>> >>>> Signed-off-by: Thomas Huth <th...@redhat.com> >>>> --- >>>> docs/system/s390x/bootdevices.rst | 82 +++++++++++++++++++++++++++++++ >>>> docs/system/target-s390x.rst | 1 + >>>> 2 files changed, 83 insertions(+) >>>> create mode 100644 docs/system/s390x/bootdevices.rst >>>> >>>> diff --git a/docs/system/s390x/bootdevices.rst >>>> b/docs/system/s390x/bootdevices.rst >>>> new file mode 100644 >>>> index 0000000000..68f0ffd450 >>>> --- /dev/null >>>> +++ b/docs/system/s390x/bootdevices.rst >>>> @@ -0,0 +1,82 @@ >>>> +Boot devices on s390x >>>> +===================== >>>> + >>>> +Booting with bootindex parameter >>>> +-------------------------------- >>>> + >>>> +For classical mainframe guests (i.e. LPAR or z/VM installations), you >>>> always >>>> +have to exactly specify the disk where you want to boot from (or "IPL" >>>> from, >>> >>> s/exactly/explictly/ ? >> >> Or "to explicit the disk ..."? > > Hm, not sure what that means?
Sorry I thought it was a verb, but the verb is explicitize. "to explicitly specify" sounds good (typo fixed).
