Date: Tue, 19 Mar 2019 17:14:15 -0600 From: Warner Losh <imp@bsdimp.com> To: James Snow <snow@teardrop.org> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: boot/pxeboot broken in freebsd-12? Message-ID: <CANCZdforUUcd9E8-KSS4O-kWAZzukV6c-Qrk%2BqSFY-0=JBkcnQ@mail.gmail.com> In-Reply-To: <20190319225319.GD91288@teardrop.org> References: <20190319225319.GD91288@teardrop.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 19, 2019 at 4:53 PM James Snow <snow@teardrop.org> wrote: > Hello -stable, > > We have a PXE environemt that builds FreeBSD-11 boxes. We've started > to dip our toes into the 12.x waters, but have had trouble getting > FreeBSD-12 to pxeboot. It would crash and burn like so: > > Startup error in /boot/lua/loader.lua: > LUA ERROR: cannot open /boot/lua/loader.lua: device not configured > > On a whim, I pulled the boot/pxeboot binary from our FreeBSD-11 > environment into the new FreeBSD-12 environment, and PXE clients started > coming right up. > > Is FreeBSD-12's pxeboot broken or have I missed something? > You need to set the NFS mount point properly. I've been able to boot the FreeBSD 12.0R installer with PXE (after fixing some issues downstream) and had that error before I had dnsmasq answering queries properly: dhcp-vendorclass=BIOS,PXEClient:Arch:00000 dhcp-userclass=FreeBSD,FreeBSD dhcp-boot=net:BIOS,12.0R-i386-bootonly/boot/pxeboot,10.0.0.5,10.0.0.5 dhcp-boot=net:BIOS,12.0R-i386-bootonly/boot/pxeboot,10.0.0.5,10.0.0.5 dhcp-option=net:BIOS,option:root-path,10.0.0.5:/tftpboot/12.0R-i386-bootonly dhcp-host=mr_noodle,set:mr_noodle dhcp-boot=tag:mr_noodle,12.0R-i386-bootonly/boot/pxeboot,10.0.0.5,10.0.0.5 dhcp-option=tag:mr_noodle,option:root-path,10.0.0.5: /tftpboot/12.0R-i386-bootonly dhcp-boot=tag:FreeBSD,12.0R-i386-bootonly/boot/pxeboot,10.0.0.5,10.0.0.5 dhcp-option=tag:FreeBSD,option:root-path,10.0.0.5: /tftpboot/12.0R-i386-bootonly is what I used in dnsmasq to get the job done. It was likely overkill (10.0.0.5 was the NFS, ftfpd and other servers for this exercise). I had to (a) create a blank /etc/fstab in the mdconfig mounted image and (b) create the proper /etc/resolv.conf in the F4 shell window just after I hit commit to make things work. And then configure the network by hand because the installer's config was wrong. So we've had some regression, just not the regression you are seeing. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdforUUcd9E8-KSS4O-kWAZzukV6c-Qrk%2BqSFY-0=JBkcnQ>