![]() have the guest network boot, which means direct kernel booting needs to be used. ![]() That also means there is nothing to pick the kernel inside the guest at boot nor something which can e.g. The first pitfall is that there is no standard bootloader or boot firmware available in Debian to boot on the "virt" machine emulated by qemu (I didn't want to use an emulation of a real machine). As such running armhf VMs on them to act as build slaves seems a good choice, but setting that up is a bit more involved than it might appear. ThunderX based servers which can only run 64 bit code). On the 64 bit ARM side, we're running on Gigabyte MP30-AR1 based servers which can run 32 bit arm code (As opposed to e.g. For 32 bit ARM we've been relying on Calxeda blade servers, however Calxeda unfortunately tanked ages ago and the hardware is starting to show its age (though luckily Debian Stretch does support it properly, so at least the software is still fresh). Luckily with the advent of ARM server systems some years ago building natively for those systems has been a lot less painful than it used to be. And just as Debian does, our OBS system builds on native systems rather than emulators. At Collabora one of the many things we do is build Debian derivatives/overlays for customers on a variety of architectures including 32 bit and 64 bit ARM systems.
0 Comments
Leave a Reply. |