Bug 1443904
Summary: | SLOF user interface display bootable device and "SLOF" words duplicate | ||
---|---|---|---|
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: | knoel, michen, qzhang, thuth, virt-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | ppc64le | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | SLOF-20170303-2.git66d250e.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 22:33:27 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-20 08:36:11 UTC
This looks to be cosmetic, and in an error path, so dropping priority. I've now tried to reproduce the problem, and I think it is not related to the empty disk, but rather occurs if SLOF was able to load a file (here the "pxelinux.0" via network), but then failed to execute it. The same thing happens if you boot into grub and then return to the firmware prompt from grub by pressing "c" and typing "halt" at the grub command prompt. Patch is now in upstream: https://github.com/aik/SLOF/commit/06e1e07e5f329dcb2 Fix included in SLOF-20170303-2.git66d250e.el7 This bug is verified for SLOF-20170303-2.git66d250e.el7 Host: 3.10.0-657.el7.ppc64le qemu-kvm-rhev-2.9.0-2.el7.ppc64le SLOF-20170303-2.git66d250e.el7.noarch the steps are same as bug description. test result: "SLOF" is not displayed duplicate, though it is not displayed, I think it is acceptable, as following: SLOF ********************************************************************** QEMU Starting Build Date = Apr 27 2017 23:12:29 FW Version = mockbuild@ release 20170303 Press "s" to enter Open Firmware. Press F12 for boot menu. Populating /vdevice methods Populating /vdevice/nvram@71000000 Populating /vdevice/v-scsi@71000001 SCSI: Looking for devices Populating /vdevice/vty@71000002 Populating /pci@800000020000000 00 0000 (D) : 1234 1111 qemu vga 00 1800 (D) : 1af4 1003 virtio [ serial ] 00 2000 (D) : 1af4 1004 virtio [ scsi ] Populating /pci@800000020000000/scsi@4 SCSI: Looking for devices 00 2800 (D) : 1033 0194 serial bus [ usb-xhci ] 00 3000 (D) : 1af4 1001 virtio [ block ] 00 8000 (D) : 1af4 1000 virtio [ net ] Installing QEMU fb Scanning USB XHCI: Initializing USB Keyboard USB mouse No console specified using screen & keyboard Welcome to Open Firmware Copyright (c) 2004, 2017 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@800000020000000/scsi@6 ... E3404: Not a bootable device! Trying to load: from: /pci@800000020000000/scsi@6 ... E3404: Not a bootable device! Trying to load: from: cdrom ... E3405: No such device Trying to load: from: /pci@800000020000000/ethernet@10 ... Initializing NIC Reading MAC address from device: 9a:7b:7c:7d:7e:72 Requesting information via DHCP: done Using IPv4 address: 10.16.70.148 Requesting file "pxelinux.0" via TFTP from 10.19.42.13 Receiving data: 0 KBytes Repeating TFTP read request... 25 KBytes TFTP: Received pxelinux.0 (25 KBytes) E3403: Bad executable: No boot partition found E3406: Client application returned an error: No boot partition found Type 'boot' and press return to continue booting the system. Type 'reset-all' and press return to reboot the system. Ready! 0 > So, this bug is verified. 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-2017:2093 |