Bringing this conversation back to something resembling 'on track'.
So - I was thinking...
QEMU on X86 can emulate X86 and ARM systems.
https://en.wikipedia.org/wiki/QEMU#ARM
"
ARM QEMU emulates the
ARMv7 instruction set (and down to ARMv5TEJ) with NEON extension.
[23] It emulates full systems like Integrator/CP board, Versatile baseboard, RealView Emulation baseboard, XScale-based PDAs, Palm Tungsten|E PDA,
Nokia N800 and
Nokia N810 Internet tablets etc. QEMU also powers the Android emulator which is part of the
Android SDK (most current Android implementations are ARM based). Starting from version 2.0.0 of their Bada SDK, Samsung has chosen QEMU to help development on emulated 'Wave' devices.
In 1.5.0 and 1.6.0 Samsung
Exynos 4210 (dual-core Cortex a9) and Versatile Express
ARM Cortex-A9 ARM Cortex-A15 are emulated. In 1.6.0, the 32-bit instructions of the ARMv8 (AARCH64) architecture are emulated, but 64-bit instructions are unsupported."
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Virtual_ARM_Linux_environment
So, would the QEMU on ARM that allows us to emulate X86 also be able to emulate 'other' ARM platforms? I'm betting it isn't going to be that simple, but is that the right path to be pursuing? Once there, would a Pyra OS running inside of a QEMU inside of a PyraOS be possible? Would Android running inside of a QEMU inside of a PyraOS host be possible? Is there a shorter path to get there?
An open source Android:
https://source.android.com/
What is the shortest path to being able to have multiple distinct Android VM instances running in switchable background/foreground mode under the Debian host OS on the ARM SoC in the Pyra?