mirror of
https://github.com/netbootxyz/netboot.xyz.git
synced 2026-04-25 15:15:56 +03:00
[GH-ISSUE #597] md5sum: command not found #186
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#186
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 @benyanke on GitHub (Apr 13, 2020).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/597
Originally assigned to: @thelamer on GitHub.
Describe the bug
When using the ubuntu installer on 2.0.11, the command md5sum doesn't exist and fails.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Ideally md5sum exists, or at the least, it is removed so it doesn't fail.
The failing command appears to be line 68 of ubuntu.ipxe.
Screenshots
@thelamer commented on GitHub (Apr 16, 2020):
I can't replicate this in UEFI or PCBios.
Can you tell us more about your environment like how you are booting netboot.xyz?
@antonym commented on GitHub (Apr 16, 2020):
Unable to replicate it either as the md5sum tools are currently compiled into the latest image. Make sure you are using the latest bootloader if you aren't already.
@benyanke commented on GitHub (Apr 17, 2020):
The screenshot above and tests have been done on QEMU/KVM on Ubuntu 18.04.
How can I go about ensuring I'm using the latest bootloader?
@thelamer commented on GitHub (Apr 17, 2020):
I asked how you are booting netboot.xyz and your response was with QEMU/KVM on Ubuntu .
Think objectively here, we need information about where you got the bootloader, how you are hosting it, what your basic network boot setup looks like.
Are you even network booting ?
Have you tried the CD/usb ?
@benyanke commented on GitHub (Apr 18, 2020):
Sure - here's my setup:
netboot.xyz is running on a physical host on my LAN, in docker, from image:
linuxserver/netbootxyz:latest, with port forwards on 69/UDP and 3000.VM network is a bridge to my LAN subnet, so the VMs exist directly on the LAN.
The KVM/QEMU VM is set to use the NIC in the boot order. This is the NIC bridged to my LAN.
Virt-manager:
Next, on my DHCP server (mikrotik), I have the
next serverDHCP option set to my server hosting netboot.xyz, and theboot file nameto menu.ipxe:From there, I simply boot the VM, and it boots from the network.
From there, I'm booted to the menu.
@thelamer commented on GitHub (Apr 18, 2020):
You need to double boot and chain into the boot payload not the ipxe file.
Right now you are using KVM's slimmed down IPXE bin to directly chain into the ipxe file.
Your boot file name on your DHCP server needs to be
netboot.xyz.kpxe, it takes longer but it is what is needed to boot stuff properly as we build a heavy IPXE bin with all the bells and whistles that is actually up to date.@benyanke commented on GitHub (Apr 19, 2020):
Thank you, this worked! I did not realize that netboot.xyz.kpxe was the proper boot filename. That worked perfectly.