public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Alwin Antreich" <alwin@antreich.com>
To: "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, 18 Feb 2026 19:23:58 +0000	[thread overview]
Message-ID: <e1208d839381447803b8d919548ff42038469837@antreich.com> (raw)
In-Reply-To: <20260204121025.630269-1-c.heiss@proxmox.com>

Hi Christoph,

just some general comments. :)


February 4, 2026 at 1:09 PM, "Christoph Heiss" <c.heiss@proxmox.com mailto:c.heiss@proxmox.com?to=%22Christoph%20Heiss%22%20%3Cc.heiss%40proxmox.com%3E > wrote:


> 
> Adds a new flag to the `prepare-iso` subcommand; `--pxe`.
> 
> When specified, instead of just creating the usual
> auto-installation-capable ISO, additionally `vmlinuz` and `initrd.img`
> will be created, which can be used in combination with the ISO to
> PXE-boot our installer.
> 
> The (generated) iPXE configuration gives a good overlook how these files
> must be used, especially what kernel commandline flags must be
> additionally given.
> 
> Tl;dr is: The `vmlinuz` is directly booted and given the `initrd.img` as
> ramdisk, the ISO file must be overlaid as `/proxmox.iso`. This will
> cause init to mount & load the rest of the installer from there.
> 
> The flag also takes an optional argument specifying the specific PXE
> bootloader to generate a configuration file for.
> 
> Currently only iPXE is supported for configuration generation.
> 
> Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
> ---
> 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 :/ ). 

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

      parent reply	other threads:[~2026-02-18 19:31 UTC|newest]

Thread overview: 3+ 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 [this message]

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=e1208d839381447803b8d919548ff42038469837@antreich.com \
    --to=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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal