Changes between Version 3 and Version 4 of Developer/Projects/Open/Paravirtualization
- Timestamp:
- 02/11/12 02:08:32 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Developer/Projects/Open/Paravirtualization
v3 v4 8 8 '''Status:''' New features to be designed. A previous GSOC project started to investigate this topic. See [wiki:GSoC/2011 RTEMSSummerOfCode2011] 9 9 10 '''Introduction:''' The overall project consists in adapting RTEMS to be executed on top of an hypervisor so that we can run RTEMS instances on a partitioned kernel (such as ARINC653-related isolation layers like PikeOS, VxWorks, etc...). To do so, it is necessary to (1) define a architecture-agnostic API to run RTEMS as a guest operating system and alsotailor an existing hypervisor to execute RTEMS instances in several partitions.10 '''Introduction:''' The overall project consists in adapting RTEMS to be executed on top of an hypervisor so that we can run RTEMS instances on a partitioned kernel (such as ARINC653-related isolation layers like PikeOS, VxWorks, etc...). To do so, it is necessary to (1) define a architecture-agnostic API to run RTEMS as a guest operating system and (2) tailor an existing hypervisor to execute RTEMS instances in several partitions. 11 11 12 12 '''Goal:''' make RTEMS compliant with partitioned kernel/isolation layer and make a proof-of-concept by collocating several RTEMS instances on top of an existing FOSS separation kernel