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.
- Where AR We? - February 19, 2018
- Flexible Scaleout, Tom Lyon, and Reveal(x) in Gestalt News 18.8 - February 19, 2018
- In Defense of Facebook’s “Protect” - February 15, 2018
- Tom Lyon – IT Origins - February 15, 2018
- Do You Want to Build a Cloud? Gestalt IT Rundown: February 14, 2018 - February 14, 2018
- AI and Machines That Think They Can Think - February 14, 2018
- Docker for Home Automation - February 13, 2018
- The Cheapest PC Is Now More Expensive and Worse - February 13, 2018
- What’s Next for Infrastructure in a Post-Meltdown Reality? - February 13, 2018
- The IT Differentiation Dilemma – The On-Premise IT Roundtable - February 13, 2018