3. KVM
Main developer: RedHat
Kernel integration state: in kernel since 2007
Status: production ready
Hardware support: same as Linux
Virtualization type: full virtualization
Supported client OS: Linux, FreeBSD, Windows
5. Xen
Main developer: Citrix, XenSource
Kernel integration state: partially in kernel since 2012
(client), no plans about the server
Status: production ready
Hardware support: only fixed number of hardware, see
HCL
Virtualization type: full virtualization, paravirtualization
Supported client OS: Linux, FreeBSD, Windows
7. OpenVZ
Main developer: Parallels (ex. SwSoft)
Kernel integration state: partially in kernel and work in
progress
Status: production ready
Hardware support: same as Linux
Virtualization type: os level
virtualization, containerization
Supported client OS: Linux
9. LinuX Containers, LXC
Main developer: same as kernel (Intel, IBM, Parallels)
Kernel integration state: partially in kernel and work in
progress
Status: not ready for production (issues in
network, disk)
Hardware support: same as Linux
Virtualization type: os level
virtualization, containerization
Supported client OS: Linux
11. Why OpenVZ?
• Production ready since 2006
• Extremely low overhead (in compare with
Xen/KVM is about 20%)
• Simple integration into Linux stack
• Many successful projects (LXC): Heorku,
CloudLinux, Docker (dot.cloud)
15. OpenVZ requirements
• Almost any physical server (yes, you can use old notebook)
• Operation system: CentOS 6, RHEL 6 or Scientific Linux 6
• One external or internal IP address
• Internet connection (only for downloading packages and templates)
• One hour of free time
19. OpenVZ – additional tools
• vzctl destroy – remove container with all data
• vzctl stop – container stop
• vzlist –a – list of all available containers on
host