diff options
| author | Jared Rossi <jrossi@linux.ibm.com> | 2024-10-19 21:29:52 -0400 |
|---|---|---|
| committer | Thomas Huth <thuth@redhat.com> | 2024-10-23 06:53:44 +0200 |
| commit | 0bd107138ff0b171e3cd314dbc200950bcab2b05 (patch) | |
| tree | b603d660921e46a16c2eb679d7135a0d0ca30ca0 /docs/system/s390x/bootdevices.rst | |
| parent | f697bed22f58eff9b2893ac2fe3d511847398400 (diff) | |
| download | qemu-0bd107138ff0b171e3cd314dbc200950bcab2b05.zip qemu-0bd107138ff0b171e3cd314dbc200950bcab2b05.tar.gz qemu-0bd107138ff0b171e3cd314dbc200950bcab2b05.tar.bz2 | |
docs/system: Update documentation for s390x IPL
Update docs to show that s390x PC BIOS can support more than one boot device.
Signed-off-by: Jared Rossi <jrossi@linux.ibm.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-ID: <20241020012953.1380075-19-jrossi@linux.ibm.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'docs/system/s390x/bootdevices.rst')
| -rw-r--r-- | docs/system/s390x/bootdevices.rst | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/docs/system/s390x/bootdevices.rst b/docs/system/s390x/bootdevices.rst index c97efb8..1a1a764 100644 --- a/docs/system/s390x/bootdevices.rst +++ b/docs/system/s390x/bootdevices.rst @@ -6,9 +6,7 @@ Booting with bootindex parameter For classical mainframe guests (i.e. LPAR or z/VM installations), you always have to explicitly specify the disk where you want to boot from (or "IPL" from, -in s390x-speak -- IPL means "Initial Program Load"). In particular, there can -also be only one boot device according to the architecture specification, thus -specifying multiple boot devices is not possible (yet). +in s390x-speak -- IPL means "Initial Program Load"). So for booting an s390x guest in QEMU, you should always mark the device where you want to boot from with the ``bootindex`` property, for @@ -17,6 +15,11 @@ example:: qemu-system-s390x -drive if=none,id=dr1,file=guest.qcow2 \ -device virtio-blk,drive=dr1,bootindex=1 +Multiple devices may have a bootindex. The lowest bootindex is assigned to the +device to IPL first. If the IPL fails for the first, the device with the second +lowest bootindex will be tried and so on until IPL is successful or there are no +remaining boot devices to try. + For booting from a CD-ROM ISO image (which needs to include El-Torito boot information in order to be bootable), it is recommended to specify a ``scsi-cd`` device, for example like this:: |