Skip to content
This repository has been archived by the owner on Sep 2, 2021. It is now read-only.

ipxe-shell bootenvs not working #351

Open
CoRfr opened this issue Sep 17, 2019 · 2 comments
Open

ipxe-shell bootenvs not working #351

CoRfr opened this issue Sep 17, 2019 · 2 comments

Comments

@CoRfr
Copy link
Contributor

CoRfr commented Sep 17, 2019

I've tried to use the bootenv from dev-library/bootenvs/ipxeshell.yaml and can't seem to get it to work.
This is the syslinux config:

      DEFAULT local
      PROMPT 0
      TIMEOUT 10
      COM32 chain.c32
      APPEND grub/grub.pxe

First thing that it complains about is that local doesn't exist, so I added LABEL local before COM32 chain.c32, but then it also complains about the APPEND format, and I can't seem to find anything in https://wiki.syslinux.org/wiki/index.php?title=Comboot/chain.c32 regarding tftp.

However it does seem like pxechn.c32 would do the job ( https://wiki.syslinux.org/wiki/index.php?title=Pxechn.c32 ), so I tried that and it fails to run grub.pxe.

It says 'Booting ...' and then some garbage characters and it stopped.

I also try to use an ipxe.pxe with some embed config instead, so something like:

DEFAULT local
PROMPT 0
TIMEOUT 10
LABEL local
  COM32 pxechn.c32
  APPEND ipxe-mymachine.pxe

and it worked.

The original solution mentions something about efi, but it doesn't seem like pxechn.c32 would work in efi mode (I've not tested).

@sygibson
Copy link
Contributor

Bertrand - It sounds like you worked through and found an issue ?

We're curious what you're trying to bootstrap? We might be able to help with alternate paths or information.

@CoRfr
Copy link
Contributor Author

CoRfr commented Sep 19, 2019

In the end it didn't work that well with pxechn.c32 as ipxe crashed (but it was executed a bit ...).
For now I ended-up putting ipxe-mymachine.pxe directly as the boot file for the subnet to skip ... well everything I guess :/
As this, it's simply replacing a previous instance of dnsmasq.

I already have an iPXE chain so I just wanted something on the DR side to, for some hosts, execute that iPXE chain. Now I'm back to all hosts as a workaround since I couldn't figure out how to execute that chain from a syslinux entrypoint.

As for what I'm trying to bootstrap:

  • some hosts have a CoreOS booted from the network
  • some hosts and VMs are running things like Ubuntu 16.04 / 18.04 (so far they are installed "manually", but that's where I'm hopping DR will assist)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants