Bug 1446018
Summary: | The content of SLOF boot menu is messy | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | xianwang <xianwang> |
Component: | SLOF | Assignee: | Thomas Huth <thuth> |
Status: | CLOSED ERRATA | QA Contact: | xianwang <xianwang> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7.4 | CC: | micai, michen, mrezanin, qzhang, thuth, virt-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | ppc64le | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | SLOF-20170724-1.git89f519f.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-10 14:41:52 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
xianwang
2017-04-27 03:05:59 UTC
This issue is for SLOF, so, it is only for powerpc. With the same qemu-kvm-rhev, kernel and same qemu cli as bug description, but SLOF-20160223-6.gitdbbfda4.el7.noarch, the boot menu is as following: (both for once=c and once=n, test result is same) Select boot device: 1. /pci@800000020000000/scsi@6: /pci@800000020000000/scsi@6 2. /pci@800000020000000/scsi@4/disk@100000000000000: /pci@800000020000000/scsi@4/disk@100000000000000 3. /vdevice/v-scsi@71000001/disk@8000000000000000: /vdevice/v-scsi@71000001/disk@8000000000000000 4. /pci@800000020000000/ethernet@10: /pci@800000020000000/ethernet@10 it only displays the "bootindex" devices. I've now suggested a patch series upstream to fix this issue: https://lists.ozlabs.org/pipermail/slof/2017-June/001564.html The new bootmenu code has been merged in upstream: https://github.com/aik/SLOF/commit/fa94a3bb20734cb8e0280b232d16b6d466ec3d53 We'll get it in downstream with the next rebase of the SLOF package. reproduced Version: Host (RHEL7.5): Compose: RHEL7.4 released (RHEL-7.4-20170711.0) kernel-3.10.0- 767 771 .el7 qemu-kvm-rhev-2.10.0-4.el7 SLOF-20170303-1.git66d250e.el7.noarch Guest: Compose: RHEL7.4 released (RHEL-7.4-20170711.0) kernel-3.10.0- 767 771 .el7 Steps to Reproduce is same the as comment0: 1.Boot a guest with qemu cli, it specifies four devices as bootindex /usr/libexec/qemu-kvm \ -name 'avocado-vt-vm1' \ -sandbox off \ -machine pseries-rhel7.4.0 \ -nodefaults \ -vga std \ -chardev socket,id=serial_id_serial0,path=/tmp/console0,server,nowait \ -device spapr-vty,reg=0x30000000,chardev=serial_id_serial0 \ -device virtio-serial-pci,id=virtio_serial_pci0,bus=pci.0,addr=04 \ -chardev socket,path=/tmp/serial0,nowait,id=idQdLRHP,server \ -device virtserialport,id=idBu8FQH,name=vs,bus=virtio_serial_pci0.0,chardev=idQdLRHP \ -object rng-random,filename=/dev/random,id=passthrough-rOXjKxaC \ -device virtio-rng-pci,id=virtio-rng-pci-GVn8yzUA,rng=passthrough-rOXjKxaC,bus=pci.0,addr=05 \ -device nec-usb-xhci,id=usb1,bus=pci.0,addr=06 \ -device pci-ohci,id=usb3,bus=pci.0,addr=07 \ -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=08 \ -drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,media=disk,format=qcow2,file=/root/micai/RHEL74_BE.qcow2 \ -device scsi-hd,id=image1,drive=drive_image1,bus=virtio_scsi_pci0.0,logical_block_size=512,physical_block_size=4096,bootindex=0 \ -drive if=none,id=drive-scsi0-0-1-0,readonly=on \ -device scsi-cd,bus=virtio_scsi_pci0.0,drive=drive-scsi0-0-1-0,bootindex=2,id=scsi0-0-1-0 \ -boot menu=on \ -drive file=disk.qcow2,if=none,id=drive-scsi0-0-0-1,format=qcow2,cache=none \ -device scsi-hd,bus=virtio_scsi_pci0.0,drive=drive-scsi0-0-0-1,bootindex=3,id=scsi0-0-0-1 \ -chardev socket,id=chardev0,path=/tmp/slofpath,server,nowait \ -device spapr-vty,chardev=chardev0 \ -object iothread,id=thread0 \ -device virtio-blk-pci,id=disk,drive=drive-disk0,iothread=thread0 \ -drive file=/root/micai/r3.qcow2,format=qcow2,if=none,id=drive-disk0,cache=none\ -object iothread,id=iothread0 \ -drive file=/root/micai/r1.qcow2,format=qcow2,if=none,cache=none,id=drive_plane,werror=stop,rerror=stop \ -device virtio-blk-pci,drive=d\rive_plane,id=plane,bus=pci.0,addr=09,iothread=iothread0 \ -drive file=/root/micai/r2.qcow2,if=none,id=drive-system-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop \ -device spapr-vscsi,reg=0x1000,id=scsi0 \ -device scsi-hd,drive=drive-system-disk,id=system-disk,bus=scsi0.0 \ -device virtio-net-pci,mac=9a:4f:50:51:52:53,id=id9HRc5V,vectors=4,netdev=idjlQN53,bus=pci.0,addr=11 \ -netdev tap,id=idjlQN53,vhost=on,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown \ -device spapr-vlan,mac=9a:4f:50:51:52:54,netdev=hostnet0,id=net0 \ -netdev tap,id=hostnet0,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown \ -m 8G,slots=4,maxmem=1024G \ -smp 8,cores=4,threads=1,sockets=2 \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -device usb-mouse,id=input1,bus=usb1.0,port=2 \ -device usb-kbd,id=input2,bus=usb1.0,port=3 \ -drive id=drive_cd1,if=none,snapshot=off,aio=threads,cache=none,media=cdrom,format=raw,rerror=stop,werror=stop,file=/root/micai/RHEL-7.4-20170711.0-Server-ppc64-dvd1.iso \ -device scsi-cd,id=cd1,drive=drive_cd1,bus=virtio_scsi_pci0.0,bootindex=1 \ -vnc :1 \ -qmp tcp:0:8881,server,nowait \ -monitor stdio \ -rtc base=utc,clock=host \ -boot order=cdn,once=c,menu=on,strict=off \ -enable-kvm \ -watchdog i6300esb \ -watchdog-action reset \ -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=15 2.Press F12 at the early stage of boot, check the boot menu in SLOF user interface Actual results: it displays again all the boot devices including "bootindex" devices,and Input selection number and the corresponding plate can not be one to one Verified Version: Change SLOF-20170303-1.git66d250e.el7.noarch to SLOF-20170724-2.git89f519f.el7.noarch.rpm Steps to Reproduce is same the as comment0: The phenomenon of normal performance,Enter the selection number and the disk one-to-one correspondence Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0820 |