[ipxe-devel] HTTP SAN / ISO booting

[Andrew Bobulsky]

Hello,

James, Michael merged his ISO SAN boot code into the mainline (master
branch?) iPXE just a few days after the commit referenced in that
original email.  I'm not sure if that fact made the mailing list or
not... I think he mentioned it on IRC when I heard it.

MWH, with regard to the error you're experiencing, I'm fairly certain
that it is because you're trying to connect two SAN devices without
explicitly declaring which INT 13 device you'd like to map to.  By
default, when no device is specified, iPXE will map a SAN target to
BIOS drive 0x80, regardless of whether or not it has done so already.
Your "sanhook" maps that iSCSI target as 0x80, and then the "sanboot"
tries to do the same, and fails.

Instead of the script you posted, try the following:

dhcp net0
set keep-san 1
set initiator-iqn iqn.1998-01.com.vmware:ipxe.testlab.bv.ar.us.local
sanhook iscsi:192.168.65.2::::iqn.1991-05.com.microsoft:ipxe-target
sanboot --drive 0x81 --no-describe http://192.168.65.3/Images/ISOs/myiso.iso


My syntax might not be perfect... not looking at the "help" text or
doc right now :)

With respect to the "--no-describe" parameter, I recall reading
something about iPXE's ibft support not being able to pass more than
one SAN device to the booted OS... haven't looked in to that yet :P

Cheers,
Andrew Bobulsky




On Thu, Jul 28, 2011 at 6:34 PM, <mwhelton at gmail.com> wrote:
>
> This is an exciting development.
>
> OK, but as soon as I tried it, I get this:
>
> http://www.ipxe.org/err/03852019
>
> Here is my embedded boot script:
>
> #!ipxe
> dhcp net0
> set keep-san 1
> set initiator-iqn iqn.1998-01.com.vmware:ipxe.testlab.bv.ar.us.local
> sanhook iscsi:192.168.65.2::::iqn.1991-05.com.microsoft:ipxe-target
> sanboot http://192.168.65.3/Images/ISOs/myiso.iso
>
> I have confirmed that the ISP is accessible with both wget and a browser.
>
> Thanks,
>
> MWH
>
> On Jul 28, 2011 1:05pm, "James A. Peltier" <jpeltier at sfu.ca> wrote:
> > ----- Original Message -----
> >
> >
> > | I think some people have wanted something like this for a while:
> >
> >
> > |
> >
> >
> > | sanboot http://boot.ipxe.org/freedos/fdfullcd.iso
> >
> >
> > |
> >
> >
> > | This is implemented, and works at a reasonable speed (even when
> >
> >
> > | booting over
> >
> >
> > | the Internet). I still need to QA the code and check that it doesn't
> >
> >
> > | introduce any regressions. Temporarily available at
> >
> >
> > |
> >
> >
> > | http://git.ipxe.org/people/mcb30/ipxe.git/shortlog/refs/heads/httpsan
> >
> >
> > |
> >
> >
> > | for anyone who wants to test it.
> >
> >
> > |
> >
> >
> > | Michael
> >
> >
> > | _______________________________________________
> >
> >
> > | ipxe-devel mailing list
> >
> >
> > | ipxe-devel at lists.ipxe.org
> >
> >
> > | https://lists.ipxe.org/mailman/listinfo/ipxe-devel
> >
> >
> >
> >
> >
> > What are the plans for merging this into the iPXE proper code stream?  Is this stable enough now to be used?
> >
> >
> >
> >
> >
> > --
> >
> >
> > James A. Peltier
> >
> >
> > IT Services - Research Computing Group
> >
> >
> > Simon Fraser University - Burnaby Campus
> >
> >
> > Phone   : 778-782-6573
> >
> >
> > Fax     : 778-782-3045
> >
> >
> > E-Mail  : jpeltier at sfu.ca
> >
> >
> > Website : http://www.sfu.ca/itservices
> >
> >
> >          http://blogs.sfu.ca/people/jpeltier
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> >
> >
> > ipxe-devel mailing list
> >
> >
> > ipxe-devel at lists.ipxe.org
> >
> >
> > https://lists.ipxe.org/mailman/listinfo/ipxe-devel
> >
> >
> >
> _______________________________________________
> ipxe-devel mailing list
> ipxe-devel at lists.ipxe.org
> https://lists.ipxe.org/mailman/listinfo/ipxe-devel
>