Thanks for you reply Fabian.
I've gotten my iPXE deployment enviroment set up and I've been playing around
with scenarios. I didn't yet end up taking the Kiwi route as you previously mentioned
since I'm able to get to edk2 UEFI iPXE on my Pis through the network.
So essentially I have the yast iso for arm and x86. What I'm struggling with is a
unattended installation. I have tried some autoyast2 configurations borrowing ideas from
repo in terms of patterns and roles, and pointing install at my nearest OSS tumbleweed
mirror. Even though Jing is coming back clean my installs are failing.
Before going to deep in that topic is this really the best avenue? All I'm trying to
achieve is a unattended installation of Kubic specifying a drive to be installed on and
giving a SSH key.
Autoyast seems way to over kill for this but there's only yast installations being
provided for aarch64 and x86.
Fedora Core-OS has something like the installer that can be called with a initial
ignition. I think I'm looking for something like that. A live kubic system that
installs to a specific drive.
One more thing: I'm assuming ignition can be specified with a net url such as a http
server like most over platforms can? Is that right?
On Mar 4 2021, at 8:29 am, Fabian Vogt <fvogt(a)suse.de> wrote:
Am Mittwoch, 3. März 2021, 16:18:42 CET schrieb Anthony J Rabbito:
I'm inquiring for some methods of PXE booting on a mixed architecture environment
between Raspberry Pis and X86 platforms. It seems like my best, and quickest path to
success would be something like this.
Compile aarch64 grub
No need to compile that yourself. For EFI, you can use the prebuilt grub.efi
from grub2-arm64-efi, combined with shim.efi for secure boot, if you need that.
and host on a tftp server along with x86 grub and
chain load based on MAC addresses
AFAIK there are various DHCP options which
indicate the arch, so you might not
have to use the MAC prefix there.
Use a custom ipxe file to either boot from hard
drive or do a fresh install
*possibly* use ignition.url as a kernel command line for combustion/ignition
configuration on the hosts
Note that initrd networking on Tumbleweed is currently broken:
Though there's a few short falls I see here.
One being RBrown has a experimental self-install image for x86-64 that installs to the
first hard drive it sees. That is almost perfect for my use-case but it would be best if
we can specify a drive by UUID (especially on storage-nodes).
Here's the kiwi
documentation for deploying images over PXE:
You could file a feature request for kiwi to accept a device ID (and possibly
other options) from the kernel cmdline.
I have been successful on getting iPXE to work on
Raspberry Pi4s though I'm unsure yet how I can instruct the existing Pi image to
install from iPXE.
Does anyone have a working implementation of PXE booting from x86, and arm to install to
disk without YaST and the use of using physical medium for combustion/igntion?
Does anyone have any thoughts to share?