6,534
edits
Changes
more on single kernel approach
Xen, KVM, VMware and other hypervisor-based products provide an ability to have multiple instances of virtual hardware (called VMs – Virtual Machines) on a single piece of real hardware. On top of that virtual hardware one can run any Operating System, so it's possible to run multiple different OSs on one single server. Each VM runs full software stack (including an OS kernel).
In contrast, OpenVZ uses a single-kernel approach. There is only one single OS kernel running, and on top of that there are multiple isolated instances of user-space programs. This approach is more lightweight than VM, leading . The consequences are: # Waiving the need to run multiple OS kernels leads to '''higher container density ''' of containers (compared to VMs)# Software stack that lies in between an application and the hardware is much thinner, this means higher performance.of containers (compared to VMs)
== Containers overhead ==
== Other features ==
* Live migration.
