13. Virtual Execution Environment¶
A Virtual Execution Environment (VEE) is a multi-sandboxed application environment for resource-constrained embedded devices running on microcontrollers or microprocessors. It allows devices to run multiple and mixed managed code (Java ® compiled binary code, C/C++ compiled binary code, JavaScript code, etc.).
A VEE is always based on a virtual execution engine that executes inside the device operating system as a process or a task, thus creating an isolated environment where code executes as virtual instructions independent from the operating system or the processor instruction set.
The GEISA Virtual Execution Environment is one of two execution environments defined within the GEISA specification. The GEISA Virtual Execution Environment definitions allows platforms which support running applications in a virtual execution environment, rather than a full operating system, to do so in an interoperable way.
VEEs may be implemented on any suitable operating system, including embedded real-time operating systems like Zephyr or FreeRTOS, as well as multi-user operating systems like Linux. Platform implementers may choose to offer both a VEE and an LEE on the same platform, but this it not an obligation.
VEEs rely on managed-code virtual runtime (typically a virtual machine). GEISA VEE MUST support multi-threaded managed C/C++, and MAY support Java ®. Support for other languages (e.g. Kotlin, Lua, Rust, ECMAScript, etc.) may be included in the future, but is not defined or mandated at this time. GEISA’s definition of VEE requires it to support a specific language (C/C++), rather than a specific virtual byte-code (i.e. Java Virtual Machine bytecode or Common Intermediate Language), resulting in VEE only being source code compatible in this version of the GEISA specification.
Warning
Application providers should be careful when using languages other than C/C++ with GEISA VEE environments, as they may not be supported by all VEE toolchains, limiting interoperability across VEE implementations.
When the host operating system is Linux, the VEE SHOULD execute in user space as a process. When the host operating system is an RTOS, such as Zephyr, the VEE SHOULD be executed as a task.
On top of this runtime sits a multi-application kernel that manages the lifecycle, scheduling, and isolation of multiple apps running concurrently. Each application executes inside its own sandbox with strict memory and API boundaries, ensuring strong fault-containment, secure separation of logic, and safe coexistence of third-party or field-updatable applications on the same device.
VEE conformant platforms will provide a consistent: