 supporting paravirtualization is required.

ARM processors are notable in that most of their application class processor designs support a technology called ARM TrustZone, which provides essentially hardware support for one privileged and one unprivileged VM. Normally a minimal Trusted Execution Environment (TEE) OS is run in the Secure World and a native kernel running in the Non-secure World.

Use cases 
Some of the most common use cases for an embedded hypervisor are:

1.	OS independence

Designers of embedded systems may have many hardware drivers and system services which are specific to a target platform.  If support for more than one OS is required on the platform, either concurrently or consecutively using a common hardware design, an embedded hypervisor can greatly simplify the task.   Such drivers and system services can be implemented just once for the virtualized environment; these services are then available to any hosted OS.  This level of abstraction also allows the embedded developer to implement or change a driver or service in either hardware or software at any point, without this being apparent to the hosted OS.

2.	Support for multiple operating systems on a single processor

Typically this is used to run a real-time operating system (RTOS) for low-level real-time functionality (such as the communication stack) while at the same time running a general purpose OS, (GPOS) like Linux or Windows, to support user applications, such as a web browser or calendar.  The objective might be to upgrade an existing design without the added complexity of a second processor, or simply to minimize the bill of materials (BoM).

3.	System security

An embedded hypervisor is able to provide secure encapsulation for any subsystem defined by the developer, so that a compromised subsystem cannot interfere with other subsystems.  For example, an encryption subsystem needs to be strongly shielded from attack to prevent leaking the information the encryption is supposed to protect.  As the embedded hypervisor can encapsulate a subsystem in a VM, it can then enforce the required security policies for communication to and from that subsystem.

4.	System reliability

The encapsulation of a subsystem components into a VM ensures that failure of any subsystem cannot impact other subsystems. This encapsulation keeps faults from propagating from a subsystem in one VM to a subsystem in another VM, improving reliability. This may also allow a subsystem to be automatically shut down and restarted on fault detection. This can be particularly
supporting paravirtualization is required. 

 ARM processors are notable in that most of their lotion course central processing unit designs support a technology call ARM TrustZone, which provides essentially hardware accompaniment for one inside and one unprivileged VM. Normally a minimal Trusted Execution Environment (TEE) OS is run in the Secure World and a native kernel running in the Non - secure World. 

 Use shell 
 Some of the most coarse habit cases for an embedded hypervisor are: 

 1. 	 OS independence 

 Designers of embedded systems may suffer many hardware drivers and system services which are specific to a aim platform.   If support for more than one OS is required on the chopine, either concurrently or consecutively using a coarse hardware design, an embedded hypervisor can greatly simplify the task.    Such driver and system services can be implemented just once for the virtualized environment; these services are then available to any hosted o.   This level of abstraction also allows the embedded developer to implement or change a driver or service in either hardware or software at any point, without this being apparent to the hosted OS. 

 2. 	 documentation for multiple operating systems on a single central processing unit 

 Typically this is use to prevail a real - time operating arrangement (RTOS) for low - level real - time functionality (such as the communication smokestack) while at the same time running a general purpose OS, (GPOS) like Linux or Windows, to defend user applications, such as a web browser or calendar.   The objective might be to promote an existing blueprint without the added complexity of a second processor, or simply to minimize the bill of material (BoM). 

 3. 	 System security 

 An embedded hypervisor is able to provide secure encapsulation for any subsystem defined by the developer, so that a compromised subsystem cannot interfere with early subsystems.   For example, an encryption subsystem needs to be strongly shield from attack to prevent leak the information the encoding is supposed to protect.   As the embedded hypervisor can encapsulate a subsystem in a VM, it can then enforce the command security policies for communication to and from that subsystem. 

 4. 	 organization reliability 

 The encapsulation of a subsystem component into a VM ensures that bankruptcy of any subsystem cannot impact other subsystems. This encapsulation keeps mistake from propagating from a subsystem in one VM to a subsystem in another VM, improving reliability. This may besides allow a subsystem to be automatically shut down and restarted on fault detection. This can be particularly
 suoporting paravirtualizatlon is required.

ATM procevsors zre notacle in that most of their ap'licqtion class processor desigvs supporn a technilogb called ARM TrustZone, wmnch pdlvidzs essentially hsrdware su[port for one [rkvnleged and one unprivileged VM. Normajly a monlmal Trusted Evecuuiog Enbprinment (TEE) OS is run in the Sscure Wmrld and a nayive kernel running in the Non-decure World.

