I'm not really sure what the history of this is, but OBP supports native iscsi boot with a FWARC case. In that caae, all the arguments are provided for and we can boot directly from an iscsi target.
What else does the firmware need to support besides what it already does support, and why? -David Darren J Moffat wrote: > Jack Meng wrote: >> 1. Store the bootpath in firmware (OBP). >> >> Details: >> This approach needs to create a dedicated option value in OBP space to >> store the bootpath, >> and then let Solaris kernel read it during booting. >> >> ISSUES: >> Negative opinion is received from firmware team for the bootpath of an >> iSCSI disk is a Solaris >> specific property (not per IEEE 1275), and firmware shouldn't maintain >> OS-dependent >> properties. > > OBP already stores Solaris specific properties and has Sun system and > Solaris specific code and properties [at the very least for WAN boot but > there was E10k specific stuff there too in the past and I'm sure there > is more]. So I really don't see why this is an issue. It reads to me > like it can be done but someone doesn't want to do it that way, is that > correct ? Or is there a technical reason why it can't be done ? >
