David Kahn wrote:
I never said that the OBP should know which driver Solaris should use.
I said that the choice of driver should: a) be defaulted, b) be settable
via boot archive and/or boot option. Administering a choice of driver
via boot archive seems reasonable to me. Storing the full
David Kahn wrote:
Bart Smaalders wrote:
Tarl Neustaedter wrote:
The knowledge of which driver to use within Solaris
isn't needed until after this stage - so I don't think it belongs in
the boot command in the first place.
This is correct... and storing such driver info somewhere where
I just submitted FWARC/2009/498 for Tarl, which adds
a new /chosen property, iscsi-tpgt.
Apparently, the information was already available to
OF, so it was easy enough to publish it, even though
we don't need it, and in theory anybody could do the
same thing that OF does to get it. Nonetheless,
I never said that the OBP should know which driver Solaris should use.
I said that the choice of driver should: a) be defaulted, b) be settable
via boot archive and/or boot option. Administering a choice of driver
via boot archive seems reasonable to me. Storing the full boot path in
the
Nicolas Williams wrote:
On Mon, Sep 14, 2009 at 03:27:45PM -0400, Tarl Neustaedter wrote:
Nicolas Williams wrote:
[...]
If it's provided by the target then the OBP should pass it to the OS.
If that's the consensus, we'll modify FWARC 2008/466 to accommodate -
probably
On Tue, Sep 15, 2009 at 05:21:32PM +0800, Jack wrote:
Nicolas Williams wrote:
On Mon, Sep 14, 2009 at 03:27:45PM -0400, Tarl Neustaedter wrote:
Solaris setup the bootpath before triggering discovery - logging to
the iSCSI target for this case, therefore a correct value is very
helpful here.
? 09-9-15 ??8:03, Nicolas Williams ??:
On Tue, Sep 15, 2009 at 05:21:32PM +0800, Jack wrote:
Nicolas Williams wrote:
On Mon, Sep 14, 2009 at 03:27:45PM -0400, Tarl Neustaedter wrote:
Solaris setup the bootpath before triggering discovery - logging to
the iSCSI target
Bart Smaalders wrote:
Tarl Neustaedter wrote:
The knowledge of which driver to use within Solaris
isn't needed until after this stage - so I don't think it belongs in
the boot command in the first place.
This is correct... and storing such driver info somewhere where a
special program
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
On Fri, Sep 11, 2009 at 11:31:10PM +0800, Jack Meng wrote:
The project team has been trying different approaches to solve the
'bootpath' issue,
2. Store the bootpath in boot_archive as the existing mechanism to
support UFS booting in x86.
3. Dynamically build the bootpath before
On Mon, Sep 14, 2009 at 02:51:35PM -0400, Tarl Neustaedter wrote:
Nicolas Williams wrote:
[...]
Er, how can the OBP not know about TPGT?
It's provided by the target during the login sequence. Potentially we
should have an RFE for OBP to specify TPGT rather than accepting what
the target
On Mon, Sep 14, 2009 at 03:27:45PM -0400, Tarl Neustaedter wrote:
Nicolas Williams wrote:
[...]
If it's provided by the target then the OBP should pass it to the OS.
If that's the consensus, we'll modify FWARC 2008/466 to accommodate -
probably create a new chosen property to export
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?
Darren J Moffat wrote:
[...]
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
Nicolas Williams wrote:
[...]
Er, how can the OBP not know about TPGT?
It's provided by the target during the login sequence. Potentially we
should have an RFE for OBP to specify TPGT rather than accepting what
the target tells us, but that's how it currently works.
Nicolas Williams wrote:
[...]
If it's provided by the target then the OBP should pass it to the OS.
If that's the consensus, we'll modify FWARC 2008/466 to accommodate -
probably create a new chosen property to export it. Or Solaris could
fetch the information by itself.
That leaves the
Tarl Neustaedter wrote:
The knowledge of which driver to use within Solaris
isn't needed until after this stage - so I don't think it belongs in the
boot command in the first place.
This is correct... and storing such driver info somewhere where a
special program needs to update it is just
Mark A. Carlson wrote:
Darren J Moffat wrote:
... suggest it be put in waiting need spec and that the project
team work with the installer and boot teams (in particular I strongly
suggest taking advice from Jan for the boot issues).
Done.
-- mark
Adding materials about investigations made
Jan Setje-Eilers wrote:
Bart Smaalders wrote:
Mark Carlson wrote:
Such a bootpath is not available from OBP, and also Solaris is
unable to
make up one for,
1) Different disk drivers, 'sd' or 'ssd' can be attached to an
iSCSI disk
2) Different TPGT can be
Darren J Moffat wrote:
... suggest it be put in waiting need spec and that the project team
work with the installer and boot teams (in particular I strongly
suggest taking advice from Jan for the boot issues).
Done.
-- mark
I am sponsoring this case for Jack Meng. It requests a minor binding and he
ONNV consolidation. I have marked it automatic, but am happy to start a timer
if an ARC member requests.
-- mark
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
Bart Smaalders wrote:
Mark Carlson wrote:
Such a bootpath is not available from OBP, and also Solaris is
unable to
make up one for,
1) Different disk drivers, 'sd' or 'ssd' can be attached to an
iSCSI disk
2) Different TPGT can be used to access the boot
Mark Carlson wrote:
Such a bootpath is not available from OBP, and also Solaris is unable to
make up one for,
1) Different disk drivers, 'sd' or 'ssd' can be attached to an
iSCSI disk
2) Different TPGT can be used to access the boot disk
23 matches
Mail list logo
