Bug 1515418
| Summary: | RFE: Provide diagnostics for failed boot | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Dr. David Alan Gilbert <dgilbert> | ||||
| Component: | ovmf | Assignee: | Laszlo Ersek <lersek> | ||||
| Status: | CLOSED ERRATA | QA Contact: | FuXiangChun <xfu> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 7.5 | CC: | areis, chayang, dgilbert, juzhang, kchamart, michen, mtessun, pbonzini, xfu | ||||
| Target Milestone: | rc | Keywords: | FutureFeature | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | ovmf-20171011-4.git92d07e48907f.el7 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-04-10 16:31:01 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: | |||||||
| Attachments: |
|
||||||
|
Description
Dr. David Alan Gilbert
2017-11-20 18:49:59 UTC
Created attachment 1356689 [details]
prototype on top of ovmf-20171011-1.git92d07e48907f.el7
This is just a quick PoC. The actual upstream solution should use status code routing / handling / reporting. We already have some REPORT_STATUS_CODE() invocations in EfiBootManagerBoot() and BdsEntry(); some new ones should be added, and the current ones should emit more information (e.g. with EFI_STATUS_CODE_DATA_TYPE_DEBUG_GUID).
Posted upstream series:
[edk2] [PATCH 0/5] MdeModulePkg, OvmfPkg: more easily visible boot progress
reporting
http://mid.mail-archive.com/20171122235849.4177-1-lersek@redhat.com
https://lists.01.org/pipermail/edk2-devel/2017-November/017850.html
Steps for virt-QE, from Dave: """ a) Install a normal BIOS VM (e.g. Fedora or RHEL) b) Use virt-manager to create a new VM, telling it to import the disk image from the VM in (a) but to customize the VM before install c) During the customize, change the machine type/bios to q35+ovmf d) Let it boot Current versions stick at the Tianocore logo This fix gives useful feedback and lets you get to the boot manager. """ Thanks. Fix included in ovmf-20171011-4.git92d07e48907f.el7 Reproduced this bug with OVMF-20171011-1.git92d07e48907f.el7.noarch & qemu-kvm-rhev-2.10.0-11.el7.x86_64. Result: 1)stick at the Tianocore logo 2)OVMF log: Error: Image at 0007CEA3000 start failed: Unsupported Error: Image at 0007CDDF000 start failed: Unsupported Error: Image at 0007CD6D000 start failed: Unsupported Error: Image at 0007BE1A000 start failed: Unsupported Error: Image at 0007BD34000 start failed: Aborted [Bds] Unable to boot! 3) cann't get to the boot manager Verified this bug with OVMF-20171011-4.git92d07e48907f.el7.noarch & qemu-kvm-rhev-2.10.0-11.el7.x86_64. Result: 1)useful feedback as below: BdsDxe: No bootable option or device was found. BdsDxe: Press any key to enter the Boot Manager Menu. 2)type Enter, I can get to the boot manager. 3)part of ovmf log as below: ....... SataControllerStart error return status = Already started BlockSize : 512 LastBlock : 77FFFFF BlockSize : 512 LastBlock : 1FFFFF BlockSize : 512 LastBlock : 75FF7FF SataControllerStart START SataControllerStart error return status = Already started BlockSize : 512 LastBlock : 77FFFFF BlockSize : 512 LastBlock : 1FFFFF BlockSize : 512 LastBlock : 75FF7FF BlockSize : 512 LastBlock : 77FFFFF BlockSize : 512 LastBlock : 1FFFFF BlockSize : 512 LastBlock : 75FF7FF BlockSize : 512 LastBlock : 1FFFFF BlockSize : 512 LastBlock : 75FF7FF [Bds] Expand \EFI\BOOT\BOOTX64.EFI -> <null string> 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:0902 Followup upstream patch series (possible candidate for a separate backport or rebase): [edk2] [PATCH v2 0/5] MdeModulePkg, OvmfPkg, ArmVirtPkg: more visible boot progress reporting https://lists.01.org/pipermail/edk2-devel/2019-February/036965.html http://mid.mail-archive.com/20190220081644.8238-1-lersek@redhat.com [edk2] [PATCH v3 0/5] MdeModulePkg, OvmfPkg, ArmVirtPkg: more visible boot progress reporting https://lists.01.org/pipermail/edk2-devel/2019-February/037068.html http://mid.mail-archive.com/20190221104112.14995-1-lersek@redhat.com (In reply to Laszlo Ersek from comment #29) > [edk2] [PATCH v3 0/5] MdeModulePkg, OvmfPkg, ArmVirtPkg: more visible boot > progress reporting > https://lists.01.org/pipermail/edk2-devel/2019-February/037068.html > http://mid.mail-archive.com/20190221104112.14995-1-lersek@redhat.com Upstream commit range 2df879827442..1797f32e0a19. |