search

netbootxyz / netboot.xyz

Your favorite operating systems in one place. A network-based bootable operating system installer based on iPXE.
https://netboot.xyz
Apache License 2.0
9.17k stars 680 forks source link

md5sum: command not found #597

Closed benyanke closed 4 years ago

benyanke commented 4 years ago

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:

  1. Boot to menu
  2. "Linux Network Installs"
  3. Ubuntu 18.04
  4. Install
  5. See failure.

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 image

thelamer commented 4 years ago

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 4 years ago

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 4 years ago

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 4 years ago

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 4 years ago

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: image

Next, on my DHCP server (mikrotik), I have the next server DHCP option set to my server hosting netboot.xyz, and the boot file name to menu.ipxe:

image

From there, I simply boot the VM, and it boots from the network. image

image

From there, I'm booted to the menu. image

thelamer commented 4 years ago

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 4 years ago

Thank you, this worked! I did not realize that netboot.xyz.kpxe was the proper boot filename. That worked perfectly.