The rapid development of container technology has squeezed out many sites of traditional virtual machine technology. No way, in the boot speed and performance, the container has too many advantages, and the development of virtual machine technology is too slow.
Now, fueled by container technology, the next generation of virtualization technologies--hyper--can be launched with the same speed as containers.
Brief introduction
Simply put, hyper = Hypervisor + Kernel + Docker Image, which is essentially a virtual machine technology.
Hyper runs the container in the virtual machine, except that the virtual machine is streamlined (based on qboot) and can quickly start a stopped virtual machine. Currently, you can run on KVM and the operating system requires Debian, and the kernel is recommended for 4.0.1.
Hyper can run multiple processes per virtual machine, borrowing the concept of pods in kubernetes. Each virtual machine is a pod in which processes share namespaces (not using namespace isolation).
Advantage
The advantage is obvious, the container technology has been lacking, with the traditional virtual machine-related advantages:
- Can seamlessly integrate with existing virtual machine-based technologies and platforms;
- It greatly improves the security of the container's existing isolation technology, especially the need to share the kernel.
- Do not rely on existing container technology (Docker daemon, LXC, Cgroup, Namespace), only MOUNT namespace support is required.
Disadvantage
The disadvantage is also obvious:
- Additional resource consumption is added, including additional cores and processes;
- Not as mature as claimed;
- The ecological environment has yet to be established.
Principle
The Hyper component is simple:
- Hyper provides command line interface
- Hyperd provides a core maintenance engine that supports REST
- Virtual machine instance: Hyperkernel as the kernel;hyperstart of the guest OS as the Startup init service.
Prospect
In fact, there are already some similar technologies, including two major categories:
- Based on the container for further encapsulation, CoreOS, Rancheros, and so on, in fact, the application of running or in the container;
- Intel's clear Container, like hyper, runs a lightweight virtual machine directly.
Each of these technologies has its own pros and cons, as well as the appropriate application scenarios that will coexist for a long time and even more virtualization technologies for the Cloud ERA scenario.
Reprint Please specify: http://blog.csdn.net/yeasy/article/details/46648303
Brief analysis of hyper--Next generation virtualization technology?