| Summary: | [dracut] basic plymouth theme used with virtio-gpu video device | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joachim Frieben <jfrieben> | ||||
| Component: | plymouth | Assignee: | Ray Strode [halfline] <rstrode> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 27 | CC: | dracut-maint-list, elad, fedora, gansalmon, harald, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, rstrode, zbyszek | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-11-30 22:22:50 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: | |||||
| Attachments: |
|
||||||
This isn't a kernel problem. It's likely related to whatever is bundled in the initramfs for plymouth. (In reply to Josh Boyer from comment #1) Kernel module virtio-gpu.ko is present in the rescue initrd file, and thus, when booting from the latter, then the boot screen looks as expected. However, even across kernel upgrades with video device virtio_gpu active upon boot, the needed kernel module is not included in the new initrd file whereas qxl.ko is. This does not seem right to me and is the cause of this issue. This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. Issue is still present for all of Fedora 26, 27, and 28. Please add kernel module virtio_gpu to the default list of modules to be included during the creation of the initrd file when installing a new kernel. Note that virtio_gpu is currently the standard video device when creating a new virtual machine with gnome-boxes, thanks. This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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. Comparing current Fedora 27 with current Fedora 28, it turns out that despite using the same Linux kernel version, namely 4.17.12-100.fc27 and 4.17.12-200.fc28, respectively, the Fedora 27 boot screen still seems to use the basic frame buffer device whereas Fedora 28 is using the correct virtio-vga device. Fedora 27 features dracut-046-8.git20180105.fc27 compared to dracut-048-14.git20180726.fc28 in the case of Fedora 28. Comparing the content of both initramfs files, Fedora 28 additionally provides ../drivers/block/virtio_blk.ko.xz ../drivers/char/virtio_console.ko.xz ../drivers/gpu/drm/virtio ../drivers/gpu/drm/virtio/virtio-gpu.ko.xz ../drivers/net/virtio_net.ko.xz ../drivers/scsi/virtio_scsi.ko.xz which explains the correct behaviour of Fedora 28. Even though resolution CURRENT_RELEASE is possible I suggest to extend the initramfs of Fedora 27 in order to provide the listed kernel modules. This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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. |
Created attachment 1206504 [details] Boot screen with basic plymouth theme Description of problem: When booting current Fedora 25 in gnome-boxes with video device virtio-gpu, then not the standard Fedora plymouth theme ("Charge") is being used but the basic theme as shown in the attached screenshot. Version-Release number of selected component (if applicable): kernel-4.8.0-0.rc8.git0.1.fc25 How reproducible: Always Steps to Reproduce: 1. Boot Fedora 25 in gnome-boxes with video device virtio-gpu. Actual results: Boot screen is not using the standard Fedora plymouth theme but some basic plymouth theme instead. Expected results: Boot screen is using the standard Fedora plymouth theme. Additional info: The same issue applied to Fedora 24 with kernels equal or prior to kernel-4.7.4-200.fc24. However, after upgrading to kernel-4.7.5-200.fc24, the standard Fedora plymouth theme is being used.