ELinOS as PikeOS Guest OS

Among many other guest operating systems, the real-time operating system and hypervisor PikeOS can run the embedded Linux ELinOS as a guest OS. This enables real-time capable target devices that also benefit from typical Linux features such as graphical support, large amount of network services and protocols. ELinOS as a guest system also serves as a basis for reusable code and binaries and thus has the potential to save development time.

ELinOS Guest Operating System on top of PikeOS ROTS & HYpervisor

ELinOS on PikeOS

ELinOS can run as guest operating system in a partition on top of PikeOS, SYSGO's real-time separation-kernel hypervisor. A partition is a separated environment in which different Application Programming Interfaces (API), runtime environments or guest OSs can reside. Partitions (and software within the partitions) are strictly separated per default. Since guest OSs are executed inside partitions, it is possible to run uncertified (unsecure) guest OSs in parallel with certified (critical) applications in other partitions.

An application suite provides the tools and materials needed to develop software using the respective API, runtime environment or guest operating system within a PikeOS partition. The resulting ELinOS partition image can be integrated into PikeOS and executed, analyzed and debugged.

Setting up ELinOS as Guest OS

ELinOS can run as a guest operating system partition on top of PikeOS. This setup enables efficient mixed-criticality systems: ELinOS executes alongside certified partitions such as ARINC 653 or POSIX, without impacting their certification context.

PikeOS supports two modes of virtualization:

  • Para-Virtualization: Requires kernel modifications (mainly around memory management) but runs on all PikeOS-supported architectures with no hardware virtualization support
  • Hardware Virtualization: Requires no guest OS modification, but requires underlying hardware support and can be slightly more complex to configure—however, it delivers near-native performance for system calls, exceptions, and interrupts


Integration Notes

  • For para-virtualized ELinOS, patch the Linux kernel accordingly
  • For hardware-virtualized ELinOS, minor tweaks—typically to the device tree—enable compatibility
  • No modifications are required beyond that, enabling any compatible Linux distribution to run as a guest, provided it targets a supported architecture

Board Support Packages (BSPs)

To run directly on hardware, ELinOS uses its own BSPs to interface with the hardware (bootloader, kernel config, drivers, device tree, etc.). However, when ELinOS runs as a guest OS on top of PikeOS, the integrated “PikeOS BSP” is used for system configuration. Like this, ELinOS knows it is running as guest OS. 


Important

  • PikeOS handles the hardware directly, via its own Board Support Packages
  • ELinOS, as a guest OS, sees a virtualized hardware environment defined by PikeOS (memory ranges, devices, virtual IRQs, etc.)
  • The only ELinOS-specific configuration needed is kernel adaptation (e.g., for para-virtualization) and possibly device tree tweaking
ELinOS BSP List

ELinOS BSP List

Board Support Packages

PikeOS BSP List

PikeOS BSP List

Board Support Packages

Customer Benefits

Check

Fast Deployment & Reduced Rime-to-Market

ELinOS integrates seamlessly into PikeOS partitions, allowing rapid system setup and reducing development cycle time

Check

Strict Isolation and Partition Safety

PikeOS enforces spatial and temporal separation between partitions, so ELinOS guests cannot affect higher-criticality applications—even if ELinOS crashes, it stays isolated

Check

Flexibility in System Architecture

ELinOS runs side-by-side with POSIX APIs, ARINC 653 partitions, or certified PikeOS native apps—enabling hybrid designs in one platform

Check

Optimized Virtualization Performance

With hardware virtualization, ELinOS achieves near-native performance, especially for system calls and interrupt handling—benchmarks show minimal overhead vs. bare-metal execution

Arrow

No BSP required for Guest Mode

As a PikeOS guest, ELinOS requires no dedicated BSP. It runs independently of the physical hardware configuration, reducing integration complexity

Check

Unified IDE Experience

CODEO provides a common toolchain for both PikeOS and ELinOS development—including configuration, debugging, and image management—with a consistent UI and workflow

CODEO Product Page

Need more Information?

Tell us about your project and your needs.
 

Contact us