https://bugzilla.novell.com/show_bug.cgi?id=785818
https://bugzilla.novell.com/show_bug.cgi?id=785818#c3
--- Comment #3 from Vasu Chandrasekhara 2012-11-20 09:51:53 UTC ---
Hi Lee, not quite, but moving the target could also be a problem in the current
implementation.
The issue is that with modern iscsi NICs, the initrd should not persist iscsi
initiator & target information. That information should be read from the iBFT
dynamically.
(If gpxe - http://etherboot.org/wiki/sanboot - is used and iBFT is not
possible, of course persisting the iscsi info in the inird makes sense.)
This way, you have a "neutral" Linux OS image residing on an arbitrary LUN and
then you can program your iSCSI capable NIC (e.g. in the BIOS or UEFI) to point
to that LUN.
The issue above, which I am pointing to, is that the iBFT is dynamically read
in boot-ibft.sh, but not acted upon in boot-network.sh.
Ideally, the only parameters which needs to be passed in the boot parameter for
an iscsi boot of Linux is: ibft_availabe (this could imply root_iscsi).
Best,
Vasu
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.