Re: port-amd64/55954: bootx64.efi hangs up on boot

[Aleksey Arens <aza.sea.agenda%gmail.com@localhost>]

The following reply was made to PR port-amd64/55954; it has been noted by GNATS.

From: Aleksey Arens <aza.sea.agenda%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: port-amd64-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
	netbsd-bugs%netbsd.org@localhost
Subject: Re: port-amd64/55954: bootx64.efi hangs up on boot
Date: Sat, 6 Feb 2021 13:56:18 -0800

 Hello Matthew,
 
 >  this might work if it was only performed only when bootx64.efi
 >  is loaded from a disk, vs via pxe or something.  they may not
 >  even be local disks at all in this case.
 
 As diskless(8) suggests, in the PXE netboot case, the network has to
 be used anyway for
 subsequent steps.  What this means in practice is that in general for
 the machine in
 question the PXE netbooting is not going to be an option -- it would
 simply hang up.
 
 A diskless(8) also vaguely suggests that the configuration for
 bootloader in the case of
 PXE boot is supplied by means other than reading a local config file.
 
 In general, the local config is used if the boot is performed from a
 local disk, with the
 kernel residing locally.  This behaviour does not involve the use of a
 network, and it is
 traditional.  So, it is a reasonable to require that network-related
 functionality is only
 be initialized whence a non-traditional behaviour is desired for local
 disk boots, whence
 a kernel is to be loaded from the network.  That would not be a common
 configuration.