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

[virt-install] Use per-device boot elements as default on s390x

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

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • rhel-10.2
    • virt-manager
    • None
    • rhel-virt-core-libvirt-2
    • ssg_virtualization
    • 5
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • Red Hat Enterprise Linux
    • Libvirt Bugs already in Sprint
    • None
    • None
    • s390x
    • None

      Feature description

      On s390x, virt-install will set <boot order="1" /> on the disk that's specified via --disk if no other boot parameters are set.

      Business justification

      Why is this feature needed?

      On s390x, <boot dev="hd"/>, at //os/boot usually works but is not supported, not even upstream. Virt-install would therefore per default create an unsupported VM setup.

      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?

      Full boot order support that's being implemented for RHEL 10.0/9.6. Epic will be linked.

      QE test plan

      TBD

              phrdina@redhat.com Pavel Hrdina
              smitterl@redhat.com Sebastian Mitterle
              Pavel Hrdina Pavel Hrdina
              Sebastian Mitterle Sebastian Mitterle
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated: