thebeanogamer / rpms / qemu-kvm

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