Post Reply 
Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
iPXE handoff issues
2016-07-12, 17:19 (This post was last modified: 2016-07-12 17:28 by jbirlingmair.)
Post: #9
RE: iPXE handoff issues
(2016-07-12 05:48)mcb30 Wrote:  Using "sanhook" and "keep-san" and then exiting back to the BIOS is not a supported method, and never will be. It may happen to work on some platforms. It's pure luck when it does, and will not be considered a bug when it doesn't. There is no way for iPXE to control what the BIOS does after iPXE exits.

It makes total sense that once iPXE exits, that all bets are off and everything is out if it's control.

Any idea why it works in gPXE?
It seems like gPXE releases the network interface for use by the next item in the boot order. How it does this while maintaining connection to the iSCSI target, I have no idea. iPXE doesn't seem to release lock on the network interface to the next in the boot order.

Just curious, is it possible to chain into a setup.exe on a CD?

I have the WDS solution working, just need to fix a iSCSI drive MBR on one of our drives, and I know the repair tools on the WindowsPE disc I have will work.

I will get started on netbooting WinPE. Better yet, if I can add in the diagnostic and repair tools into one of my WDS boot WIMs then I can just use that.
Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
iPXE handoff issues - jbirlingmair - 2016-06-01, 00:01
RE: iPXE handoff issues - mcb30 - 2016-06-03, 16:51
RE: iPXE handoff issues - mcb30 - 2016-06-03, 19:59
RE: iPXE handoff issues - mcb30 - 2016-07-12, 05:48
RE: iPXE handoff issues - jbirlingmair - 2016-07-12 17:19
RE: iPXE handoff issues - mcb30 - 2016-07-12, 18:42

User(s) browsing this thread: 1 Guest(s)