Changes between Version 2 and Version 3 of Developer/Projects/Open/Paravirtualization


Ignore:
Timestamp:
Feb 11, 2012, 2:08:01 AM (8 years ago)
Author:
Julien Delange
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Projects/Open/Paravirtualization

    v2 v3  
    66
    77
    8 Credit: Boost C++'s Google SoC page for the inspiration for the template entry.
     8'''Status:''' New features to be designed. A previous GSOC project started to investigate this topic. See [wiki:GSoC/2011 RTEMSSummerOfCode2011]
    99
    10 '''Status:''' Previous GSOC project started to investigate the topic. See [wiki:GSoC/2011 RTEMSSummerOfCode2011]
     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 also tailor an existing hypervisor to execute RTEMS instances in several partitions.
    1111
    12 '''Introduction:''' The overall project consist in adapting RTEMS to be executed on top of an hypervisor so that we can run RTEMS instance on a partitioned kernel (such as ARINC653-related isolation layers like PikeOS, VxWorks, etc...). To do so, it is necessary to define an API to run RTEMS as a guest operating system and also tailor an existing hypervisor to execute RTEMS instances in several partitions.
    13 
    14 '''Goal:'''
     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
    1513
    1614'''Requirements:''' low-level development, intel/sparc instructions, kernel design