From: Hannes Duerr <h.duerr@proxmox.com>
To: Alwin Antreich <alwin@antreich.com>,
Christoph Heiss <c.heiss@proxmox.com>,
pve-devel@lists.proxmox.com
Subject: Re: [PATCH installer] assistant: add support for splitting ISO into (i)PXE-compatible files
Date: Wed, 25 Feb 2026 16:07:54 +0100 [thread overview]
Message-ID: <0fec8ec2-232f-4a4a-b9d7-bd9deb484045@proxmox.com> (raw)
In-Reply-To: <e1208d839381447803b8d919548ff42038469837@antreich.com>
On 2/18/26 8:31 PM, Alwin Antreich wrote:
>> FWIW, I'm also working on PXELINUX support, but that has a few quirks.
>>
>> Tested this with a TFTP server and default iPXE. I.e. copying
>> `boot.ipxe`, `vmlinuz`, `initrd.img` and the `.iso` file to the TFTP
>> server root, and then booting off it using the iPXE commandline using:
>>
>> $ dhcp
>> $ chain --autofree tftp://<ip-of-tftp-server>/boot.ipxe
>>
>> In addition, tested this with OPNsense set up such that it automatically
>> instructs iPXE to load `boot.ipxe` from the set TFTP server, completely
>> automating an installation from booting the machine to being able to
>> log into the finished system.
>>
> Frank and I have tested your patch and aside from what Hannes already wrote, it worked nicely. +1
>
> I've tried additionally to PXE boot it with secure boot. It would be awesome if you could add a signed ipxe.efi.
> Sadly I had to go with the shimx64.efi route (my test with the shim command didn't work :/ ).
We can't do the signing our self, but @f.gruenbichler told me yesterday
that there is finally secureboot support from ipxe upstream since last
november.
Further information and a link to download the signed ipxe-shim can be
found in the pull-request [0]
[0]
https://github.com/rhboot/shim-review/issues/319#issuecomment-3521239969
> I also love the idea of a netboot image that could bring down the memory usage and load time. Otherwise ipxe has sanboot, that might help on the ipxe front.
>
> Thanks
>
> Cheers,
> Alwin
next prev parent reply other threads:[~2026-02-25 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 12:09 Christoph Heiss
2026-02-16 16:23 ` Hannes Duerr
2026-02-18 19:23 ` Alwin Antreich
2026-02-25 15:07 ` Hannes Duerr [this message]
2026-02-25 15:13 ` Hannes Duerr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0fec8ec2-232f-4a4a-b9d7-bd9deb484045@proxmox.com \
--to=h.duerr@proxmox.com \
--cc=alwin@antreich.com \
--cc=c.heiss@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox