The KVM support of Android 13 is for greater security, but it can also take it for fun.
Here is a new funny feature of Android 13: Virtualization support. Google creates Virtualization on Android from its own reasons at Android, but the Android developer KDDRAG0N has the function with the boot arm with Windows 11 and Desktop Linux. The developer even has the version of Windows of Doom that works, all in a virtual machine in the pixel 6.
KDRAG0N says that Android 13 has a complete KVM functionality "of" Native Performance ". It needs root to activate the functionality that does not support the GPU acceleration. The functionality does not support the nested virtualization, so that now can run Android in Windows and Windows on Android, with an infinitely nested OS conferred that is not in question.
This makes a decent demonstration not at all, what Google wants to do with the next VM support of Android. Speeds Mishal Rahman has been observing the process of virtualization of Android for some time, and the apparent plan is to use a day (possibly on Android 13) virtual machines as a security and privacy sandbox for various functions. Instead of processing confidential data at the level of authorization of normal application
The first part of Google's virtualization work is standardized, the Linux kernel is supplied with an Android device. Today, the Kernel in Android is the usual history of the Android with each individual telephone model that has loaded a personalized version of the Linux kernel with certain changes and units. The nuclei never update, and it is very difficult to record virtualization functions in an operating system when literally located 10,000 different Android cores. Google plan to standardize Linux kernel is called "GKI" or "Generic Kernel Image".
Generic kernel is the Android core with as many changes as possible, and changes from each manufacturer or hardware manometer through a module system. Now, the main kernel is standardized and has a known set of functions. One day, the Kernal can even be updateable. The GKI sends first on pixel 6, so the pixel 6 is the first Android phone (and previously, previously) that can do so.
Google takes over the Linux Kernel Virtual Machine Manager, Crosvm, Crosvm. The company also builds a headless and striped version of Android, which is running on a VM.
Previously, this small operating system was adopted to go through the name "mikrodroid", but the moniker seems to be just a label in the VM software software. The most precise name seems to be "compos", as expected in an isolated compilation operating system. All this code will eventually be delivered to any Android phone through a new main module.
Google introduces the main distribution of Android and the virtual machine protected in the hypervisor of the device, which makes VM data an additional level of private and safety are the most restrictive Android configuration. For appetizers, Google wants to use it as a replacement for the fiduciary area of the arm (running things like DRM) and cryptographic work. Google wants to get rid of Trustzone because Trustzone is full of third-party third-party code, and because Trustzone is slow. With a faster safe environment in which you can work, Google could begin to obtain more sensitive tasks, such as voice recognition in one of these private VMs. So far, the company appears as if there was progress!
