robin.thoni/ipxe - git rthoni.com

Michael Brown 8b2942a7db [xen] Cope with unexpected initial backend states Under some circumstances (e.g. if iPXE itself is booted via iSCSI, or after an unclean reboot), the backend may not be in the expected InitWait state when iPXE starts up. There is no generic reset mechanism for Xenbus devices. Recent versions of xen-netback will gracefully perform all of the required steps if the frontend sets its state to Initialising. Older versions (such as that found in XenServer 6.2.0) require the frontend to transition through Closed before reaching Initialising. Add a reset mechanism for netfront devices which does the following: - read current backend state - if backend state is anything other than InitWait, then set the frontend state to Closed and wait for the backend to also reach Closed - set the frontend state to Initialising and wait for the backend to reach InitWait. Signed-off-by: Michael Brown <mcb30@ipxe.org>		10 lat temu
contrib	[errdb] Strip platform error code for non-platform-generated errors	11 lat temu
src	[xen] Cope with unexpected initial backend states	10 lat temu
COPYING	Initial revision	19 lat temu
COPYRIGHTS	[build] Rename gPXE to iPXE	14 lat temu
README	[doc] Re-add README file	14 lat temu

iPXE README File

Quick start guide:

   cd src
   make

For any more detailed instructions, see http://ipxe.org