[ipxe-devel] [PATCH] Format HTTP Range with unsigned long long

Linus Lüssing linus.luessing at c0d3.blue
Wed May 31 09:33:25 UTC 2017


On Tue, May 30, 2017 at 10:51:49PM +0100, Michael Brown wrote:
> On 30/05/17 11:07, Linus Lüssing wrote:
> >Thanks! That indeed helped, http exchange looks fine now in
> >Wireshark. Now, for both a Kali Linux and Fedora 24 ISO first Grub, then the
> >Linux kernel and then the initrd load and run fine. However both of
> >them still fail when they try to mount the rootfs.
> >
> >I guess I'm either missing something simple or having some
> >fundamental misunderstanding regarding sanboot? I'm currently
> >trying to just boot such Live images via a:
> >
> >"sanboot http://<path>/file.iso"
> 
> That probably won't work, because the loaded operating system doesn't
> understand the concept of an HTTP SAN device.
> 
> You can boot a live Fedora from HTTP with a syntax such as:
> 
>   #!ipxe
>   set repo http://server/path/to/distro
>   kernel ${repo}/images/pxeboot/vmlinuz \
>      initrd=initrd.img \
>      root=live:${repo}/LiveOS/squashfs.img
>   initrd ${repo}/images/pxeboot/initrd.img
>   boot
> 
> This doesn't actually use HTTP SAN booting: instead you load the
> kernel+initrd directly and passing a kernel command-line argument which
> tells the initrd where to find the rest of the distro.

I was hoping not having to extract kernel/initrd/rootfs for every LiveOS
I want to add. Being able to just throw in ISOs directly would have been
so convenient :D.

But thanks! (and the "root=live:" looks good/easy too, did not
know about it before; so far I had been doing this with NFS instead
of HTTP)


PS: Is there some documentation regarding SAN you would recommend?
I'm a little curious now how difficult it might be to teach Linux
to map a SAN device to a place where a LiveOS could find and mount
it as root device by default.



More information about the ipxe-devel mailing list