thebeanogamer / rpms / qemu-kvm

Forked from rpms/qemu-kvm 5 months ago
Clone
97168e
From 407e23d7f0c9020404247afe7d4df98505222bbb Mon Sep 17 00:00:00 2001
97168e
From: Thomas Huth <thuth@redhat.com>
97168e
Date: Mon, 14 Nov 2022 14:25:02 +0100
97168e
Subject: [PATCH 1/3] docs/system/s390x: Document the "loadparm" machine
97168e
 property
97168e
MIME-Version: 1.0
97168e
Content-Type: text/plain; charset=UTF-8
97168e
Content-Transfer-Encoding: 8bit
97168e
97168e
RH-Author: Thomas Huth <thuth@redhat.com>
97168e
RH-MergeRequest: 233: s390x: Document the "loadparm" machine property
97168e
RH-Bugzilla: 2128225
97168e
RH-Acked-by: Cornelia Huck <cohuck@redhat.com>
97168e
RH-Acked-by: Cédric Le Goater <clg@redhat.com>
97168e
RH-Acked-by: Jon Maloy <jmaloy@redhat.com>
97168e
RH-Commit: [1/2] e9589ea32d2a8f82971476b644e1063fa14cf822
97168e
97168e
The "loadparm" machine property is useful for selecting alternative
97168e
kernels on the disk of the guest, but so far we do not tell the users
97168e
yet how to use it. Add some documentation to fill this gap.
97168e
97168e
Buglink: https://bugzilla.redhat.com/show_bug.cgi?id=2128235
97168e
Message-Id: <20221114132502.110213-1-thuth@redhat.com>
97168e
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
97168e
Signed-off-by: Thomas Huth <thuth@redhat.com>
97168e
(cherry picked from commit be5df2edb5d69ff3107c5616aa035a9ba8d0422e)
97168e
---
97168e
 docs/system/s390x/bootdevices.rst | 26 ++++++++++++++++++++++++++
97168e
 1 file changed, 26 insertions(+)
97168e
97168e
diff --git a/docs/system/s390x/bootdevices.rst b/docs/system/s390x/bootdevices.rst
97168e
index 9e591cb9dc..d4bf3b9f0b 100644
97168e
--- a/docs/system/s390x/bootdevices.rst
97168e
+++ b/docs/system/s390x/bootdevices.rst
97168e
@@ -53,6 +53,32 @@ recommended to specify a CD-ROM device via ``-device scsi-cd`` (as mentioned
97168e
 above) instead.
97168e
 
97168e
 
97168e
+Selecting kernels with the ``loadparm`` property
97168e
+------------------------------------------------
97168e
+
97168e
+The ``s390-ccw-virtio`` machine supports the so-called ``loadparm`` parameter
97168e
+which can be used to select the kernel on the disk of the guest that the
97168e
+s390-ccw bios should boot. When starting QEMU, it can be specified like this::
97168e
+
97168e
+ qemu-system-s390x -machine s390-ccw-virtio,loadparm=<string>
97168e
+
97168e
+The first way to use this parameter is to use the word ``PROMPT`` as the
97168e
+``<string>`` here. In that case the s390-ccw bios will show a list of
97168e
+installed kernels on the disk of the guest and ask the user to enter a number
97168e
+to chose which kernel should be booted -- similar to what can be achieved by
97168e
+specifying the ``-boot menu=on`` option when starting QEMU. Note that the menu
97168e
+list will only show the names of the installed kernels when using a DASD-like
97168e
+disk image with 4k byte sectors. On normal SCSI-style disks with 512-byte
97168e
+sectors, there is not enough space for the zipl loader on the disk to store
97168e
+the kernel names, so you only get a list without names here.
97168e
+
97168e
+The second way to use this parameter is to use a number in the range from 0
97168e
+to 31. The numbers that can be used here correspond to the numbers that are
97168e
+shown when using the ``PROMPT`` option, and the s390-ccw bios will then try
97168e
+to automatically boot the kernel that is associated with the given number.
97168e
+Note that ``0`` can be used to boot the default entry.
97168e
+
97168e
+
97168e
 Booting from a network device
97168e
 -----------------------------
97168e
 
97168e
-- 
97168e
2.37.3
97168e