5 ms·
Around this time: https://youtu.be/QTmAtXoPkgw?t=256 https://youtu.be/QTmAtXoPkgw?t=256 (4:16 into the video) it talks about how ChromeOS runs Android, Linux,
by liamcardenas 8y ago
Around this time: https://youtu.be/QTmAtXoPkgw?t=256 https://youtu.be/QTmAtXoPkgw?t=256 (4:16 into the video)
it talks about how ChromeOS runs Android, Linux, and ChromeOS apps natively, in a performant and secure manner, without emulation using a combination of containers and hardware virtualization.
This strikes me as very similar to Qubes' security model. Very interesting to see this architecture developed by a company like Google.
- bsaul 8y agoWhat do you mean by "without emulation ... using hardware virtualization" ? Is the difference that hardware of the VM has to match the one of the real hardware ?
- liamcardenas 8y agoGood question. I don't know the official difference between emulation and virtualization. I do want to point out that these were the words of the presenter, and not my own: “So, Android and Linux support don’t do any emulation. By using lightweight containers and hardware virtualization support, your code will run natively.”
- celkam 8y agoYes. In emulation, you have one chip architecture trying to mock the behavior of another chip architecture (like running ARM code on x86). In virtualization, you're setting up secure contexts, but sending the instruction for the code in the container straight to the CPU without translation.
- jeena 8y agoI find the picture they're showing also quite confusing, my guess is that they're using some kind of a hardware hypervisor and that runs different VMs.