mirror of
https://github.com/netbootxyz/netboot.xyz.git
synced 2026-04-26 07:35:57 +03:00
[GH-ISSUE #383] Exec format error with uefi on packet.com server #149
Labels
No labels
Hacktoberfest
Hacktoberfest
bootloader
bsd
bug
confirmed
documentation
duplicate
enhancement
enhancement
enhancement
eol
experimental-merged
freebsd
help wanted
invalid
investigate
ipxe
linux
live-os
memdisk
menu
no-issue-activity
no-issue-activity
pull-request
released
todo
upstream
windows
windows
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/netboot.xyz#149
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mikemrm on GitHub (Nov 5, 2019).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/383
Originally assigned to: @antonym on GitHub.
Hello,
On a packet.com server that boots in EFI mode, I'm receiving an error
Could not boot: Exec format errorIt seems the following code is statically pointing to a.kpxe(legacy image)github.com/antonym/netboot.xyz@39f4303790/src/boot.cfg (L118-L124)This was replicated using a
c2.medium.x86with theCustom iPXEos with the url pointing tohttps://boot.netboot.xyzHere is the full console output
I was able to get around this problem by chain loading the
netboot.xyz.efiimage first.Here is the console output with this process
It seems the
${platform}variable can be used to detect whether or not the server is in uefi mode.http://ipxe.org/cfg/platform
I hope this information helps. Let me know if I can provide any additional information.
@antonym commented on GitHub (Nov 6, 2019):
Feel free to give it a try once the packet.efi image is built(probably about 10 min from now) and let me know if that helps things out.
Thanks!
@mikemrm commented on GitHub (Nov 6, 2019):
Seems to be working! Thanks!