Bug 1095445 - PXE booting failes with error "Direct booting from floppy is no longer supported" when KERNEL ends in ".0"
Summary: PXE booting failes with error "Direct booting from floppy is no longer suppor...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: syslinux
Version: 20
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1095453
TreeView+ depends on / blocked
 
Reported: 2014-05-07 18:02 UTC by James W. Mills
Modified: 2015-06-29 20:30 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
: 1095453 (view as bug list)
Environment:
Last Closed: 2015-06-29 20:30:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Epic PXE failure (2.19 MB, image/jpeg)
2014-05-07 18:02 UTC, James W. Mills
no flags Details

Description James W. Mills 2014-05-07 18:02:09 UTC
Created attachment 893411 [details]
Epic PXE failure

Description of problem:
PXE boot fails with message "Direct booting from floppy is no longer supported" when kernel image name ends with ".0"

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

syslinux-4.05-7.fc20.x86_64

and also in an earlier version:

PXELINUX 3.80 2009-05-04

How reproducible:

100%

Steps to Reproduce:
1. Edit a known working PXE configuration, changing the KERNEL line from:

KERNEL whatever

to

KERNEL whatever.0

2. ln -s (or copy) the whatever kernel to whatever.0
3. Try and boot from PXE again

Actual results:

Hard lockup with above message hidden in a crazy plaid color pattern

Expected results:

A booting PXE configuration

Additional info:

An example using RHEL 6.5

# cat templates/rhel65.menu 
MENU TITLE Template rhel65

DEFAULT default
TIMEOUT 1
LABEL default
  MENU LABEL default
  KERNEL vmlinuz.fedora.rhel65
  APPEND ks=http://192.168.2.222/kickstart/rhel65/default.cfg initrd=initrd.fedora.rhel65 ramdrive_size=8192


The above configuration boots just fine.  However, if I change KERNEL to this:

KERNEL vmlinuz.fedora.rhel65.0

and run this command (from my tftproot):

# ln -s vmlinuz.fedora.rhel65 vmlinuz.fedora.rhel65.0

And try to PXEboot again, I get the failure.

I'm attaching the screenshot of the failure, mostly because it is awesome, but also because if you squint you can see the error message along the top-left. :)

Thanks!
~james

Comment 1 Fedora End Of Life 2015-05-29 11:47:30 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 2 Fedora End Of Life 2015-06-29 20:30:49 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.


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