You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Organizing of the Domain-interaction Hypervisor project, with inititial focus on the full-day AMM Workshop.

Next Meeting

Tuesday, March 6, 10:00 AM CET

Agenda:

Minutes & other info

AMM Workshop Agenda Topics ideas

  • Requirements gathering
    • Requests from HV vendors for OEMs/adopters/customers/etc to clarify technical requirements,
      e.g. on particular driver, performance, reliability, safety.  
      • Central device driver management?
        • i.e. HV+BSP supporting hardware register access arbitration.
        • ...?
        • Even possible without this?  What would be design patterns to use if the HV is not giving the hardware virtualization you need.
      • BSPs available vs. needed
      • Unikernel support
        • e.g. tested/demonstrated
        • any special matching needed between HV and unikernel (para-virtualization) – likely not...
    • (Maybe in particular, how is reliability & safety quantified?)
      Boils down to: Several safety related parts brought together - how to design (and evaluate) the total system. 
    • Footprint
      • Memory usage
      • # Lines of code (auditing/reliability/trust...)
  • Training / informative materials?
    • Vendor-independent
    • From users/system integrator's perspective.
    • What can be done today, what can't be done today
    • Consequences of para virt or hardware support for virtualization, and related BSP design
    • Connection between "management/sales" slides and the very detailed HV documentation.  Knowledge required in the gap here.
  • Cross-domain architectures, examples, recommendations
    • (repeated from above) Boils down to: Several safety related parts brought together - how to design (and evaluate) the total system.
    • (repeated from above) Consequences of para virt or hardware support for virtualization, and related BSP design
      • Is design even possible without virtualized hardware?  Design patterns to coordinate access if the HV is not giving the hardware virtualization you need?
    • 12 factors for service-oriented platforms.
      continue here next meeting:  
  • Required technology demonstrations
  • Market/Technology survey
  • Requirements survey - Questionnaire (to OEMs)
    • Results could be statistics/anonymized if needed.
    • Start work on this questions list.
  • Feature evaluation
    • Compare features
      • Separate BSPs - paravirt or hardware virt support?
    • ... or simply list "what types of features can a Hypervisor have"
    • Comparing types of HV / key characteristics?
  • Graphics/GPU Sharing (in relation to GSHA project)
    • What things are hardware dependent?
    • How to share graphics buffers?
  • Health/Debugging/Analysis/Logging (in relation to SHDA project
  • Audio...
  • How to minimize impact on the development process when using HVs 
  • Glossary/terms - does everyone have the same understanding of terms?











  • No labels