Changes

OpenVZ technology scales as well as standard ===== So what is Virtuozzo? =====Virtuozzo is a Linux kernel — up to thousands of CPUs based virtualization platform, combining container and terabytes of RAM. Besideshypervisor virtualization, into a single container could be scaled up from taking a little fraction of available resources up product. While primarily built for service providers to all resources available dynamically — you do not even have to restart the container. For examplerun cloud services and applications, containers can natively use up to all available CPUs which it is different from hypervisor technology which requires special tricks like co-scheduling used by variety of businesses, including MSP, SMB and even the best hypervisors are inefficient with more then 4-8 vCPUsEnterprises.

===== How does What is OpenVZ improve efficiency of servicesand how it compares to Virtuozzo? =====OpenVZ is a free and opensource portion of Virtuozzo. It includes core of Virtuozzo functionality, like kernel and command line management tools for creating and managing containers. Virtuozzo includes everything that OpenVZ does, plus additional features and services available with the commercial version only.

For existing hardware, ===== How does Virtuozzo 7/OpenVZ allows pair 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 loadspredecessor (Virtuozzo versions 4. To decrease complexityx and 6/OpenVZ) =====Previously, OpenVZ provides standardized and centralized server management, logically decoupled from actual hardwareVirtuozzo were built out of the same code base with some unique patches applied. And when its time That warranted the user interfaces to buy new serversbe similar but not identical. With Virtuozzo 7, you can now use few more powerful servers instead of many little ones — with added benefits of better reliability, better peak performance the compatibility will be on the binary level - effectively the open source components will be the same between OpenVZ and typically longer lifespanVirtuozzo.

===== How does OpenVZ improve flexibility of servicesusers will benefit from it? =====OpenVZ components will be undergoing the same testing procedures as the commercial product. Also, some new features previously available on Virtuozzo only (notably hypervisor) will become available on the product built for OpenVZ community users.

By providing unified scalable platform with such unique features as rapid application and updates provisioning. Each container is hardware independent and can be moved to another OpenVZ-based system in seconds over ===== What support options are available for Virtuozzo 7? =====For the network. This allows for ease of hardware maintenance moment, only preview (move out all containers and do whatever you need with the boxbeta) and improved availability (keep a synchronized copy versions of your container elsewhere Virtuozzo 7 are available. They are intended for development and start it up when primary service failed)testing only, not for production. If your old box Virtuozzo 7 is not able to cope with peak load anymoreyet commercially supported. For supported commercial version, just move your containers please refer to a new one[http://www.odin.com/products/virtuozzo/ Virtuozzo 6].

===== What is the performance overheadWhy I need Virtuozzo/OpenVZ when LXC exist? =====See our [[comparison]] of different virtualization solutions.

Near zero===== When OpenVZ will be in upstream kernel? =====Our kernel developers [http://openvz.org/File:Kernel_patches_stats. There is no emulation layerpng 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, only security isolationmemory controller, checkpoint-restore and all checking is done on the kernel level without context switchingmuch 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]]. ===== I see a lot of processes in D state. What does that mean? =====:See [[Processes in D state]]. ===== My container cannot access the internet. What should I do? ===== If you can ping the host node but receive an error similar to: <pre>[root@test com/RHEL Hardware Compatibility List]# ping 8.8.8.8PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.From 192.168.1.1 icmp_seq=1 Destination Host Prohibited</pre> then likely the host node has an active firewall. Running the command

<pre>===== How existing OpenVZ users can upgrade to the [[root@host ~Virtuozzo|new version]# /etc/init.d/iptables stop]? =====iptables: Flushing firewall rules: While there is no in-place upgrade, we prepared [ OK ]iptables: Setting chains to policy ACCEPT: filter [ OK Upgrade_script_from_OpenVZ_to_Virtuozzo_7|upgrade script]iptables: Unloading modules: [ OK ]</pre> will turn it offfor OpenVZ users to move their containers to the new platform. If that works, then you know iptables firewall needs The script allows to transfer containers from old to new OpenVZ version (or from OpenVZ to be configuredVirtuozzo).