Editing FAQ

== General ==
===== What is a container (Virtual Environment, Virtual Private Server, VPS, VE)? =====
:See [[Container]].

===== What are highlights of OpenVZ technology? =====
In short, OpenVZ is the only highly scalable virtualization technology with near-zero overhead, strong isolation and rapid customer provisioning that's ready for production use right now. Deployment of OpenVZ improves efficiency, flexibility and quality of service in the enterprise environment.

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

===== What applications can run inside an OpenVZ container? =====

Most of applications can be installed to a container without any modifications. Oracle, DB/2, Weblogic, Websphere and other big applications run just fine inside an OpenVZ container. Applications and services do not have to be aware of OpenVZ. However, direct access to hardware is not available by default.

===== How is OpenVZ different from other technologies? =====
:See [[Introduction to virtualization]].

===== How is OpenVZ updated and why it is secure? =====
:See [[Security]].

===== How scalable is OpenVZ? =====

OpenVZ technology scales up pretty well - we've tested it on machines up to 8 CPU and up to 64 GB of RAM. Besides, a single container could be scaled up from taking a little fraction of available resources up to all resources available dynamically - you do not even have to restart the container.

===== How OpenVZ improves efficiency of services? =====

For existing hardware, OpenVZ allows 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 loads. To decrease complexity, OpenVZ provides standardized and centralized server management, logically decoupled from actual hardware. And when its time to buy new servers, you can now use few more powerful servers instead of many little ones — with added benefits of better reliability, better peak performance and typically longer lifespan.

===== How OpenVZ improves flexibility of services? =====

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 the network. This allows for ease of hardware maintenance (move out all containers and do whatever you need with the box) and improved availability (keep a synchronized copy of your container elsewhere and start it up when primary service failed). If your old box is not able to cope with peak load anymore, just move your containers to a new one.

===== What is a performance overhead? =====

Near zero. There is no emulation layer, only security isolation, and all checking is done on the kernel level without context switching.

===== What are performance expectations? =====

Peak performance is achieved when only one container has active tasks. In this case, it could use 100% of available resources: all CPUs, all physical memory, all disk and network bandwidth. OpenVZ is not limiting you to a single-CPU virtual machine. 

===== I want to show my appreciation to OpenVZ and put some logo to my site. Where to get it? =====
:See [[Artwork]].

===== Are there any control panels available for OpenVZ? =====
:See [[Control_panels]].

== Installation and upgrade ==

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

===== Why there are different kernel flavours available and what do they mean? =====
:See [[Different kernel flavors (UP, SMP, ENTERPRISE, ENTNOSPLIT)]].

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

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

===== How can I check package signatures? =====
:See [[Package signatures]].

===== Is it possible to run x86 container on a x86_64 arch? =====
: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 on an x86_64 system.

===== What filesystems should I choose for saving my containers? =====
: Any filesystem which supports Unix style permissions is usable, such as Ext3 or ReiserFS. XFS works, but does not have support for disk quotas inside containers.

== Networking ==

===== How do I set up VPN for a container? =====
:See [[VPN via the TUN/TAP device]].

===== What is veth and how do I use it? =====
:See [[Virtual Ethernet device]].

===== Why doesn't net-snmpd work on my containers? =====
:See [[SNMPD in container]].

== 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]].

== Troubleshooting ==
===== My kernel crashed. 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]].

== Quick reference card for OpenVZ ==
{{PDFlink|[http://pronics.fi/~eero/mirrors/openvz-reference-card.pdf openvz-reference-card.pdf]}}