Lesson plan

EmbeddedXEN

EmbeddedXEN is a Type-1 (bare metal) hypervisor based on the open source XEN hypervisor from Citrix. EmbeddedXEN results from several Years of Research in the field of ARM-based CPUs and hypervisor technology based on XEN. The overall architecture has been revisited in order to support the hardware diversity of ARM CPUs platforms and provide an excellent framework to deal with a native OS and a third-party OS cross-compiled from a different ARM CPU. EmbeddedXEN provide a virtualized hardware interface to the third-party OS. EmbeddedXEN has been initiated and is under current development at the Reconfigurable Embedded Digital Systems (REDS) Institute of HEIG-VD, Switzerland. EmbeddedXEN has been released as an open source project on SourceForge. From March 2020, a novel framework called SOO (Smart Object Oriented) has been released on Gitlab. It followed the evolution with deep changes from EmbeddedXEN (also called Embx) from many Years. EmbeddedXEN is considered as development basis at the origin of SOO.

Back to article

Article summary

EmbeddedXEN is a Type-1 (bare metal) hypervisor based on the open source XEN hypervisor from Citrix. EmbeddedXEN results from several Years of Research in the field of ARM-based CPUs and hypervisor technology based on XEN. The overall architecture has been revisited in order to support the hardware diversity of ARM CPUs platforms and provide an excellent framework to deal with a native OS and a third-party OS cross-compiled from a different ARM CPU. EmbeddedXEN provide a virtualized hardware interface to the third-party OS. EmbeddedXEN has been initiated and is under current development at the Reconfigurable Embedded Digital Systems (REDS) Institute of HEIG-VD, Switzerland. EmbeddedXEN has been released as an open source project on SourceForge. From March 2020, a novel framework called SOO (Smart Object Oriented) has been released on Gitlab. It followed the evolution with deep changes from EmbeddedXEN (also called Embx) from many Years. EmbeddedXEN is considered as development basis at the origin of SOO.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.