62 lines
2.8 KiB
Diff
62 lines
2.8 KiB
Diff
|
From 3c57b3a6d48d7ddad44b67fdf9ccaebc40e5c125 Mon Sep 17 00:00:00 2001
|
||
|
|
From: Jared Rossi <jrossi@linux.ibm.com>
|
||
|
|
Date: Thu, 14 Nov 2024 19:27:42 -0500
|
||
|
|
Subject: [PATCH 2/9] docs/system/s390x/bootdevices: Update loadparm
|
||
|
|
documentation
|
||
|
|
|
||
|
|
RH-Author: Thomas Huth <thuth@redhat.com>
|
||
|
|
RH-MergeRequest: 297: [c10s] Fixes for the new s390x "boot order" feature
|
||
|
|
RH-Jira: RHEL-68444
|
||
|
|
RH-Acked-by: Miroslav Rezanina <mrezanin@redhat.com>
|
||
|
|
RH-Commit: [1/8] bd74a0794bf0f2872061850ca410bab819c6a0d6 (thuth/qemu-kvm-cs9)
|
||
|
|
|
||
|
|
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>
|
||
|
|
(cherry picked from commit 0271fdc650b212533b8aeaecbedfe8ccf6bbbef3)
|
||
|
|
---
|
||
|
|
docs/system/s390x/bootdevices.rst | 24 +++++++++++++++++++++++-
|
||
|
|
1 file changed, 23 insertions(+), 1 deletion(-)
|
||
|
|
|
||
|
|
diff --git a/docs/system/s390x/bootdevices.rst b/docs/system/s390x/bootdevices.rst
|
||
|
|
index 1a1a764c1c..97b3914785 100644
|
||
|
|
--- a/docs/system/s390x/bootdevices.rst
|
||
|
|
+++ b/docs/system/s390x/bootdevices.rst
|
||
|
|
@@ -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
|
||
|
|
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.
|
||
|
|
-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
|
||
|
|
--
|
||
|
|
2.39.3
|
||
|
|
|