Bug 1277609 - grub2 netboot failure when SNP exclusive patch present
grub2 netboot failure when SNP exclusive patch present
Product: Fedora
Classification: Fedora
Component: grub2 (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Peter Jones
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-11-03 11:20 EST by George Beshers
Modified: 2017-08-08 08:21 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-08-08 08:21:18 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description George Beshers 2015-11-03 11:20:35 EST
Description of problem:

Fedora24/rawhide grub2 grub2-2.02-0.23.fc24.src.rpm generates grub2 code that
fails to network boot on UV300 platforms.

Instead, the transfer attempts eventually timeout and the grub> prompt 
eventually shows up.

Commenting out this patch fixes the problem:

Patch0050: 0050-reopen-SNP-protocol-for-exclusive-use-by-grub.patch

Research shows that the code in this patch is not upstream at this time.

I'm not a grub2 expert but grub2-2.02-0.23.fc24.src.rpm already contains
the code from this similarly named patch:

Subject: [PATCH 3/3] efinet: open Simple Network Protocol exclusively

I'm not sure if that code serves the same purpose but it's worth checking out.

Please consider removing the 

so UV300 systems can network boot again over the network.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:
Comment 1 paul 2016-01-19 03:51:56 EST
I had this same problem on F23. Removing the 0050 patch allows PXE EFI boot to work. This happens in a vmware VM with EFI boot enabled as well as from a Dell laptop attempting EFI PXE boot.
Comment 2 Jan Kurik 2016-02-24 10:31:46 EST
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
Comment 3 George Beshers 2016-12-22 11:16:26 EST
Getting ready for OnBoarding first week of January.
Comment 4 Fedora End Of Life 2017-07-25 15:26:06 EDT
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 5 Fedora End Of Life 2017-08-08 08:21:18 EDT
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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

Thank you for reporting this bug and we are sorry it could not be fixed.

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