Changes

Jump to: navigation, search

Comparison

3,403 bytes added, 09:42, 23 September 2015
New comparison table
{{Stub}}
== Feature comparison of different virtualisation virtualization solutions ==
{| class="wikitable sortable"
!ParameterFeature!Description!OpenVZ-legacy(stable)!Virtuozzo 6(PCS 6)!Virtuozzo 7 OpenVZ!Virtuozzo 7 CommercialPlus!LXC
!Proxmox
!Citrix Xen!Microsoft Hyper-V2012 R2!RHEV 3.5!Citrix XenServer 6.5
|-
|Virtualization type|Containers|Containers and hypervisor|Containers and hypervisor|Containers and hypervisor|Containers and hypervisor|'''HW virtualization support (Hypervisor)'''|Hypervisor|-|Guest Full emulation of underneath hardware level: full isolation guest environment, no dependencies from host OS support|Linux|Windows, Linux, FreeBSD|Windows, Linux|Windows, Linuxoverhead for hypervisor layer.|Windows, Linux, FreeBSDNo|Windows, Linux (limited support)Yes|Windows, Linux (limited support)|-Yes|Unified management tools for CTs and VMsYes
|No
|Yes
|Yes
|Yes
|???|???|???Yes
|-
|Central management'''OS-level virtualization (Containers)'''|[[Control_panelsSharing the same instance of host OS: high density, high performance, high dependencies from host OS.|Yes|Yes|Yes]]|PVAYes|???Yes|???Yes|???No|???No|???No
|-
|Toolkit for compact of fat ploop images'''Hypervisor technology'''|NoTechnology that enables to run Virtual Machines.|Yes, pcompactNone|Yes, pcompactParallels Desktop Monitor|Yes, pcompactKVM|NAKVM|NANone|NAKVM|Hyper-V|KVM|Xen
|-
|Toolkit for migration physical servers '''Containers technology'''|Technology that enables to containersrun Containers.|Virtuozzo Containers|No, only [[Physical_to_containerVirtuozzo Containers with enhancements|instruction]]Virtuozzo Containers with enhancements|Yes, p2c migrateVirtuozzo Containers with enhancements|Yes, p2c migrateLinux containers|Yes, p2c migrateLXC (moved from OpenVZ since 4.0)|???None|???None|???None
|-
|Rebootless kernel update'''Memory Overcommit'''|Ability to present more memory to virtual machines than physically available |Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|-|'''Page sharing'''|Memory (RAM) savings through sharing identical memory pages across virtual machines|Yes|Yes, only for CTs|Yes|Yes|Yes|Yes|No|Yes
|No
|Yes, vzreboot
|Yes, vzreboot
|Yes, vzreboot
|NA
|NA
|NA
|-
|Pure kernel live updates'''Unified management tool for CTs and VMs'''|No, only with external Single tool [http://kernelcare.com/ KernelCare]for managing both containers and virtual machines (if applicable)|None|No, only with external tool [http://kernelcare.com/ KernelCare]Yes|Yes|Yes|???None|???No|???None|???None|???None
|-
|Repair mode '''Central Management tool'''|Is centralized multi-server management available for VPSthis edition?|Yes, 3rd party|Yes, Parallels Virtual Automation (PVA)
|No
|Yes, PVA
|Yes, 3rd party
|Yes
|???Yes, System Center Virtual Machine Manager|???Yes, RHEV Manager|???Yes, XenCenter|???-|???'''Update Management'''|Integrated patching mechanism for the virtual environments (Guest OS) / guest tools / templates|No integrated update, YUM (Linux)|No integrated update, YUM (Linux), WSUS (Windows)|No integrated update, YUM (Linux), WSUS (Windows)|No integrated update, YUM (Linux), WSUS (Windows)|No integrated update, APT (Linux)|No integrated update, YUM (Linux), WSUS (Windows)|Yes (WSUS, SCCM, Virtual Machine Servicing Tool 2012 for offline VM update)|No integrated update, YUM (Linux), WSUS (Windows)|No integrated update, YUM (Linux), WSUS (Windows)
|-
|'''Live migration between servers VE snapshot'''|Ability to take a snapshot of a virtual environment while the guest OS is running (no zero downtimee.g. for roll-back or backup purposes)|Yes|Yes|Yes|Yes|Offline, CRIU support is planned|Yes
|Yes
|Yes
|Yes
|???
|???
|???
|-
|Live migration between servers '''Integrated Backup'''|Are backup plugins/tools provided to backup virtual environments (zero downtimeover and above the ability to perform classic backup using agents in the guests)|No|Yes
|No
|Yes
|No
|Yes
|Yes
|???No|???|???No
|-
|Flexible container OS templates'''Backup Integration API'''|Integration with 3rd party backup applications for backup of the virtual environment.|No, (only [https://openvz.org/Download/template/precreated precreated templates]through snapshots)|Yes|Yes|Yes|No (only through snapshots)|Yes, vztemplates(vzdump)
|Yes
|Yes
|???
|???
|???
|-
|Memory deduplication for binary files
|No
|Yes, pfcache techology
|???
|???
|???
|???
|???
|-
|Support for cloud storages for containers'''VEs Templates (VM, CT)'''|NFS, Ability to create and store master images and limited Parallels Cloud Storagedeploy virtual machines from them|Yes (CT only)|Yes|Yes, Parallels Cloud Storage|???Yes|???Yes (OpeVZ templates)|???Yes|???Yes|???Yes|Yes
|-
|Completely isolated disk subsystem for containers'''P2V migration'''|Integrated or added P2V (or V2V) capability in order to convert physical systems to virtual environment.|No|Yes, ploop|Yes, ploop|Yes, ploop|YesNo|No, ploop3rd party tools|NAYes|NANo|NANo
|-
|Fast and reliable kernel on top '''Live Migration of RHEL 2.6.32VEs'''|Ability to migrate virtual machines between hosts without perceived downtime|Yes, but with no zero downtime|Yes, Kernal-Level Migration|Yes, CRIU|Yes, CRIU|Offline, CRIU support is planned
|Yes
|Yes (same version as OpenVZ)
|Yes
|Yes
|Yes
|NA
|NA
|-
|Full backup capability'''Automated Live Migration (DRS)'''|Ability to put host into maintenance mode which will automatically live migrate all virtual machines onto other available hosts so that the host can be brought shut down safely|No|No|No|Yes|No|No, but open source solutions exists
|Yes
|Yes
|Yes
|???
|???
|???
|-
|Incremental backup'''Storage Migration'''|Integrated Power Management features Ability to automatically migrate vms onto fewer hosts and power off unused capacity (hosts), wake systems back up when required |No|No|No|No|No|No, and no open source solutions
|Yes
|Yes
|Yes
|???
|???
|???
|-
|NUMA optimization '''Cluster size'''|Maximum number of hosts in the cluster/pool relationship and maximum number vms per cluster/pool (balancingif specified)|No, but some [https:None|32 hosts/cluster validated (100 hosts/code.google.com/p/vmcluster maximum) -balancerPStorage limitation|Not tested yet|Not tested yet|None|32 nodes|64 nodes|200 nodes|16 nodes|-numa/downloads/detail?name|'''Integrated HA'''|Recover virtual environment in case of host failures through restart on alternative hosts (downtime =vm-balancer.py&can=2&q= open source solutions exists]restart time)|No|Yes|No|Yes|No|Yes
|Yes
|Yes
|Yes
|???
|???
|???
|-
|Physical-'''Site Failover'''|Integrated ability to-Virtual, Container-(ideally live) migrate virtual machine data (virtual disk files) to-Virtual different storage e.g. for array upgrades/migrationand I/O management|No|No|No|No|No|No|Manual
|No
|Integrated Disaster Recovery - manual
|-
|'''Supported Storage'''
|Supported types of Storage (DAS: Direct Attached Storage, NAS: Network Attached Storage, FC: Fibre Channel, iSCSI, FCoE - Fibre Channel over Ethernet)
|DAS (EXT4)
|NAS (NFS), DAS (EXT4)
|DAS (EXT4)
|NAS (NFS), DAS (EXT4)
|NAS (NFS), DAS (EXT4)
|SAN, NAS (NFS), Ceph 
|DAS, NAS (SMB), SAN (iSCSI, FC, FCoE)
|DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)
|DAS, NAS (NFS), SAN (iSCSI, FC, FCoE)
|-
|'''Virtual Disk Format'''
|Supported format(s) of the virtual disks for the virtual machines
|CT - ploop
|CT - ploop, VM - ploop
|CT - ploop, VM - ploop\Qcow2
|CT - ploop, VM - ploop\Qcow2
|Any
|qcow2
|vhdx, vhd, pass-though (raw)
|Qcow2, raw disk
|vhd, raw disk
|-
|'''Thin Disk Provisioning'''
|Ability to over-commit overall disk space by dynamically growing the size of virtual disks based on actual usage rather than pre-allocating full size.
|Yes
|Yes
|Yes
|Yes
|Yes, depends on disk format (dm-thin)
|Yes (???)
|Yes
|Yes
|Yes
|???
|???
|???
|-
|API'''Virtual SAN'''|[https://libvirtEnhanced storage capability e.org/drvopenvzg.html LibVirt]providing a virtual SAN through virtualized 'local' storage |Yes, [[Virtuozzo_ecosystem#API]]Virtuozzo Storage|Yes, [[Virtuozzo_ecosystem#API]]Virtuozzo Storage|Yes, [[Virtuozzo_ecosystem#API]]Virtuozzo Storage|???Yes, Virtuozzo Storage|Yes, but 3rd party (DRBD 9, Ceph, GlusterFS)|Yes, but 3rd party (DRBD 9, Ceph, GlusterFS)|Yes, Storage Spaces|???Yes, Red Hat Storage|???No
|-
|Opensource'''Storage QoS'''|Ability to control Quality of Service for Storage I/O for virtual machines|No|Only IOPs limits|Only IOPs limits|Only IOPs limits|No|No
|Yes
|Partially
|Yes
|Partially
|Yes
|-
|'''Advanced Network Switch'''
|Centralized virtual network configuration (rather than managing virtual switches on individual hosts), typically with enhanced networking capabilities
|No
|No
|No
|No
|No
|Yes, Open vSwitch support
|Yes
|Neutron Integration
|Open vSwitch integration
|-
|'''Network QoS'''
|Ability to create and store master images and deploy virtual machines from them
|Only bandwidth limits
|Only bandwidth limits
|Only bandwidth limits
|Only bandwidth limits
|Only bandwidth limits
|Yes, with Open vSwitch 
|Yes
|Yes
|Yes
|-
|'''Memory deduplication for binary files'''
|Memory and IOPS deduplication management that enables/disables caching for Container directories and files, verifies cache integrity, checks Containers for cache errors, and purges the cache if needed
|No
|Yes, pfcache
|Yes, pfcache
|Yes, pfcache
|No
|No
|None
|None
|None
|-
|Source code'''Completely isolated disk subsystem for CTs'''|[https://src.openvz.org/projects/OVZL Yes]|???Yes, ploop|[https://src.openvz.org/projects/OVZ Yes], ploop|[https://src.openvz.org/projects/OVZ Yes], ploop|[https://git.proxmox.com/ Yes], ploop|[http://www.citrix.ru/go/products/xenserver/xenserver-source-free.html Yes], with LVM
|No
|None
|None
|None
|-
|Support'''API\SDK'''|Yes|OpenVZ API for Ruby, LibVirt|Parallels SDK, LibVirt|Parallels SDK, LibVirt|Parallels SDK, LibVirt|Liblxc, API for Ruby, python2, Haskell, Go|Proxmox VE uses a REST like API (JSON data format)|Windows SDK|RHEV-M API: REST API, SDKs|XenAPI, community support XenServer SDKs|-|'''Image Catalog integration'''|Integration with 3rd-party image catalog services of popular server applications and [[Supportdevelopment environments that can be installed with one click.|No|No|No|Yes (Bitnami)|No|Yes (Turnkey)|None|None|None|-|'''Open Stack integration'''|Driver for Open Stack Nova|Yes|pay support]]Yes
|Yes
|NoYes|Full supportYes|(LXC and KVM supported through libvirt)
|Yes
|Yes
|Yes
|-
|Hosting automation'''Kernel maintenance'''|???Ability to upgrade kernel with minimal downtime.|KernelCare service integration|kernel rebootless update (vzreboot)|Yes, [http://www.odin.com/ru/products/automation/ Odin Automation]KernelCare service integration|kernel rebootless update (vzreboot)|???KernelCare service integration|Yes, [http://www.odin.com/ru/products/automation/ Odin Automation]KernelCare service integration|???None|???KernelCare service integration|???KernelCare service integration
|-
|Shared storage'''Power Panel'''|[[Parallels_Cloud_StorageA tool used for managing particular virtual machines and containers by their end users.|No|Yes|Odin Cloud Storage]]No|Odin Cloud StorageYes|???None|Odin Cloud StorageNone|CEPH?None|???None|???None
|-
|Ability to donate'''Open Source'''||Yes|No|Yes|No|Yes|Yes|No|No|No (but there is Open Source edition)|-|'''License\Subscription'''||No|Yes|No|[https://openvz.org/Donations Yes]
|No
|[https://openvz.org/Donations Yes]
|No
|[http://pveYes|Yes|Yes, Enterprise Edition|-|'''Support'''||Both community and commercial support|Commercial support|Community support|Commercial Support|Yes, Canonical Ltd.proxmox.com/wiki/Show_Your_Support Yes]|???Both community and commercial support|Commercial support|Commercial support|Both community and commercial support|???-
|}
 
== Virtuozzo main benefits in comparison to OpenVZ ==
 
* Ability to create Virtual Machines.
: In addition to Containers, one can create full-scale VMs using a build-in hypervisor. Both Containers and Virtual Machines are managed by the same tools in a uniform way.
 
* Virtuozzo Storage.
: A resilient and robust way to unify all your local nodes storage into a single highly available SAN-grade distributed storage system.
 
* Higher container density.
: Virtuozzo provides efficient memory and file sharing mechanisms (VZFS or pfcache) enabling higher container density and better performance of containers.
 
* Unified management tools for CTs and VMs
: Virtuozzo ships with number of management, monitoring, troubleshooting, and administration tools significantly reducing management, administration, and deployment costs. Specific tools include:
<ul>
: <li> [http://www.odin.com/support/virtualization-suite/pva Parallels Virtual Automation]</li>
: <li> Number of additional CLI tools.</li>
</ul>
 
* Support and maintenance.
:Virtuozzo is a commercial product supported and maintained by Odin with options for 24×7 phone support and guarantees on maintenance schedules.
 
* Advanced recovery, monitoring, and back-up tools.
 
* Physical-to-Virtual (P2V) and Virtual-to-Physical (V2P) migration tools.
: Those tools allow easy conversion of existing physical machines into a container (and vice-versa) facilitating the adoption of virtualized infrastructure.
 
* Common client-server XML-based management API.
: API allows easily integration of Virtuozzo into existing management infrastructure and development of additional management and monitoring modules.
 
* Traffic accounting tools.
: These tools enable bandwidth management and control for individual containers and provide additional security mechanisms for containers running on the same host.
 
 
 
== See also ==
 
- [http://www.stableit.ru/2015/05/technical-comparison-of-openvz-and.html Technical comparison of OpenVZ and commercial Virtualization Platforms from Parallels/Odin]

Navigation menu