This method of compiling for armel (e.g. ARMv5, earlier, and some ARMv6) which uses pbuilder in an ARM HardFloat VM is not recommended as it is extremly slow (because of running in a emulated VM, not because of using pbuilder), but is included for completeness.
Create an UEFI (newish) ARM Hard Float (32-bit) virtual machine for Libvirt/KVM using automated image build using Packer.
Create a non-EFI (old school) ARM Hard Float virtual machine for Libvirt/KVM using packer to automate a repeatable process. The resulting image is meant to be used along with subsequent Packer provisioning to create a Libvirt base image, not be be used directly (although you can).
Create a non-EFI (old school) ARM Hard Float virtual machine for Libvirt/KVM using a traditional interactive Debian install.
These are some updated personal notes about setting up the Windows side of a nice combined Windows and Linux productivity and development environment in Virtual Machine running under Libvirt Qemu/KVM (that is with Linux as the host OS). It uses open source software combined with some key proprietary pieces on a single machine. It is important to note this environment is geared to those who are used to the Linux ecosystem and also want to use or try the new hybrid model.
The cross-compilation toolchains builtin to most
modern Linux distributions do not support older versions of GCC. For old kernels (and other software) that require GCC4 or lower for building, this poses a challenge. One either needs to build a cross-compilation toolchain or use virtualization. This article describes setting up a virtual ARM environment for doing armel (ARMv5) compilation using docker containers.
A guide to configuring an OVH VPS (Virtual Private Server) with CentOS 7