Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 16 Jun 2020 22:37:24 +0100
From:      Miguel C <miguelmclara@gmail.com>
To:        Rebecca Cran <rebecca@bsdio.com>
Cc:        freebsd-current <freebsd-current@freebsd.org>
Subject:   Re: CTF: UEFI HTTP boot support
Message-ID:  <CADGo8CXksUB9vjtqj7gYpBreuucV3eGWbk1V%2Bq-yB2y_AAz=7w@mail.gmail.com>
In-Reply-To: <CADGo8CWRqMdZ1ZD=dpRyNjBRdq9PXTUKF8deQ3NhgPnAFBOJ0A@mail.gmail.com>
References:  <CADGo8CUrJaUdNpoJ3FwpNt09Eq3MEtc2R-TRWa44WizuS6GKFw@mail.gmail.com> <0b38b537-9d9b-b3ae-bae3-bb5b4926bbaa@bsdio.com> <CADGo8CWRqMdZ1ZD=dpRyNjBRdq9PXTUKF8deQ3NhgPnAFBOJ0A@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 16, 2020 at 10:35 PM Miguel C <miguelmclara@gmail.com> wrote:

>
> On Tue, Jun 16, 2020 at 7:25 PM Rebecca Cran <rebecca@bsdio.com> wrote:
>
>> On 6/16/20 5:17 AM, Miguel C wrote:
>>
>> > I've been trying out FreeBSD with raspberry Pi4 (4GB) and wanted to se=
e
>> > what the state of HTTP BOOT is in FreeBSD, so I bumped into this!
>> >
>> > I'm curious if it should be possible to point to a img/iso directly (I
>> > tried to use the img.xz unpacked it and make it available on a local w=
eb
>> > server and that didn't seem to work for me)  but maybe thats cause tho=
se
>> > images miss something, so arm64 aside does that work for amd64? I.E.
>> using
>> > the bootonly.iso?
>>
>> Unfortunately HTTP boot only works as far as the kernel: UEFI fetches
>> loader.efi, the loader fetches and runs the kernel over HTTP -- and then
>> you need to use NFS to mount the filesystem (or have a local root
>> filesystem).
>>
>>
> Thanks for the reply , I can work with that for a live system still bette=
r
> than tftp, http+nfs should be that hard.
>
>
>> UEFI also has RamDisk support, but I don't think that's for remote
>> ISO/disk files, just local files.
>>
>> As for the ISO it does seem to work for remote ISO files, the bhyve con
> presentantion suggests the same and I was able to boot the ubuntu arm64
> install iso using the direct link as a  HTTP BOOT entry,.
>
> =EF=BF=BD>Start HTTP Boot over IPv4....
>>   Station IP address is 172.16.50.62
>>
>>   URI: http:/?172.16.50.106/uarm64.iso
>>   File Size: 916357120 Bytes
>>   Downloading...26%
>>
>
> But we also don't seem to have iso images for the raspberry pi, so it
> might not work there, this does sugget just a link to the .efi file would
> work: https://github.com/jljusten/tianocore/wiki/HTTP-Boot but I tired
> that with no succes
>

Actually that was bad interpertation on my side for a ramdisk to be used it
needs o be iso/img format.


> In any case from what you're saying... for a live system I need http + nf=
s
> for rootfs.
>
> But I'm still clueless how to set that up for FreeBSD, the guide mentione=
d
> here is linux centric, what need to live on the http server side?
>
>
>> --
>> Rebecca Cran
>>
>>
>>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADGo8CXksUB9vjtqj7gYpBreuucV3eGWbk1V%2Bq-yB2y_AAz=7w>