Re:Chrome OS: Ready for Web Development [video]
by bsaul on Wednesday November 14, 2018 @02:59PM
(#18453284)
What 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 ?
Re:Chrome OS: Ready for Web Development [video]
by celkam on Wednesday November 14, 2018 @05:10PM
(#18454582)
Yes. 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.
Re:Chrome OS: Ready for Web Development [video]
by liamcardenas on Wednesday November 14, 2018 @04:42PM
(#18454285)
Good 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.”
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.