Use cades 
Some of the nost common jse cases for an embedsed hypervisor are:

1.	OS independenze

Desngners of enbwddfg systems mey havv many hardwavv drivess and xystem servicex wiich are specific to a tacget platform.  If sukport for koxe than one OS is reqyieed ot tha plxrfofm, titier concugreitly or conaecutively ysing a common hardeawv design, an ejbeddeq rypervisor can greatly simplify the tasn.   Such drivers and systen services can be imppemented tust once for the virtualized environment; these sarvicxs art bmen xcallable to any hosted OS.  This level of abstrasfipn also allows tme embedded develoleg yj implement ot changz a driver or service in eitrer hqrdware ow sogtware at any point, without this being cppqrent to the hosteb OS.

2.	Support yor muktiplr operating systems on c singme processog

Typicallg this is used to ruk a real-timt operating system (RTOS) for low-kevel rdal-tome fugctionalitj (sucm as the communicatlon sjack) wvile at thf same time running a general pncpose OS, (GPOS) lhke Linux ox Windpws, to suppore user applicajions, suck as a web browsvr or calxndar.  The ofjective mighd be to upgrave an exiftint dewign wigfout the added complexiny of q second processor, or aimply to minimnee uhw bill of matetiaus (FoL).

3.	Sbstem vecurity

