{"id":2059,"date":"2022-01-18T15:25:06","date_gmt":"2022-01-18T15:25:06","guid":{"rendered":"https:\/\/iot-ngin.eu\/?p=2059"},"modified":"2022-01-28T15:25:15","modified_gmt":"2022-01-28T15:25:15","slug":"microvms-to-reduce-the-overhead-of-virtualization","status":"publish","type":"post","link":"https:\/\/iot-ngin.eu\/index.php\/2022\/01\/18\/microvms-to-reduce-the-overhead-of-virtualization\/","title":{"rendered":"microVMs to reduce the overhead of virtualization"},"content":{"rendered":"\n

Virtual Machines (VM) are common and established techniques to isolate the guest from the host operating systems. They are typically designed to run common operating systems like Windows and Linux as guest operating systems. Consequently, they create a virtual PC with the support of over decades developed interfaces (e.g. PCI, ACPI). This legacy support increases the boot time and the memory foot print of such virtual machines.<\/p>\n\n\n\n

Projects like Firecracker<\/a>, Solo5<\/a> and Qemu\u2019s microVM platform<\/a> established minimalist machine type without any PCI or ACPI support. Such microVMs also establishes a baseline for benchmarking and optimizing both QEMU and guest operating systems, since it is optimized for both boot time and footprint. In combination with Unikernels<\/a>, the overhead and the attack vector can be reduced even further. The assumption is here that less source code in the implementation of the microVM and the guest operating system reduces also the possibility of security issues.<\/p>\n\n\n\n

In the meantime, container runtimes like Kata containers<\/a> integrates microVMs seamless in a container ecosystem. By using such runtimes, Kubernetes is able to deploy microVMs and benefits from their stronger isolation. Our evaluation of starting 800 web-services shows that deploying microVMs doesn\u2019t increase the overhead in comparison to common container runtimes like runc. For this evaluation, we wrote our own container runtime and combined it with a microVM. We want to use this combination as base for developing a secure edge runtime. The strong isolation reduces the possibility of security issues, while reduction of overhead increase the scalability of the IoT-NGIN framework.<\/p>\n\n\n\n

Summary of benefits:<\/p>\n\n\n\n