ACRN v2.0, released in June 2020, introduced a hybrid approach for industrial IoT and edge systems: ordinary virtual machines could share resources while workloads needing stronger isolation could run with resources partitioned. The release also highlighted real-time VM support, graphics and device virtualization, shared-memory communication, and container orchestration. In July 2020, TÜV SÜD Rail GmbH approved ACRN’s functional-safety concept, but the announcement did not establish that final IEC 61508 certification had been completed.
What is ACRN v2.0?
ACRN is an open-source, Type 1 reference hypervisor stack for consolidating multiple operating-system workloads on embedded hardware. A Type 1 hypervisor runs directly on the machine’s hardware rather than inside a host operating system. ACRN’s architecture divides a system into functional domains and uses an ACRN Device Model to emulate virtual devices and mediate I/O.
As an Amazon Associate I earn from qualifying purchases.
Project ACRN describes the software as a lightweight platform intended for embedded development, including systems with real-time and safety-critical requirements. The project launched in 2018; v2.0 followed on 24 June 2020. Its central architectural change was hybrid mode, which combines resource sharing with partitioning rather than requiring a deployment to choose only one model.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesHow hybrid mode works
In a shared-resource arrangement, virtual machines can use common system resources. In a partitioned arrangement, resources can be assigned to a workload that needs stronger separation from other activity. Hybrid mode lets a system use sharing for ordinary workloads and partitioning for selected mixed-criticality workloads on the same platform. The exact isolation and timing properties depend on the hardware, configuration, device assignments, and workload; the release announcement alone does not establish guarantees for a particular deployment.
#1 Best Overall
What capabilities did v2.0 add or highlight?
The 24 June 2020 release article described features spanning VM lifecycle, device access, real-time support, inter-VM communication, and orchestration. They are capabilities of the release, not a guarantee that every combination of hardware and guest operating system is supported.
| Area | v2.0 capability | Why it matters |
|---|---|---|
| VM lifecycle and safety | Pre-launched Safety VM support; post-launched VM support through OVMF | Supports different boot and launch arrangements for workloads with distinct requirements. |
| Real-time workloads | Post-launched real-time VM support and real-time performance optimizations | Provides a path for real-time workloads alongside other VMs; application-specific latency and scheduling needs still need validation. |
| CPU and device access | CPU sharing and SR-IOV support | Allows resource-sharing and virtualized-device approaches, subject to hardware and device support. |
| Graphics | Graphics passthrough and shared graphics | Offers alternative ways to make graphics resources available to virtual machines. |
| Inter-VM communication | Shared-memory communication | Allows VMs to exchange data through shared memory. |
| Boot and configuration | GRUB bootloader and configuration-tool support | Extends boot and system-configuration options. |
| Containers and orchestration | Kata Containers support; VM orchestration through tools such as OpenStack; Docker or Kubernetes orchestration for Kata Containers | Connects VM-based isolation and container-oriented deployment workflows. |
How should the functional-safety announcement be understood?
What TÜV SÜD approved
On 21 July 2020, the Linux Foundation announced that TÜV SÜD Rail GmbH had approved ACRN’s functional-safety concept, design, and management process. The announcement quoted the concept letter as stating: “ACRN Hypervisor is able to fulfill the requirements in accordance with SIL 3 of the IEC 61508 standard.” That is a statement about the concept’s ability to fulfill requirements, alongside concept approval; it should not be read as proof that a particular ACRN-based product or system had obtained final certification.
Rank #2
What the announcement did not establish
The same announcement said ACRN was on track for final certification by the end of 2020. The available announcement does not verify whether that later certification was completed, what its scope would have covered, or whether it applied to a specific product, configuration, or deployment. For a safety-related project, buyers and engineering teams should verify the current certification status and scope, the evidence for the exact software and hardware configuration, and the applicable development and assessment process with the relevant vendors or assessors.
Can ACRN run real-time and non-real-time workloads together?
That was one of the use cases v2.0 was designed to address. Hybrid mode can combine shared resources for ordinary VMs with partitioning for selected workloads, while the release included support for post-launched real-time VMs and real-time performance optimizations. This makes ACRN relevant to mixed-criticality edge systems in which, for example, a general-purpose operating system and a time-sensitive workload need to coexist.
“Real-time” does not by itself specify a deadline, worst-case latency, or scheduling guarantee. Whether a system is suitable depends on the application’s timing requirements and the full configuration, including processor, devices, firmware, workload, and hypervisor settings. Validate those requirements on the intended platform rather than treating a feature-list entry as a measured guarantee.
Which operating systems and orchestration tools work with ACRN?
Guest operating systems
Project materials describe ACRN guests including Linux, Windows, Android, and real-time operating systems. The v2.0 release article specifically named Windows 10, Ubuntu, Android, and VxWorks. Those examples indicate the breadth of guests discussed for the release; they do not establish that every edition, version, or configuration is currently supported on every ACRN-compatible platform.
Orchestration
The release highlighted VM orchestration through tools such as OpenStack. For Kata Containers, it described orchestration with Docker or Kubernetes. These are distinct deployment paths: OpenStack can manage VMs, while Kata Containers uses lightweight VMs to provide container isolation and can be orchestrated through container tooling. Confirm compatibility among the ACRN version, orchestration stack, host platform, and guest images before relying on a specific workflow.
Is ACRN commercially supported?
ACRN itself is an open-source project and reference hypervisor. Project ACRN says TTTech Industrial made ACRN 2.0 available in Nerve Blue, a commercial, fully supported industrial edge-computing platform running on Intel processors. TTTech described that integration as targeting functional safety, real-time processing, and flexible resource sharing. This is an example of commercial product support built around ACRN; it is not evidence that the community project alone provides a vendor support contract.
Best Value
Processor compatibility is version- and platform-specific. ACRN documentation later referenced Intel Atom x6000E, Pentium, Celeron N/J, and 11th Gen Core families in its v2.2 context. That information is not a current compatibility guarantee for v2.0 or for present-day systems; check current ACRN and vendor documentation for the exact processor, firmware, and release combination.
What does ACRN’s code-size comparison mean?
A 2018 Project ACRN overview reported approximately 27,000 lines of code for ACRN, compared with fewer than 156,000 lines for datacenter-centric hypervisors. This is the project’s own comparison, not an independently audited measurement or a benchmark of speed, reliability, security, or safety. Code size alone does not establish that a hypervisor is easier to certify or better suited to a particular device.
When is ACRN v2.0 a relevant option?
ACRN v2.0 is most relevant to teams evaluating consolidation for embedded, industrial IoT, or edge systems that may need to mix ordinary VMs, real-time workloads, and more isolated domains. A practical evaluation should establish:
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Whether the target processor, firmware, devices, and graphics hardware are supported by the ACRN release being considered.
- Whether sharing, partitioning, passthrough, SR-IOV, or shared graphics matches the system’s isolation and device-access needs.
- What timing and latency requirements apply, and how they will be validated on the actual configuration.
- Which guest operating systems and orchestration tools are supported for the exact versions in the proposed deployment.
- What safety evidence and certification scope are required, and whether those apply to the complete product configuration.
- Whether project-level resources are sufficient or a commercially supported distribution such as Nerve Blue is required.
ACRN v2.0’s significance is its attempt to bring sharing and partitioning into one embedded hypervisor platform, with a functional-safety concept approval announced in 2020. That historical milestone is useful context, but it does not replace current compatibility checks or product-specific safety and performance evidence.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
