Xen Project Forms Safety Committee, Enlisting AMD, EPAM, and Renesas to Pursue Formal Certification for Its Open Source Hypervisor
The Linux Foundation-hosted Xen Project launched a Safety Committee with AMD, EPAM, and Renesas as founding contributors, aiming to bring formal functional-safety certification to the open source hypervisor for automotive, avionics, and robotics use.
Overview
The Xen Project, the open source virtualization platform hosted by the Linux Foundation, has formed a Safety Committee dedicated to bringing formal functional-safety certification to its hypervisor, according to a Linux Foundation press release. AMD, EPAM, and Renesas are the committee’s founding contributors, and the move is aimed at expanding Xen’s role in automotive, industrial automation, avionics, and robotics systems where software failures can carry safety consequences.
As The Register reports, the initiative “is not an admission of security woes, but a push to ensure the hypervisor complies with formal safety standards like IEC-61508, which defines the processes and practices used in software that runs in devices and settings that could conceivably harm humans.”
What We Know
- The Xen Safety Committee is described by the Linux Foundation as “a collaborative initiative for developing and maintaining shared engineering artifacts that support functional safety activities and expand Xen’s role across automotive, industrial automation, avionics, robotics, and other safety-critical systems,” according to the Linux Foundation.
- Beyond maintaining Xen’s source code, the committee will collaboratively develop and maintain engineering artifacts meant to support organizations’ downstream functional safety certification, per the Linux Foundation.
- Founding contributors AMD, EPAM, and Renesas have already developed “an extensive set of software safety requirements, architecture specifications, MISRA-related engineering, DFMEA analysis, testing frameworks, tooling, code coverage, and process documentation that will serve as the initiative’s initial foundation,” the Linux Foundation said. The Register confirms AMD, EPAM, and Renesas as the three founding contributors.
- The project also created Premier Plus, a new membership tier for organizations pursuing functional safety certification, according to both the Linux Foundation and The Register.
- The initiative builds on a lifecycle change made earlier this year: in 2026 the project extended support for Xen releases to five years, made up of three years of regular support followed by two additional years of security-only support, the Linux Foundation said.
- “Safety engineering has traditionally required every organization to recreate much of the same foundational work. We believe open source can change that,” said Cody Zuschlag, Community Manager at Xen Project, according to The Register. “By maintaining shared engineering evidence alongside the software itself, the Xen community can reduce duplicated effort, accelerate certification programs, and make functional safety more practical for industries building the next generation of software-defined systems.”
- “AMD is a pioneer of functional safety certifications for open source software,” said Christopher Hatch, of AMD’s Product Applications Engineering, Embedded Software Marketing group, per the Linux Foundation.
- “Achieving baseline functional safety certification for Xen is a critical milestone,” said Artem Mygaiev, Technology Solutions Director at EPAM, according to the Linux Foundation.
- “As a founding contributor to the Xen Project’s Safety Initiative, Renesas is proud to help establish a collaborative framework,” said Aish Dubey, Vice President at Renesas Electronics, per the Linux Foundation.
- “Systems with safety considerations need a trusted hypervisor,” said Kate Stewart, Vice President of Dependable Embedded Systems at The Linux Foundation, according to the Linux Foundation.
- “Xen is a critical component of the AGL SoDeV Software Defined Vehicle platform,” said Dan Cauchy, Executive Director of Automotive Grade Linux, according to the Linux Foundation.
- The Register writes that Xen has “in recent years emphasized work to make its code more suitable to run in embedded workloads and devices like cars,” noting that virtualizing workloads in a vehicle means an isolated, glitchy application “can’t impact performance of a critical application like collision avoidance.”
- The Register reports it understands that Xen Project members believe more device categories, including robots, will need similar workload isolation, and that the project wants Xen to become the hypervisor of choice in those scenarios as well, according to The Register.
- The Register reports that Boeing recently joined the Xen Project, and that the outlet understands interest in Xen’s safety work was one reason the aerospace company signed up.
- The safety push follows closely on an update to Xen’s flagship hypervisor delivered in early August, which, per The Register, “added support for AMD Zen 5 Bus Lock Threshold, which makes it easier to ensure one guest VM doesn’t make it harder for other workloads to access CPU resources,” along with improved Arm support and continued progress toward a fully functional RISC-V release.
What We Don’t Know
Neither the Linux Foundation nor The Register specified a timeline for when Xen might achieve baseline functional safety certification under IEC-61508 or comparable standards, nor how many additional companies may join the Safety Committee or the Premier Plus tier beyond the three founding contributors.
Analysis
The formation of a dedicated safety committee reflects a broader pattern of Linux Foundation-hosted infrastructure projects formalizing governance structures around specific technical guarantees — in this case, functional safety rather than security. By pairing a chipmaker constituency (AMD and Renesas) with a systems integrator (EPAM) as founding contributors, and creating a paid membership tier tied specifically to certification work, the Xen Project is positioning itself to compete for adoption in automotive and industrial markets where formal safety compliance, not just open source licensing terms, determines whether a hypervisor can be deployed at all.