Mobile device virtualization solution based on bare-metal hypervisor with optimal resource usage and power consumption

A computing system with multiple hardware-isolated virtual machines (VMs) with a minimal overhead requirement comprising:

• a physical computing system comprising a Central Processing Unit (CPU), virtualization extensions, a memory, a memory management unit (MMU), an input/output memory management unit (IOMMU), a user interface hardware and a storage/communication hardware;
• a foreground VM comprising a foreground direct driver to access the user interface hardware and a foreground paravirtualized driver to access the storage/communication hardware;
• a background VM comprising a background direct access driver to access the user interface hardware and a background paravirtualized driver to access the storage/communication hardware;
• an interoperability VM comprising a direct access driver to access the storage/communication hardware, wherein the interoperability VM allows paravirtualized access to the storage/communication hardware from the background VM and the foreground VM;
• and
• a bare-metal hypervisor to concurrently run, independently and isolated from one another, each of the interoperability VM, the foreground VM, and the background VM,
• wherein the bare-metal hypervisor performs a switch from the foreground VM to the background VM upon a switch initiation, wherein during the switch the foreground VM becomes the background VM and vice-versa,
• wherein the bare-metal hypervisor configures the input/output memory management unit to prevent direct access to the user interface hardware by the background VM,
• wherein the bare-metal hypervisor configures the input/output memory management unit to only allow a direct access to the storage/communication hardware by the interoperability VM,
• wherein an interrupt for the user interface hardware is handled by the foreground VM and an interrupt for the storage/communication hardware is handled by the interoperability VM,
• wherein the bare-metal hypervisor activates the background VM from time to time without performing the switch between the foreground VM and the background VM, and
• wherein the bare-metal hypervisor activates the background VM and allocates CPU resources thereto when the background VM is a target of the custom timer event or of a paravirtualized storage and communication driver interrupt event.