Hypervisors in the Vehicle: a Standards-Based Approach to Virtualization
Total Page:16
File Type:pdf, Size:1020Kb
Hypervisors in the vehicle: A standards-based approach to virtualization A report based on the webinar by Automotive World and GENIVI Alliance. The webinar which was broadcast in February of ! ! is still available for download " see #$%. It however had some poor audio &uality in some parts. A better recordin' is now available at #$% but some may still prefer to 'et this information in written form. The document is not an e(act transcript of the webinar) but it is close. The content and messa'e is the same, and the information is presented here to'ether with the correspondin' presentation slides from the webinar) with the followin' adjustments: , -ommon spo.en e(pressions have been e(chan'ed for more typical written lan'ua'e to reach more typical written &uality. , /inor clarifications and some lost details have been added. , A few chapters are e(tended and elaborate on details that did not 0t within the time of the webinar , For the 1&A session, more thou'htful and complete answers to 'iven &uestions can be 'iven, now that there is time to formulate the answers. Also) the section presented by Tero 3alminen from 4pen3yner'y has a 'ood &uality audio in the recordin') and is not included in te(t form in this document. The 0rst part of the presentation was done by Gunnar Andersson 5GENIVI Technical 6ead7) who is also the author of this text. We promised to address a &uestion in this webinar : 8Is there a need for a more standards-based approach for deployin' hypervisors in the vehicle?: , to ensure that automotive requirements are met, , to reduce risk and concerns amon' adopters of virtualization) , to promote portability, , and to minimize system integration effort. This report includes what we have already done toward this end, and leave the &uestion a open for you to thin. about. After hearin'=readin' this and the results that we published in a 0rst version, if at the end of this you believe the answer is >es, then we are really loo.in' forward to your support and participation. If anyone thin.s no, then we loo. forward to your thou'hts on this as well. Today’s Outline First, to e(plain how and why GENIVI is addressin' these &uestions I will 'ive a little overview of GENIVI, how we thin. and an update on what GENIVI is today, because some of you might still need that. Then we will hear from 4pen3yner'y to hear their reflections on virtualization and reasons for companies to support this standards effort . The specification we are highlightin' today was announced in its 0rst release in combination with the -ES ! ! conference. I'd like to explain how we wor. in the associated project that produces the specification. Then a brief discussion of why virtualization is needed in the 0rst place. Often presentation will 'o into a now relatively tired ramble about how the industry is chan'in') the need for consolidation of ECAs, and mixed criticality. This is a messa'e we assume the audience has heard many times over. The idea of 8why virtualization: is rather to note that itis a &uestion that could be analyzed in detail, and mention some separate wor. tryin' to answer that &uestion in a serious way. Then movin' on to -hallen'es and solutions. This is where we intend to ma.e the core ar'ument for how standards might ma.e our situation better. What are the issues today, and how could we address them to'ether9 Then) if you haven@t yet loo.ed at the specification itself) there is a basic e(planation of content here. Why is it called a platform and what is a platform9 This might be obvious, but definition of terms is a core activity in all our projects, and since there is likely a mixed audience, if you 0rst need to understand what virtualization is, some of this presentation of the different parts of a virtualized system might help. What about VIRTIO? We have a clear direction and statement to ma.e there. Primarily, the rationale for an automotive specification) that complements VIRTIO. Further discussion of the approach) i.e. why and how to write a new specification. Why is a new specification not unnecessary or overlappin' wor., and how do we want to structure this wor.9 Further deep dive into the content, assumin' we have time left, and a Future outloo.. At the end, time for some 1&A. Slide: Comic 3ince this is a heavy technical subject, the presentation was started on a li'hter note with a comic showin' two individuals, seemin'ly from the stone-a'e, each wor.in' on half of a wheel . The idea is proposed by one of them that that collaboration might be a 'ood idea9 The comic strip was used in the webinar presentation with permission from its copyright holder) and it can be viewed in the recordin'. Honestly, there have been times when I loo.ed at the automotive industry and thou'ht about somethin' like those confused ancient wheel,buildin' people. I ima'ine them bein' oblivious to each other@s similar activities before they ta.e interest in the commonality of the needs and have the epiphany that collaboration might help! Our industry sometimes seem to fail to understand that the really interestin' wor. begins when everyone already has the basic fundamental buildin' bloc.s in place, like the wheel in the analo'y. 6et@s therefore put the virtualization wor. in context with a short review of the GENIVI Alliance of today. GENIVI now has over $! years of experience in supportin' standardization and shared software solutions in our automotive industry, and this is the .ey: collaboration. We still believe that collaboration) on multiple different levels has the potential to ma.e the automotive industry much more effective, and it is fran.ly likely to be a necessity, to adequately address the future complexity challen'es. >ou could therefore say that collaboration was a survival skill bac. in the stone a'e, and is equally in today's modern business environment. Over $! years now, GENIVI has wor.ed with this idea of creatin' shared specification and software, 'ettin' rid of waste, avoidin' reinventin' of the same software over and over) avoidin' the wasted effort that come from integration problems between software, and... just 'eneral uncertainty. This uncertainty 'oes beyond technical matters " it can show itself as distrust and constant friction in the business and contract relationships. This is why the industry conversations we seek to facilitate can have profound effects. Inefficiency prevents the industry from havin' the time and resources to solve the really challen'in' problems. Gust pic.in' on one, does anyone here believe that our industry is current successfully solvin' the future cybersecurity challen'e? If li.e me you thin. the answer is no) then there are two ways to wor. on that+ We could address the security &uestion directly and become more effective in that wor., and GENIVI wor.s on that too. Hut you can also realize that there is a lot of effort spent on unnecessary basic development problems in other areas. If the industry 0(es that throu'h effective collaboration) it will free up resources to instead wor. on e.g. 1uality. 3afety. Innovation. Will every one of you, after this webinar and report put in small part of your resources towards the industry 'oal to achieve a virtualization standard9 /any of our projects use this I,level model about the history and future of in,car electrical architectures. The picture is used with permission from Hosch who is the copyright holder. NOTE It is li.ely that you could 'et the right to use this picture throu'h other means, but in this document the open,source license of the document does not include this picture. The industry is currently spea.in' a lot about consolidation and domain fusion. This includes creatin' lar'e central high performance computer5s) to process many different tasks, and that is one place where virtualization is likely to be e(pected. I believe that very &uic.ly followin' on the domain fusion came a .ind of push,bac. and the realization that the physical reality of the car is still there. Physical laws of the universe can@t be bro.enJ such as it matters where you locate an antenna if you want wireless communication and it matters how lon' the cable to that antenna must be. For some other functions, initial processin' might be best done NEAB the sensor that measured the data. All of those physical realities of the car balance a'ainst the consolidation desires, and so the Zone-oriented architecture approach came up. This see.s to optimize the in,car electrical architecture to the ma(imum. It can strike the right balance between distributed systems and consolidated systems. The industry is at this Lth level today and systems are increasin'ly connected) but it is nothin' compared to the vision of the Ith level of Vehicle -loud -omputin'. 3ince it@s a future this is a va'ue idea at best, but in a cloud,driven architecture we are not only considerin' cars to be more heavily connected) to each other and to infrastructure but certain parts of the car may become a ?exible computin' unit on wheels. Gust like servers in the cloud come and 'o and just like the software runnin' on those servers is constantly deployed and redeployed, we might see similar ?exibility in the vehicles themselves.