71aed0d95c
- kvm-virtio-net-Add-queues-before-loading-them.patch [RHEL-69477] - kvm-docs-system-s390x-bootdevices-Update-loadparm-docume.patch [RHEL-68440] - kvm-docs-system-bootindex-Make-it-clear-that-s390x-can-a.patch [RHEL-68440] - kvm-hw-s390x-Restrict-loadparm-property-to-devices-that-.patch [RHEL-68440] - kvm-hw-Add-loadparm-property-to-scsi-disk-devices-for-bo.patch [RHEL-68440] - kvm-scsi-fix-allocation-for-s390x-loadparm.patch [RHEL-68440] - kvm-pc-bios-s390x-Initialize-cdrom-type-to-false-for-eac.patch [RHEL-68440] - kvm-pc-bios-s390x-Initialize-machine-loadparm-before-pro.patch [RHEL-68440] - kvm-pc-bios-s390-ccw-Re-initialize-receive-queue-index-b.patch [RHEL-68440] - kvm-vnc-fix-crash-when-no-console-attached.patch [RHEL-61633] - Resolves: RHEL-69477 (qemu crashed when migrate vm with multiqueue from rhel9.4 to rhel9.6) - Resolves: RHEL-68440 (The new "boot order" feature is sometimes not working as expected [RHEL 9]) - Resolves: RHEL-61633 (Qemu-kvm crashed if no display device setting and switching display by remote-viewer [rhel-9])
46 lines
1.9 KiB
Diff
46 lines
1.9 KiB
Diff
From 5a0451f82a143dbaa0f75543a75c8e4560ac477f Mon Sep 17 00:00:00 2001
|
|
From: Thomas Huth <thuth@redhat.com>
|
|
Date: Mon, 11 Nov 2024 11:55:06 +0100
|
|
Subject: [PATCH 03/10] docs/system/bootindex: Make it clear that s390x can
|
|
also boot from virtio-net
|
|
MIME-Version: 1.0
|
|
Content-Type: text/plain; charset=UTF-8
|
|
Content-Transfer-Encoding: 8bit
|
|
|
|
RH-Author: Thomas Huth <thuth@redhat.com>
|
|
RH-MergeRequest: 298: [c9s] Fixes for the new s390x "boot order" feature
|
|
RH-Jira: RHEL-68440
|
|
RH-Acked-by: Cédric Le Goater <clg@redhat.com>
|
|
RH-Acked-by: Miroslav Rezanina <mrezanin@redhat.com>
|
|
RH-Commit: [2/8] 2921f4532ad7b0891dea251a4d768776170c6271 (thuth/qemu-kvm-cs9)
|
|
|
|
Let's make it clear that s390x can also boot from virtio-net, to avoid
|
|
that people think that s390x can only boot from disk devices.
|
|
|
|
Reported-by: Boris Fiuczynski <fiuczy@linux.ibm.com>
|
|
Message-ID: <20241111105506.264640-1-thuth@redhat.com>
|
|
Reviewed-by: Prasad Pandit <pjp@fedoraproject.org>
|
|
Reviewed-by: Boris Fiuczynski <fiuczy@linux.ibm.com>
|
|
Signed-off-by: Thomas Huth <thuth@redhat.com>
|
|
(cherry picked from commit b8c5fdc6588f82d95807be0eb2215d215a3ba16e)
|
|
---
|
|
docs/system/bootindex.rst | 2 +-
|
|
1 file changed, 1 insertion(+), 1 deletion(-)
|
|
|
|
diff --git a/docs/system/bootindex.rst b/docs/system/bootindex.rst
|
|
index 988f7b3beb..5e1b33ee22 100644
|
|
--- a/docs/system/bootindex.rst
|
|
+++ b/docs/system/bootindex.rst
|
|
@@ -53,7 +53,7 @@ booting. For instance, the x86 PC BIOS boot specification allows only one
|
|
disk to be bootable. If boot from disk fails for some reason, the x86 BIOS
|
|
won't retry booting from other disk. It can still try to boot from
|
|
floppy or net, though. In the case of s390x BIOS, the BIOS will try up to
|
|
-8 total devices, any number of which may be disks.
|
|
+8 total devices, any number of which may be disks or virtio-net devices.
|
|
|
|
Sometimes, firmware cannot map the device path QEMU wants firmware to
|
|
boot from to a boot method. It doesn't happen for devices the firmware
|
|
--
|
|
2.39.3
|
|
|