The difference between OS-level virtualization (containers) and hardware virtualization (virtual machines) in InfoboxCloud
When creating a virtual server in InfoboxCloud, the user can set the flag “I will manage the OS kernel”. If the flag is not set, OS-level virtualization is used (by default). If the flag is set, hardware virtualization is used.
In this article, we will answer a frequently asked question: what is the difference in the types of virtualization of InfoboxCloud and which virtualization to choose.
OS-level virtualization allows virtualization of physical servers at the kernel level of the operating system.
')
The OS virtualization layer provides isolation and security of resources between different containers. The virtualization layer makes each container look like a physical server. Each container serves the applications in it and the workload.
From the point of view of the application, each container is an independent system. Independence is provided by the level of virtualization of the Parallels Cloud Server operating system. The minimum amount of CPU resources is spent on virtualization: 1–2%.
Key Features:
It is also interesting that virtual server image files are stored in a single file (.hdd), which makes it easier to perform migration and backups due to sequential access to a single file instead of separate container files.
After creating the container, the template of the operating system from which the creation was made is no longer necessary. This means that even if we declare an OS that is outdated and remove it from the cloud, your created servers will continue to work.
Containers use native journaling disk quotas and in case of a physical server crash, no quota recalculation is required.
In hardware virtualization, the base layer is the hypervisor. This layer is loaded on the server and provides interaction between the server hardware and the virtual machines. To provide resources to virtual machines, they are virtualized on the server. Virtual machines run their own copy of the operating system and applications on virtualized hardware.
Each virtual server is stored in at least two files: a configuration file and a hard disk file.
The created virtual server, as in the case of virtualization at the OS level, does not depend on the presence of the OS template in the cloud. In the case of updating or deleting a template, changes on the virtual server will not occur.
If you have never thought about it - use container virtualization. It is great for most tasks on a virtual Linux – server. You will get the fastest possible server creation and reboot times (which is very important when migrating the server). Also, when using OS-level virtualization, auto-scaling of RAM is available.
If you need Windows, the installation of OS kernel extensions (for example for VPN), full control over the OS kernel, the ability to use Docker , the OS manual upgrade - use hardware virtualization.
Successful use of InfoboxCloud !
In this article, we will answer a frequently asked question: what is the difference in the types of virtualization of InfoboxCloud and which virtualization to choose.
OS-level virtualization
OS-level virtualization allows virtualization of physical servers at the kernel level of the operating system.
')
The OS virtualization layer provides isolation and security of resources between different containers. The virtualization layer makes each container look like a physical server. Each container serves the applications in it and the workload.
Key Benefits of Container Virtualization
- Containers run at the same level as physical servers. The lack of virtualized hardware and the use of real hardware and drivers provide unrivaled performance.
- Each container can scale to the resources of the entire physical server.
- Virtualization technology at the OS level allows you to achieve the highest density among the available among virtualization solutions. It is possible to create and launch hundreds of containers on one ordinary physical server.
- Containers use a single OS, which makes their support and updating very simple. Applications can also be deployed in a separate environment.
InfoboxCloud container features
From the point of view of the application, each container is an independent system. Independence is provided by the level of virtualization of the Parallels Cloud Server operating system. The minimum amount of CPU resources is spent on virtualization: 1–2%.
Key Features:
- Containers look like a normal Linux – system. They include the usual startup scripts. Third-party applications can run in containers without the need for modification.
- The user can change any configuration files and install any additional software in containers.
- Containers are completely isolated from each other (file system, processes, sysctl variables) and Parallels virtual machines.
- Containers share dynamic libraries, which significantly saves memory.
- The processes in the containers are scheduled for execution on all available CPUs. Containers are not limited to a single CPU and can use the full power of a host's CPU.
It is also interesting that virtual server image files are stored in a single file (.hdd), which makes it easier to perform migration and backups due to sequential access to a single file instead of separate container files.
After creating the container, the template of the operating system from which the creation was made is no longer necessary. This means that even if we declare an OS that is outdated and remove it from the cloud, your created servers will continue to work.
Containers use native journaling disk quotas and in case of a physical server crash, no quota recalculation is required.
Hardware virtualization
In hardware virtualization, the base layer is the hypervisor. This layer is loaded on the server and provides interaction between the server hardware and the virtual machines. To provide resources to virtual machines, they are virtualized on the server. Virtual machines run their own copy of the operating system and applications on virtualized hardware.
Key Benefits of Hardware Virtualization
- The ability to create multiple virtual machines with different operating systems (including Windows). No dependency on a single OS kernel. The user can install his own patches on the kernel if it is necessary to obtain the extended functionality of a virtual server.
- Virtual machines look like a regular computer. They contain their own virtual hardware and software that can run in virtual machines without the need for modification.
- Virtual machines are completely isolated from each other and from the server's OS, where virtual machines are started (isolation at the file system level, processes, sysctl variables).
- Thanks to the use of Intel and AMD virtualization technologies, the performance of virtual servers is very high and is close to the performance of real hardware.
Each virtual server is stored in at least two files: a configuration file and a hard disk file.
The created virtual server, as in the case of virtualization at the OS level, does not depend on the presence of the OS template in the cloud. In the case of updating or deleting a template, changes on the virtual server will not occur.
What virtualization to choose?
If you have never thought about it - use container virtualization. It is great for most tasks on a virtual Linux – server. You will get the fastest possible server creation and reboot times (which is very important when migrating the server). Also, when using OS-level virtualization, auto-scaling of RAM is available.
If you need Windows, the installation of OS kernel extensions (for example for VPN), full control over the OS kernel, the ability to use Docker , the OS manual upgrade - use hardware virtualization.
Successful use of InfoboxCloud !
Source: https://habr.com/ru/post/247595/
All Articles