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

The new "boot order" feature is sometimes not working as expected [RHEL 9]

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

    • qemu-kvm-9.1.0-6.el9
    • Yes
    • Important
    • CustomerScenariosInitiative
    • 1
    • rhel-virt-hwe-s390x
    • ssg_virtualization
    • 100
    • False
    • False
    • Hide

      None

      Show
      None
    • Yes
    • zKVM CY24Q4
    • Feature
    • Hide
      .KVM on IBM Z now supports more than one boot device

      Guest operating systems running on KVM on IBM Z hosts can attempt booting from additional devices when the primary boot device is not bootable. This feature is supported for the following device types:

      * `virtio-net`
      * `virtio-blk`
      * `virtio-scsi/cdrom`

      To configure the order of the boot devices for the VM, use the `order` parameter on the `<boot>` line of their XML configuration. The VM will now attempt up to 8 devices for booting.

      In addition, these devices now support the `loadparm` parameter for the `<boot>` line of their XML configuration. By using `loadparm`, it is possible to configure which boot entry the device uses when the guest operating system boots from the device.
      Show
      .KVM on IBM Z now supports more than one boot device Guest operating systems running on KVM on IBM Z hosts can attempt booting from additional devices when the primary boot device is not bootable. This feature is supported for the following device types: * `virtio-net` * `virtio-blk` * `virtio-scsi/cdrom` To configure the order of the boot devices for the VM, use the `order` parameter on the `<boot>` line of their XML configuration. The VM will now attempt up to 8 devices for booting. In addition, these devices now support the `loadparm` parameter for the `<boot>` line of their XML configuration. By using `loadparm`, it is possible to configure which boot entry the device uses when the guest operating system boots from the device.
    • Done
    • s390x
    • None

      What were you trying to do that didn't work?

      The following boot scenarios don't work:

      • Boot from a non-bootable CD-ROM image first, then from a hard disk or network device next
      • Boot from a non-bootable network device first, then from a bootable network device
      • The scsi-hd devices don't have a "loadparm" property yet

      Please provide the package NVR for which the bug is seen:

      qemu-kvm-9.1.0-2.el9 

      How reproducible is this bug?

      100%

      Steps to reproduce

      1. /usr/libexec/qemu-kvm ... \
         -drive if=none,id=d1,file=/tmp/bad.dat,format=raw,media=cdrom \
         -device virtio-scsi -device scsi-cd,drive=d1 \
         -drive if=none,id=d2,file=good.qcow2 -device virtio-blk,drive=d2 
      2. /usr/libexec/qemu-kvm ... -netdev user,id=n1 \
         -device virtio-net-ccw,netdev=n1,bootindex=1 \
         -netdev user,id=n2,tftp=/boot,bootfile=vmlinuz \
         -device virtio-net-ccw,netdev=n2,bootindex=2
      3. /usr/libexec/qemu-kvm ... -device scsi-hd,drive=d1,loadparm="1"

      Expected results

      The guest should be able to boot successfully

      Actual results

              thuth@redhat.com Thomas Huth
              thuth@redhat.com Thomas Huth
              Thomas Huth Thomas Huth
              Leo Fu Leo Fu
              Jiří Herrmann Jiří Herrmann
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: