Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-71834

Support more than one pxe boot entry

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • rhel-10.2
    • CentOS Stream 10
    • qemu-kvm
    • qemu-kvm-10.1.0-1.el10
    • Moderate
    • FutureFeature
    • 2
    • rhel-virt-hwe-s390x
    • ssg_virtualization
    • 10
    • 200
    • False
    • False
    • Hide

      None

      Show
      None
    • Yes
    • Red Hat Enterprise Linux
    • zKVM CY25 sprint 4, zKVM Planning
    • Pass
    • Automated
    • Enhancement
    • Hide
      Feature, enhancement: VMs can boot into several kernels via network
      Reason: Network boot needs a fallback mechanism when a kernel entry is faulty.
      Result: A VM on s390x can now be configured to load from a number of pxe boot entries. For that the //interface/boot@loadparm needs to be set. For example, setting @loadparm=2 will load into the linux2 entry of this configuration:

      # pxelinux
      default linux2
      label linux1
      kernel linux1/kernel.img
      initrd linux1/initrd.img
      append ip=dhcp inst.repo=...
      label linux2
      kernel linux2/kernel.img
      initrd linux2/initrd.img
      append ip=dhcp inst.repo=...
      Show
      Feature, enhancement: VMs can boot into several kernels via network Reason: Network boot needs a fallback mechanism when a kernel entry is faulty. Result: A VM on s390x can now be configured to load from a number of pxe boot entries. For that the //interface/boot@loadparm needs to be set. For example, setting @loadparm=2 will load into the linux2 entry of this configuration: # pxelinux default linux2 label linux1 kernel linux1/kernel.img initrd linux1/initrd.img append ip=dhcp inst.repo=... label linux2 kernel linux2/kernel.img initrd linux2/initrd.img append ip=dhcp inst.repo=...
    • Proposed
    • s390x
    • None

      Feature description 
      As an administrator I want to be able to select which kernel to boot into via PXE in order to select the OS version that I want to install.

If more than one boot entry is available I should be able to select the one that I need via menu. For consistency with boots from disks, I'd want to use the loadparm value to select a boot entry directly.

      Business justification

      Why is this feature needed?

      I want to manage several available OS installations in the same pxe configuration file. Libvirt for example, only allows to set one for TFTP boots, ref. https://libvirt.org/formatnetwork.html#addressing

      Impact to you

      Not sure.

      What hardware or software does this enable?

      N/A

      If hardware, is it on-board in a system (eg, LOM) or an add-on card?

      N/A

      What is the business impact?

      Not sure.

      What market problems / audience does it address?

      N/A

      QE test plan
      TBD

      Additional information

      Sample multi-boot pxe config:

      # pxelinux
default rhel95
label rhel95
kernel 95/kernel.img
initrd 95/initrd.img
append ip=dhcp inst.repo=<rhel-9.5 install tree url>
label rhel96
kernel 96/kernel.img
initrd 96/initrd.img
append ip=dhcp inst.repo=<rhel-9.6 install tree url>

              smitterl@redhat.com Sebastian Mitterle
              smitterl@redhat.com Sebastian Mitterle
              Thomas Huth Thomas Huth
              Sebastian Mitterle Sebastian Mitterle
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: