Hello, I have a VIM3-Pro I am evaluating as a pixel streaming thin client for a few hundred crew-stations. My goal is to demonstrate an automated and scalable eMMC Manjaro install solution. Khadas’s documentation on PXE booting a uImage or zImage Kernel from the uBoot environment appears to be a viable option for this use-case.
Before I mess up my board’s eMMC I was wondering if there is a recommended approach for testing a uBoot install. I have experience with booting x86_64 kernel images in QEMU using the PVH entry point, but I have never attempted to to boot kernel images with uBoot in qemu like so:
I realize that the PXE uBoot install has its limitations and there may not be a method for kicking off a script to configure the uBoot environmental variables without a serial connection . The automated install process is less of a concern in this post. When I say scalable install I would like the install to serve hundreds of clients. This may mean manually provisioning each client’s uBoot into a PXE boot state, but from then on I would like to be able to:
Send a Wake on LAN (client begins in powered off state)
I have a little different situation, where the plan is have hundreds of RPi4. The route I am taking is to use a read-only nfsroot with a systemd overlayfs to make a psudo writeable root. Just one image to maintain (or however many copies are needed to handle the load) and I have one RPi4 that can mount the image read-write for updating and configuration modifications. This can even be done on the fly, depending on the changes required.
Overlayfs with nfsroot is an interesting concept for managing a single source of truth. Where I work we try to deploy rootless containers with podman and systemd as much as possible. Our DevOps foo is not at the maturity level where we are comfortable deploying rootless containers with fuse-overlayfs quite yet. I wish you luck on your project. That would be a spectacular feat to scale the configuration of hundreds of RPi4s with a single RPi4 VFS.