Bug 1571860
Summary: | virt-install hangs before to start anaconda GUI for f28 ppc64le | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michel Normand <normand> | ||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 28 | CC: | anaconda-maint-list, berrange, crobinso, dan, jonathan, kellin, lance, vanmeeuwen+fedora, v.podzimek+fedora, vponcova, wwoods | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | ppc64le | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2019-05-28 22:00:49 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: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 1071880 | ||||||||
Attachments: |
|
Description
Michel Normand
2018-04-25 14:37:47 UTC
Re-assigning to anaconda, since the description states the problem is with the guest OS, and the same host works fine with anaconda from F26/27 guest. This is a follow up of the previous bug https://bugzilla.redhat.com/show_bug.cgi?id=1569045 where virt-install was called with text console and not vnc console. Created attachment 1426733 [details] all_tmp_logs.txt anaconda hangs because X failed to start as detailed in attached all_tmp_logs.txt === [anaconda root@localhost /]# tail -f /tmp/anaconda.log 15:01:00,949 INF threading: Thread Done: AnaWaitForConnectingNMThread (140735373832576) 15:01:01,432 WRN display: X startup failed: Xorg exited with status 1 15:01:01,439 WRN stdout: X startup failed, falling back to text mode 15:01:01,440 DBG anaconda: changing display mode from GUI to TUI 15:01:03,457 DBG simpleline: Scheduling screen AskVNCSpoke 15:01:03,458 DBG simpleline: New signal RenderScreenSignal enqueued with source ScreenScheduler 15:01:03,459 DBG simpleline: Starting main loop 15:01:03,459 DBG simpleline: Processing signal RenderScreenSignal 15:01:03,460 DBG simpleline: Processing screen ScreenData(AskVNCSpoke,None,False) 15:01:03,473 DBG simpleline: Input is required by ScreenData(AskVNCSpoke,None,False) screen === === tail of /tmp/X.log === [ 167.245] (EE) Device(s) detected, but none match those in the config file. [ 167.245] (EE) Fatal server error: [ 167.245] (EE) no screens found(EE) [ 167.245] (EE) Please consult the Fedora Project support at http://wiki.x.org for help. [ 167.245] (EE) Please also check the log file at "/tmp/X.log" for additional information. [ 167.245] (EE) [ 167.245] (EE) Server terminated with error (1). Closing log file. === If I compare the X*.log between f27 and f28, this may points to missing "/dev/dri/card0" for f28. What is the cause ? === $grep -i dev.dri Xf28.log Xf27.log Xf28.log:[ 167.235] (EE) open /dev/dri/card0: No such file or directory Xf28.log:[ 167.235] (EE) open /dev/dri/card0: No such file or directory Xf27.log:[ 137.456] (II) xfree86: Adding drm device (/dev/dri/card0) Xf27.log:[ 137.504] (II) modeset(0): using drv /dev/dri/card0 === I guess the previous X.log failure is related tot the bosh_drm failure reported in syslog; BUT I do not know how to continue the investigation. Dan do you have a suggestion ? === extract all_tmp_logs.txt: 15:00:36,276 INFO kernel:fb: switching to bochsdrmfb from OFfb vga 15:00:36,276 INFO kernel:Console: switching to colour dummy device 80x25 15:00:36,276 WARNING kernel:bochs-drm 0000:00:07.0: BAR 0: can't reserve [mem 0x200081000000-0x200081ffffff pref] 15:00:36,277 ERR kernel:[drm:bochs_hw_init [bochs_drm]] *ERROR* Cannot request framebuffer 15:00:36,277 WARNING kernel:Trying to free nonexistent resource <0000200081000000-0000200081ffffff> 15:00:36,277 WARNING kernel:bochs-drm: probe of 0000:00:07.0 failed with error -16 === at least a bypass would be to add "plymouth.enable=0" as virt-install --extra-args as suggested by https://lists.opensuse.org/opensuse-bugs/2016-05/msg02027.html This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. I just verified that no more problem with f29 release. |