From: ebiederm@xmission.com (Eric W. Biederman)
To: Joshua Jensen <joshua@joshuajensen.org>
Cc: kexec@lists.infradead.org
Subject: Re: kexec-tools not loading iPXE zImage
Date: Mon, 29 Oct 2012 21:14:33 -0700 [thread overview]
Message-ID: <87390wfvfa.fsf@xmission.com> (raw)
In-Reply-To: <loom.20121030T014113-581@post.gmane.org> (Joshua Jensen's message of "Tue, 30 Oct 2012 00:49:39 +0000 (UTC)")
Joshua Jensen <joshua@joshuajensen.org> writes:
> I'm having an issue with kexec not being able to load a freshly compiled
> ipxe.lkrn file, even though it is a zImage:
>
>
> # file ipxe.lkrn
> ipxe.lkrn: Linux kernel x86 boot executable zImage, version \353FHdrS\007\002,RW-
> rootFS,
>
> # kexec -l ipxe.lkrn
> Cannot determine the file type of ipxe.lkrn
>
>
> Any ideas? Is there any way to determine where the error is, with the ipxe.lkrn
> file or kexec ?
Use the source?
My guess is that ipxe.lkrn uses a very old version of the x86 boot
protocol.
Doing what you are doing is a bit iffy if the version of ipxe you are
building depends upon BIOS calls.
It used to be possible to build a .elf version of etherboot that was
bootable via linuxbios and depended on no BIOS calls, and that should
work if the code survived the great gutting of etherboot.
Although this does seem a bit of a round about way to get something
done, loading a more limited bootloader from what is essentially a more
featureful bootloader.
Eric
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2012-10-30 4:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 0:49 kexec-tools not loading iPXE zImage Joshua Jensen
2012-10-30 4:14 ` Eric W. Biederman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87390wfvfa.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=joshua@joshuajensen.org \
--cc=kexec@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.