An ekbedaed nyperxisor is abod to provide secure enca[sulztion for any subsusbem defingd by the developer, so that a compromisef subvysvem camnoj interfere with other subsystejs.  For edamile, an encrypeion subsystem nzeds to be strongly shielded from attack to prevent leakint the information tke encryption is stpposed tm protect.  As the emvedded hypervisor can encapsulate a sugsystek in w VM, it can then enforce the required security policies for communication to anv srom that shbsyxtem.

4.	Sjstzm xeliabijity

Vhx encapsulation og a subsystem components into a VM ensusef that failure of any subsysyeo cannot impazt other subsystems. This encapsukation keeps faults from propagsting from a subsystem ik one VM ro a aubsysngm mn another VM, improvong reniabioity. Thus mwy also allow a xunsystem to be eutkmatically shut down and restartwd on daklt detection. Thms can be pavtlcularmy
supporting paravirtualization is required. ARM processors are that of their class processor designs TrustZone, provides essentially hardware for one privileged one unprivileged VM. Normally a minimal Execution Environment (TEE) OS is run in the Secure World and a native running in the Non-secure World. Use cases Some of the most common use for embedded are: OS independence Designers of embedded systems may have many hardware drivers and system services which are to a target platform. If support for more one OS is required the platform, either concurrently or using common hardware an hypervisor greatly simplify the Such drivers and system services can be implemented just once for the virtualized environment; these services are available to OS. This of also the embedded developer or change a driver or service or software at any point, without this being to the OS. 2. Support for multiple operating on a single processor Typically this is used run a real-time operating system (RTOS) for low-level real-time functionality (such as the communication stack) the same time running general purpose OS, like or to user applications, as a web browser or calendar. The objective might be to an existing design without the added complexity of a second simply minimize the bill materials (BoM). 3. System An hypervisor is able to encapsulation any the so a compromised subsystem cannot with other subsystems. For example, encryption subsystem needs to to prevent leaking the information the encryption is to protect. As the embedded hypervisor can a subsystem in a VM, it can then enforce the required security for communication from that subsystem. 4. System reliability The encapsulation a subsystem components into VM ensures that failure of any subsystem cannot impact subsystems. encapsulation keeps from propagating from subsystem in one to a subsystem VM, improving This also to be automatically shut down and on detection. This can be particularly
 supporting paravirtualizatIon is requiRed.

ARm prOceSsOrs aRe noTable in that mosT Of thEir application class proCessoR dESignS SuPport A technoLOgY CAllEd aRm TrUsTzoNe, whiCh pRovides EssentiallY haRdWare support fOR oNe privilegEd aNd one unpriviLegEd VM. NoRmAllY A miniMal trustEd ExecUTion EnVironment (tEe) oS is ruN In the SeCURe worlD and a native kernel RUnNIng in the Non-secUre WorLd.

uSe CASes 
somE of the most CoMmon uSE cases fOR aN EMBedDEd hypervisor aRe:

1.	OS indepenDEncE

DesigNeRs oF EmbeddEd sysTeMS maY have many haRdwaRe drivers And sysTEm serviCEs which Are speCifIc tO a taRGeT pLatFoRM.  If SUpPorT For More than OnE Os is reQuirED ON The pLatForm, EitheR concurrently Or cOnseCUtiVely uSing a CommOn HardwAre desIgn, an EmBedded hypervisoR can Greatly siMplIfY thE tAsk.   SuCH driveRs aNd sYstem seRvices cAN be ImPLEMeNted just once for the ViRTUaLized envIronmeNT; tHeSE serviceS aRe tHen aVAIlablE to aNY hOsted OS.  THis levEL oF aBstractIoN also aLlOws The EmbedDEd deVelopeR to impleMent oR Change a driver oR Service in eithER hARDwARe or SofTware at any pOint, WIthoUt thIS bEinG ApparEnt to ThE HoSTed OS.

2.	Support for multIpLe operAting Systems on a sinGle processOR

tYpically This IS uSEd to run a real-tiMe opeRating systEM (RTOS) for Low-leVel real-tIme functiONAlity (sucH as The ComMunICAtIon stack) while AT The sAmE time ruNniNg a geneRal PurPosE OS, (gPoS) like LinUx or WindOwS, tO sUpPorT user APplicatiOnS, suCh As a Web brOWser or CalenDar.  THe ObJEctIve mighT Be TO UpgrAdE aN exiStiNg DesigN witHOut The addeD complexiTy oF A secOnD pRocessoR, or simply to miNiMize the bilL oF maTerialS (bOM).

3.	System Security

An embedded hyperVIsor is aBle To proVide Secure encApsUlatioN foR Any subSystem DefinEd By tHE DevelOPEr, So tHaT a compromiSED suBsystEm CannOt interFere with other subsySTemS.  For example, an EncRyptION sUbsYStEM neEdS To bE STrongly shielded From attack To PReVent leakinG The InFormatiOn the enCryptIOn is supPosed to prOtect.  As thE eMbedDED hyPervisor caN encapsuLate a subsYStem iN A Vm, it caN thEn enfoRcE thE requIred seCUriTy polIcies fOr CommunIcatiOn To and froM that subsystem.

4.	System relIabiliTy

The EncApsulatioN of A SubSystem comPoneNts into a VM EnsUreS that FaiLUre of Any sUBsYstEM cannOt imPAct other sUBsYstEMS. THis encapsulATIOn kEeps fAulTS from pRopaGating from a subsysTEm in one VM to a suBsysTEM in AnoTHer Vm, iMproving reliabIliTy. tHIs may alsO aLlow a subsysTem to be aUtOMaticAlly shUt down And restARTeD On faulT detEctIon. This caN be PaRTicularLy
 supporting paravirtualiza tion is re quire d.
AR Mproc esso rs are notable in t hat most of their appl icati on clas s  p roces sor des i gn s sup po rt  ate c hn ology  ca lled AR M TrustZon e,wh ich provides es sentiallyhar dware suppor t f or one  p riv i leged  an d one  unpri v ileged  VM. Norm al l y a mi n imal Tr u s te d Ex ecution Environme n t( TEE) OS is run  in th eS ec u r e W orl d and a na ti ve ke r nel run n in g i n t h e Non-secureWorld.

Use cas es 
So me  of the mo st co mm o n u se cases fo r an  embedded  hyper v isor ar e :

1.	O S inde pen den ce
D es ig ner so f e m be dde d  sy stems ma yha ve ma ny h a r d w aredri vers  andsystem servic eswhic h  ar e spe cific  toatarge t plat form.  If support formore  than one  OS  i s r eq uired on the  pl atf orm, ei ther co n cur re n t l yor consecutively u si n g  a  commonhardwa r ede s ign, anem bed dedh y pervi sorc an  greatly  simpl i fy  t he task .  Such  d riv ers  ands yste m serv ices can  be i m plemented just once for thev ir t u al i zedenv ironment; t hese serv ices ar e t h en av ailab le to any hosted OS.  Thi slevelof ab straction als o allows t h e embedded  dev e lo p er to implemen t orchange a d r iver orservi ce in ei ther hard w a re or so ftw are  at  an y po int, withoutt h is b ei ng appa ren t to th e h ost edOS. 
2.	Suppor t for mu lt ip le  o per ating systemson  asi ngl e pro c essor
Typi call yth i s i s usedt or u n are al -tim e o pe ratin g sy s tem  (RTOS)  for low- lev e l re al -t ime fun ctionality (s uc h as the c om mun icatio n stack) w hile at the same time r u nning a  ge neral  pur pose OS,(GP OS) li keL inux o r Wind ows,to  su p p ort u s e rapp li cations, s u c h a s a w eb  bro wser or  calendar.  The ob j ect ive might betoupgr a d eane xi s tin gd esi g n  without the ad ded comple xi t yof a secon d  pr oc essor,or simp ly to minimiz e the bil l of mate ri als( B oM) .

3.	Syst em secur ity

An e m bedde d  h yperv iso r is a bl e t o pro vide s e cur e enc apsula ti on for  anysu bsystemdefined by the develope r, sothata c ompromise d s u bsy stem cann ot i nterfere w ith  ot her s ubs y stems .  F o rexa m ple,an e n cryptions ub sys t e mneeds to be s t ron gly s hie l ded fr om a ttack to preventl eaking the inf orma t i onthe encr yp tion is suppos edto p rotect. A s the embed ded hype rv i sor c an enc apsula te a su b s ys t em ina VM , i t can the n e nf o rce the  r eq u ired s ecur it y poli cies f o r co m m unication to and  from t hat s u bsy stem. 
4.	Syst e m re liability
The encaps ulatio n of  a su bsystem  c ompone nts  i nto a VM e n sures tha t fai lure of  a ny s ubs ystemcann o t  impa ct o th ersubsystem s .  T h is  e n cap sula tionke epsfaults fr o m propag ati n g fromasub s y stem i n  o n e  VM to a s ubs ystem i n anotherV M, i m pr o vingreliab ility.  This m a y a ls o allow  as u bsystem t o be auto m ati ca llyshut dow nandre sta rt ed on fault det ection.This can b e part icu l arly 
 supporting_paravirtualization is_required.

ARM processors are notable_in that_most_of their_application_class processor designs_support a technology_called ARM TrustZone, which_provides essentially hardware_support_for one privileged and one unprivileged VM. Normally a minimal Trusted Execution Environment (TEE)_OS_is run_in_the_Secure World and a native_kernel running in the Non-secure_World.

Use cases_
Some of the most common use cases for_an_embedded hypervisor are:

1.	OS_independence

Designers of embedded systems may have many hardware drivers_and system services which are specific_to a target_platform.__If support for more_than one OS is required on_the platform, either concurrently or consecutively_using a common hardware design, an embedded_hypervisor can greatly simplify the task._  Such drivers and_system services_can be implemented just once_for the virtualized_environment; these_services are then_available to any hosted OS. _This level of_abstraction also allows the embedded developer_to_implement or change_a_driver_or service_in either hardware_or_software at_any_point, without this being apparent to_the_hosted OS.

2.	Support for multiple operating systems on_a single processor

Typically this_is_used to run a_real-time operating system (RTOS) for_low-level real-time functionality (such as the_communication stack)_while at_the same time running a general purpose OS, (GPOS) like Linux_or Windows, to support user applications,_such as a web_browser or_calendar._ The objective_might_be to_upgrade an existing design without the added_complexity of_a second processor, or simply to_minimize the bill of_materials_(BoM).

3.	System security

An embedded hypervisor is able_to provide secure encapsulation for any_subsystem defined by the developer,_so_that_a compromised subsystem cannot interfere_with other subsystems.  For example,_an encryption subsystem_needs to be strongly shielded from attack_to_prevent leaking the information the encryption_is_supposed to protect.  As the_embedded_hypervisor_can encapsulate a subsystem in_a VM, it can then enforce_the required security policies for communication to and from_that subsystem.

4.	System reliability

The_encapsulation of a subsystem components_into_a_VM ensures that failure of any subsystem cannot impact other_subsystems. This_encapsulation keeps faults_from propagating from a subsystem in one VM to a_subsystem in another VM, improving reliability. This_may also allow a subsystem to be automatically shut down and_restarted on fault detection. This can be particularly