Changes

===== How does OpenVZ improve efficiency of servicesSo what is Virtuozzo? =====Virtuozzo is a Linux based virtualization platform, combining container and hypervisor virtualization, into a single product. While primarily built for service providers to run cloud services and applications, it is used by variety of businesses, including MSP, SMB and Enterprises.

For existing hardware, ===== What is OpenVZ allows and how it compares to utilize its processing power better by improving average load from 3-5% to at least 30-50%, while still providing ability to handle peak loadsVirtuozzo? =====OpenVZ is a free and opensource portion of Virtuozzo. To decrease complexityIt includes core of Virtuozzo functionality, OpenVZ provides standardized like kernel and centralized server command line management, logically decoupled from actual hardwaretools for creating and managing containers. And when its time to buy new serversVirtuozzo includes everything that OpenVZ does, you can now use few more powerful servers instead of many little ones — plus additional features and services available with added benefits of better reliability, better peak performance and typically longer lifespanthe commercial version only.

===== How does Virtuozzo 7/OpenVZ improve flexibility of services? pair compares to its predecessor (Virtuozzo versions 4.x and 6/OpenVZ) =====Previously, OpenVZ and Virtuozzo were built out of the same code base with some unique patches applied. That warranted the user interfaces to be similar but not identical. With Virtuozzo 7, the compatibility will be on the binary level - effectively the open source components will be the same between OpenVZ and Virtuozzo.

By providing unified scalable platform with such unique features as rapid application and updates provisioning. Each container is hardware independent and can ===== How OpenVZ users will benefit from it? =====OpenVZ components will be moved to another OpenVZ-based system in seconds over undergoing the network. This allows for ease of hardware maintenance (move out all containers and do whatever you need with same testing procedures as the box) and improved availability (keep a synchronized copy of your container elsewhere and start it up when primary service failed)commercial product. If your old box is not able to cope with peak load anymoreAlso, just move your containers to a some new onefeatures previously available on Virtuozzo only (notably hypervisor) will become available on the product built for OpenVZ community users.

===== What is a performance overheadsupport options are available for Virtuozzo 7? =====For the moment, only preview (beta) versions of Virtuozzo 7 are available. They are intended for development and testing only, not for production. Virtuozzo 7 is not yet commercially supported. For supported commercial version, please refer to [http://www.odin.com/products/virtuozzo/ Virtuozzo 6].

Near zero. There is no emulation layer, only security isolation, and all checking is done on the kernel level without context switching===== Why I need Virtuozzo/OpenVZ when LXC exist? =====See our [[comparison]] of different virtualization solutions.

===== What are performance expectationsWhen OpenVZ will be in upstream kernel? =====Our kernel developers [http://openvz.org/File:Kernel_patches_stats.png work hard] to merge containers functionality into the upstream Linux kernel, making OpenVZ team the biggest contributor to Linux Containers (LXC) kernel, with features such as PID and network namespaces, memory controller, checkpoint-restore and much more.

:Aside from this wiki, which contains lots of information, you can check extensive [[Man|manual pages]] and [http://docs.openvz.org Virtuozzo documentation].

== Installation and upgrade === Who needs OpenVZ? How it can be used? =====:See [[Use cases]].

===== What hardware How scalable is supported by OpenVZ kernel? =====:See [http://www.parallels.com/en/products/virtuozzo/hcl/ Virtuozzo HCL].

===== Why there are different OpenVZ technology scales as well as standard Linux kernel flavours available — up to thousands of CPUs and what do they mean? =====:See terabytes of RAM. Read more about [[Different kernel flavors (UP, SMP, ENTERPRISE, ENTNOSPLIT)WP/Containers_density|OpenVZ containers density]] and [[performance]].

==Installation and upgrade === How do I rebuild the kernel? =====:See [[Kernel build]].

===== What does 021stab018 in How to install OpenVZ kernel version mean? =====:See [[Kernel versioning]].

===== How can I check package signatures? =====There are two versions of OpenVZ available:See [[Package signatures]].

===== Is it possible to run x86 container * [[Roadmap|stable version]]: OpenVZ legacy (based on a x86_64 arch? =====RHEL5 and RHEL6 kernels).* [[Roadmap|development version]]:Sure :) We actually did some work on that to enable migration of x86 container from x86 to x86_64 and back, and to enable using 32-bit iptables in 32bit container [[Virtuozzo]] Linux distribution based on an x86_64 systemRHEL7 kernel.

== Networking == ===== How do I set up VPN for a container? =====:See [[VPN via the TUN/TAP device]]. ===== What hardware is veth and how do I use it? =====:See [[Virtual Ethernet device]]. ===== Why doesn't net-snmpd work on my containerssupported by OpenVZ kernel? =====:See [[SNMPD in container]]. ===== Can I use private IPs for my containers? =====https:See [[NAT]]. == User Beancounters (UBC) == ===== What are those User Beancounters? =====See [[UBC]]. ===== What units are UBC parameters measured in? =====See [[UBC parameter units]]. ===== How do I set up a container which is able to get X Mb of RAM? =====See [[Setting UBC parameters]]. ===== I can not start a program in container: it reports out of memory. What do I do? =====See [[Resource_shortage]]. ===== How can I reset <code>failcnt</code> in <code>/proc/user_beancounters</code>? =====See [[UBC failcnt reset]]hardware. == Troubleshooting ======= My kernel crashedredhat. What should I do? =====:See [[When you have an oops]com/ RHEL Hardware Compatibility List].

===== I see a lot of processes in D state. What does that meanHow existing OpenVZ users can upgrade to the [[Virtuozzo|new version]]? =====:See While there is no in-place upgrade, we prepared [[Processes in D stateUpgrade_script_from_OpenVZ_to_Virtuozzo_7|upgrade script]]for OpenVZ users to move their containers to the new platform. The script allows to transfer containers from old to new OpenVZ version (or from OpenVZ to Virtuozzo).