QNX HYPERVISOR Running multiple OS-es in a single vehicle is going to be a major trend forward (one for instrument clusters, one for infotainment, one for autonomous driving etc.), so hypervisors will be the most foundational software component for connected vehicles. This is why industry experts don't see connected vehicles as "smartphones on wheels", they see them as "data centers on wheels".
Blackberry's QNX hypervisor is currently the most widely-adopted virtualization platform (arguably the industry-standard) among vehicles that need to run multiple OS-es (instrument clusters: QNX, infotainment: Automotive Grade Linux/Android Automotive/QNX/Windows Embedded Automotive/AliOS etc).
The other commercial alternatives in the RTOS hypervisor space (OpenSynergy's COQOS, SysGO's PikeOS, Wind River's VxWorks hypervisor, Green Hills' INTEGRITY) did not find much success in the automotive industry, showing that Blackberry's QNX hypervisor indeed has some stickiness among automakers. In fact, the only 2 hypervisors that currently support VirtIO are QNX hypervisor and COQOS. VirtIO is the upcoming standard that makes the deployment of Android Automotive on vehicles easier by hosting them as virtual machines.
In other words, if an automaker wants to use Android Automotive as their In-Vehicle Infotainment, the path of least resistance is to either use QNX hypervisors or COQOS because this way the automakers no longer have to implement the Hardware Abstraction Layer required for Android Automotive to work on bare-metal. Android Automotive will likely dominate the infotainment space due to its robust media apps development ecosystem and cross compatibility with the smartphone ecosystem. IVY will provide an interface for Android Automotive app developers to access vehicle sensor and localization data (possible monetization opportunity?). Any forward-looking automaker who wishes to compete with Tesla will definitely choose the Android Automotive + QNX hypervisor (+ Blackberry IVY possibly) stack. Recent examples include Volvo Polestar 2 and Ford.
QNX also has the largest market share in the digital instrument clusters RTOS space currently. QNX uses a microkernel architecture so it is designed to guarantee functional safety and hard real-time requirements which are essential for instrument clusters and vehicle control. Nobody wants to see their speedometer or brakes lagging behind or their digital dashboard crashing in the middle of the road because this poses safety risk. QNX is ISO 26262 ASIL-D certified, the highest possible safety rating for automotive RTOS.
AGL is no match in this space due to its monolithic architecture that makes it difficult to guarantee functional safety and hard real-time requirements. Some automakers may choose to use AGL/Linux for now (eg. Tesla), but this is really an unsafe practice and should hopefully be regulated soon. I remember hearing horror stories about Tesla's dashboard crashing and blacking out when the car is still moving on Autopilot on the freeway. Hopefully, as ADAS/self-driving becomes more mainstream, traffic authorities will make ISO 26262 ASIL-D safety certification a legal requirement for all connected vehicles.
On the security side, Blackberry's integration of Cylance into QNX will also be a key differentiator. As vehicles become more connected to the internet, hacking is inevitable and security will be a major requirement for all automakers. To see how scary it can be, see this Jeep hackvideo. Blackberry has a great track record in security and its security expertise is world leading, so this is another stickiness of QNX.