An old dog is learning some new tricks. QNX has been around since the 80s, and the OS is getting a big update from BlackBerry.
For those not familiar, QNX began as one of the first OS’s using a microkernel architecture. As opposed to a traditional monolith kernel, a microkernel runs most system level events as “servers”, which can be turned off by developers as needed. This combined with being a real-time operating system made the OS a natural fit for embedded automative operating systems.
Now, QNX supports containers with the release of their QNX Hypervisor 2.0. This will allow developers to further fine tune how applications components interact with important safety systems. It seems like a natural extension for an OS entirely geared around minimal resource utilization, reliability, and compartmentalization.
Sadly, it doesn’t look like QNX will be running Docker on your car any time soon.
Larry Dignan Comments:
QNX Hypervisor 2.0 creates containers to ensure that any breach in one auto application can be contained. For instance, an issue in the infotainment system wouldn’t impact digital instruments with containers and application isolation.
Qualcomm Technologies is adopting QNX Hypervisor 2.0 for some of its digital cockpit applications. Qualcomm will use BlackBerry’s hypervisor for its Snapdragon 820A automotive platform.
- Trends – IT Origins Survey - April 19, 2018
- Qualcomm’s Terrible No Good Very Bad Acquisition | Gestalt IT Rundown: April 18, 2018 - April 18, 2018
- Open Mesh Brings Major Disruption to SMB Space, Goes Full-Stack - April 17, 2018
- BONUS: Karen Lopez – IT Origins - April 17, 2018
- You Can’t Handle the SaaS in Gestalt News 18.14 - April 16, 2018
- Sonia Cuff – IT Origins - April 12, 2018
- Traditional is the New Legacy - April 11, 2018
- The Security Problem of Email Dots - April 10, 2018
- You Should Care Where SaaS Lives | On-Premise IT Roundtable - April 10, 2018
- VPNs Made Easy, Panera Data Breach, and InfiniSync in Gestalt News 18.13 - April 9, 2018
Leave a Reply