motorhead/qemu
1
0
Fork 0
mirror of https://github.com/Motorhead1991/qemu.git synced 2025-08-30 21:42:06 -06:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs/system/s390x/bootdevices: Update loadparm documentation

Browse source 
Update documentation to include per-device loadparm support.

Signed-off-by: Jared Rossi <jrossi@linux.ibm.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-ID: <20241115002742.3576842-1-jrossi@linux.ibm.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
This commit is contained in:
Jared Rossi 2024-11-14 19:27:42 -05:00 • committed by Thomas Huth
parent 6dc293540e
commit 0271fdc650
1 changed files with 23 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

24
docs/system/s390x/bootdevices.rst
View file

@ -79,7 +79,29 @@ The second way to use this parameter is to use a number in the range from 0
to 31. The numbers that can be used here correspond to the numbers that are to 31. The numbers that can be used here correspond to the numbers that are
shown when using the ``PROMPT`` option, and the s390-ccw bios will then try shown when using the ``PROMPT`` option, and the s390-ccw bios will then try
to automatically boot the kernel that is associated with the given number. to automatically boot the kernel that is associated with the given number.
Note that ``0`` can be used to boot the default entry. Note that ``0`` can be used to boot the default entry. If the machine
``loadparm`` is not assigned a value, then the default entry is used.
By default, the machine ``loadparm`` applies to all boot devices. If multiple
devices are assigned a ``bootindex`` and the ``loadparm`` is to be different
between them, an independent ``loadparm`` may be assigned on a per-device basis.
An example guest using per-device ``loadparm``::
qemu-system-s390x -drive if=none,id=dr1,file=primary.qcow2 \
-device virtio-blk,drive=dr1,bootindex=1 \
-drive if=none,id=dr2,file=secondary.qcow2 \
-device virtio-blk,drive=dr2,bootindex=2,loadparm=3
In this case, the primary boot device will attempt to IPL using the default
entry (because no ``loadparm`` is specified for this device or for the
machine). If that device fails to boot, the secondary device will attempt to
IPL using entry number 3.
If a ``loadparm`` is specified on both the machine and a device, the per-device
value will superseded the machine value. Per-device ``loadparm`` values are
only used for devices with an assigned ``bootindex``. The machine ``loadparm``
is used when attempting to boot without a ``bootindex``.
Booting from a network device Booting from a network device