Open main menu

OpenVZ Virtuozzo Containers Wiki β

Changes

FAQ

2,531 bytes removed, 10:18, 9 January 2021
Undo revision 23356 by 203.81.71.218 (talk)
{{Virtuozzo}}
 
== General ==
===== What is a container (Virtual Environment, Virtual Private Server, VPS, VE)? =====
:See [[Container]].
===== What are highlights of OpenVZ technologySo what is Virtuozzo? =====In short, OpenVZ Virtuozzo is the only highly scalable a Linux based virtualization technology with near-zero overheadplatform, strong isolation combining container and rapid customer provisioning that's ready hypervisor virtualization, into a single product. While primarily built for production use right now. Deployment service providers to run cloud services and applications, it is used by variety of OpenVZ improves efficiencybusinesses, flexibility including MSP, SMB and quality of service in the enterprise environmentEnterprises.
===== Who needs What is OpenVZ? How and how it can be usedcompares to Virtuozzo? =====:See [[Use cases]]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.
===== What applications can run inside an How does Virtuozzo 7/OpenVZ container? 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.
Most applications can be installed to a container without any modifications. Oracle, DB/2, Weblogic, Websphere and other big applications run just fine inside an ===== How OpenVZ users will benefit from it? =====OpenVZ container. Applications and services do not have to components will be aware of OpenVZundergoing the same testing procedures as the commercial product. HoweverAlso, direct access to hardware is not some new features previously available by defaulton Virtuozzo only (notably hypervisor) will become available on the product built for OpenVZ community users.
===== How is OpenVZ different from other technologiesWhat support 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:See [[Introduction to virtualization]//www.odin.com/products/virtuozzo/ Virtuozzo 6].
===== How is Why I need Virtuozzo/OpenVZ secured & updatedwhen LXC exist? =====:See our [[Securitycomparison]]of different virtualization solutions.
===== How scalable is When OpenVZwill 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.
OpenVZ technology scales as well as standard Linux kernel — up to thousands of CPUs and terabytes 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. For example, containers can natively use up to all available CPUs which is different from hypervisor technology which requires special tricks like co-scheduling and even the best hypervisors are inefficient with more then 4-8 vCPUs.
 
===== How does OpenVZ improve 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 does OpenVZ improve 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 the 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]]. [http://code.google.com/p/ovz-web-panel/ OVZ Web panel] is recommended.
===== What kind of documentation is available? =====
: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.
===== What filesystems should I choose for saving my containers? =====: Currently, ext4 is recommended. 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.See [[Quick installation]]
== 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 containers? =====:See [[SNMPD in container]]. ===== Can I use private IPs for my containerssupported by OpenVZ kernel? =====: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 containerhttps: 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]]hardware. ===== I see a lot of processes in D stateredhat. What does that mean? =====:See [[Processes in D state]com/ RHEL Hardware Compatibility List]. ===== My container cannot access the internet. What should I do? ===== If you can ping the host node but receive an error similar to: Destination Host Prohibited
then likely ===== How existing OpenVZ users can upgrade to the host node has an active firewall. Running [[Virtuozzo|new version]]? =====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 command /etc/initnew platform.d/iptables stop will turn it off. 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).
Anonymous user
Retrieved from "https://wiki.openvz.org/Special:MobileDiff/13051...23371"