Bug 1515694 - Xen boot entries ask for non-exisiting grub2 module2.mod
Summary: Xen boot entries ask for non-exisiting grub2 module2.mod
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 27
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-21 09:05 UTC by Helmut Schlattl
Modified: 2020-07-17 16:49 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 22:28:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Helmut Schlattl 2017-11-21 09:05:38 UTC
Description of problem:
grub2-mkconfig creates xen boot entries with 'insmod module2' while this module is not provided (or already built-in?). This causes an error message during the boot process, but it continues after a while (or by pressing a key). 

Version-Release number of selected component (if applicable):
grub2-tools-2.02-19.fc27.x86_64
grub2-pc-modules-2.02-19.fc27.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create new config file with xen-entries by grub2-mkconfig
2. Boot this kernel
3.

Actual results:
After selecting the entry, grub2 complains about non-existing module2

Expected results:
Boot without grub2-warnings.

Additional info:
Apparently the scripts /etc/grub.d/20_linux_xen needs some amendments.

Comment 1 Lars S. Jensen 2018-01-11 12:23:12 UTC
module2 is part of multiboot2.mod see /usr/lib/grub/i386-pc/command.lst:
multiboot2: multiboot2
module2: multiboot2
multiboot: multiboot
module: multiboot

so removed the 'insmod ${module_loader}' line from /etc/grub.d/20_linux_xen and it is related to #1486002#33 that is closed.
I don't know if is also working on arm64

Comment 2 Helmut Schlattl 2018-01-12 13:33:52 UTC
I am aware of the bug fix, but will the patch also go into the rpm-package some day?
 
(Bug #1486002 is not closed yet).

Comment 3 Ben Cotton 2018-11-27 14:43:06 UTC
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.

Comment 4 Ben Cotton 2018-11-30 22:28:34 UTC
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.

Comment 5 Bill McGonigle 2018-12-02 14:18:54 UTC
Just upgraded to f28 and hit this.  Please bump version.

Xen boots with an f27 kernel currently, but this module error seems to be causing confusion, e.g.  bug 1486002 .  Addressing this will help clarify other issues.

# grep module2 /etc/grub.d/20_linux_xen 
                module_loader="module2"

# rpm -qf /etc/grub.d/20_linux_xen 
grub2-tools-2.02-38.fc28.x86_64

# rpm -q xen
xen-4.10.2-2.fc28.x86_64


Note You need to log in before you can comment on or make changes to this bug.