diff options
author | Thomas Huth <thuth@redhat.com> | 2024-11-15 15:12:02 +0100 |
---|---|---|
committer | Thomas Huth <thuth@redhat.com> | 2024-11-18 17:13:47 +0100 |
commit | 429442e52d94f890fa194a151e8cd649b04e9e63 (patch) | |
tree | 306e943335342ea5d9ca7b7015d23884e21fe43d /pc-bios/QEMU,cgthree.bin | |
parent | 6e7c96ae61e0542e97d385084f1f2281a0331054 (diff) |
hw: Add "loadparm" property to scsi disk devices for booting on s390x
While adding the new flexible boot order feature on s390x recently,
we missed to add the "loadparm" property to the scsi-hd and scsi-cd
devices. This property is required on s390x to pass the information
to the boot loader about which kernel should be started or whether
the boot menu should be shown. But even more serious: The missing
property is now causing trouble with the corresponding libvirt patches
that assume that the "loadparm" property is either settable for all
bootable devices (when the "boot order" feature is implemented in
QEMU), or none (meaning the behaviour of older QEMUs that only allowed
one "loadparm" at the machine level). To fix this broken situation,
let's implement the "loadparm" property in for the SCSI devices, too.
Message-ID: <20241115141202.1877294-1-thuth@redhat.com>
Acked-by: Eric Farman <farman@linux.ibm.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'pc-bios/QEMU,cgthree.bin')
0 files changed, 0 insertions, 0 deletions