Editing FAQ

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
−
{{Virtuozzo}}
 
−
 
 
== General ==
 
== General ==
 +
===== What is a container (Virtual Environment, Virtual Private Server, VPS, VE)? =====
 +
:See [[VE]]
  
−
===== So what is Virtuozzo? =====
+
===== Who needs OpenVZ? How it can be used? =====
−
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.
+
:See [[Use cases]]
  
−
===== What is OpenVZ and how it compares to Virtuozzo? =====
+
===== How is OpenVZ different from other technologies? =====
−
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.
+
:See [[Introduction to virtualization]]
  
−
===== How does Virtuozzo 7/OpenVZ pair compares to its predecessor (Virtuozzo versions 4.x and 6/OpenVZ) =====
+
===== How is OpenVZ updated and why it is secure? =====
−
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.
+
:See [[Security]]
  
−
===== How OpenVZ users will benefit from it? =====
+
===== I want to show my appreciation to OpenVZ and put some logo to my site. Where to get 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.
+
:See [[Artwork]]
  
−
===== What support options are available for Virtuozzo 7? =====
+
== Installation and upgrade ==
−
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].
 
  
−
===== Why I need Virtuozzo/OpenVZ when LXC exist? =====
+
===== What hardware is supported by OpenVZ kernel? =====
−
See our [[comparison]] of different virtualization solutions.
+
:See [http://www.swsoft.com/en/products/virtuozzo/hcl/ Virtuozzo HCL].
  
−
===== When OpenVZ will be in upstream kernel? =====
+
===== Why there are different kernel flavours available and what do they mean? =====
−
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.
+
:See [[Different kernel flavors (UP, SMP, ENTERPRISE, ENTNOSPLIT)]]
  
 +
===== How do I rebuild the kernel? =====
 +
:See [[Kernel build]]
  
−
===== I want to show my appreciation to OpenVZ and put some logo to my site. Where to get it? =====
+
===== What does 021stab018 in OpenVZ kernel version mean? =====
−
:See [[Artwork]].
+
:See [[Kernel versioning]]
 +
 
 +
===== How can I check package signatures? =====
 +
:See [[Package signatures]]
 +
 
 +
===== Is it possible to run x86 VPS on a x86_64 arch? =====
 +
:Sure :) We actually did some work on that to enable migration of x86 VE from x86 to x86_64 and back, and to enable using 32-bit iptables in 32bit VE on an x86_64 system.
 +
 
 +
===== What filesystems should I choose for saving my VEs? =====
 +
The safest choice is ext2/3 to save your VEs. Remember that ReiserFS is less stable than ext2/3.
 +
If you choose to use XFS, there will be no support for disk quota inside VEs.
 +
 
 +
== Networking ==
  
−
===== What kind of documentation is available? =====
+
===== How do I set up VPN for a VE? =====
 +
:See [[VPN via the TUN/TAP device]]
  
−
:Aside from this wiki, which contains lots of information, you can check extensive [[Man|manual pages]] and [http://docs.openvz.org Virtuozzo documentation].
+
===== What is veth and how do I use it? =====
 +
:See [[Virtual Ethernet device]]
  
−
===== Who needs OpenVZ? How it can be used? =====
+
===== Why doesn't net-snmpd work on my VEs =====
−
:See [[Use cases]].
+
:See [[SNMPD on VEs]]
  
−
===== How scalable is OpenVZ? =====
+
== User Beancounters ==
  
−
OpenVZ technology scales as well as standard Linux kernel — up to thousands of CPUs and terabytes of RAM. Read more about [[WP/Containers_density|OpenVZ containers density]] and [[performance]].
+
===== What are those User Beancounters? =====
 +
See [[UBC]].
  
−
== Installation and upgrade ==
+
===== What units are UBC parameters measured in? =====
 +
See [[UBC parameter units]]
  
−
===== How to install OpenVZ? =====
+
===== How do I set up a VE which is able to get X Mb of RAM? =====
 +
See [[Setting UBC parameters]].
  
−
There are two versions of OpenVZ available:
+
===== I can not start a program in VE: it reports out of memory. What do I do? =====
 +
See [[Resource_shortage]].
  
−
* [[Roadmap|stable version]]: OpenVZ legacy (based on RHEL5 and RHEL6 kernels).
+
===== How can I reset <code>failcnt</code> in <code>/proc/user_beancounters</code>? =====
−
* [[Roadmap|development version]]: [[Virtuozzo]] Linux distribution based on RHEL7 kernel.
+
See [[UBC failcnt reset]].
  
−
See [[Quick installation]]
+
== Troubleshooting ==
 +
===== My kernel crashed. What should I do? =====
 +
:See [[When you have an oops]]
  
−
===== What hardware is supported by OpenVZ kernel? =====
+
===== I see a lot of processes in D state. What does that mean? =====
−
:See [https://hardware.redhat.com/ RHEL Hardware Compatibility List].
+
:See [[Processes in D state]]
  
−
===== How existing OpenVZ users can upgrade to the [[Virtuozzo|new version]]? =====
+
===== Quick reference card for OpenVZ =====
−
While there is no in-place upgrade, we prepared [[Upgrade_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).
+
http://pronics.fi/~eero/mirrors/openvz-reference-card.pdf

Please note that all contributions to OpenVZ Virtuozzo Containers Wiki may be edited, altered, or removed by other contributors. If you don't want your writing to be edited mercilessly, then don't submit it here.
 If you are going to add external links to an article, read the External links policy first!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Template used on this page:

Retrieved from "https://wiki.openvz.org/FAQ"