Editing Vzctl for upstream kernel

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:
{{DISPLAYTITLE: vzctl for upstream kernel}}
 
 
 
'''This article describes using OpenVZ tool vzctl as an alternative to LXC tools.'''
 
'''This article describes using OpenVZ tool vzctl as an alternative to LXC tools.'''
  
 
Recent vzctl releases (starting from version 4.0) can be used with upstream (non-OpenVZ) Linux kernels (that essentially means any recent 3.x kernel). At the moment, it provides just basic functionality.
 
Recent vzctl releases (starting from version 4.0) can be used with upstream (non-OpenVZ) Linux kernels (that essentially means any recent 3.x kernel). At the moment, it provides just basic functionality.
It is currently possible to create, start and stop a container with the same steps as one would use for a normal OpenVZ container. Other features may be present with limited functionality, while some are not present at all. We appreciate all bug reports, please file to [http://bugzilla.openvz.org/enter_bug.cgi?component=vzctl bugzilla].
+
It is currently possible to create and start a container with the same steps as one would use for a normal OpenVZ container. Other features may be present with limited functionality, while some are not present at all. We appreciate all bug reports, please file to [http://bugzilla.openvz.org/enter_bug.cgi?component=vzctl bugzilla].
  
 
Running vzctl on upstream kernels is considered an experimental feature. See [[#Limitations]] below.
 
Running vzctl on upstream kernels is considered an experimental feature. See [[#Limitations]] below.
Line 110: Line 108:
 
If you are living on the bleeding edge, get vzctl sources from git. Then run autogen.sh to recreate auto* files:
 
If you are living on the bleeding edge, get vzctl sources from git. Then run autogen.sh to recreate auto* files:
  
  git clone <nowiki>https://src.openvz.org/scm/ovzl/vzctl.git</nowiki>
+
  git clone <nowiki>git://git.openvz.org/pub/vzctl</nowiki>
 
  cd vzctl
 
  cd vzctl
 
  ./autogen.sh
 
  ./autogen.sh
Line 133: Line 131:
  
 
  # make install
 
  # make install
 
vzctl is also bundled in some Linux distributions, so you can install vzctl using native distro tools (i.e. your package manager):
 
 
* vzctl in [https://launchpad.net/ubuntu/+source/vzctl Ubuntu Linux] [https://help.ubuntu.com/community/OpenVZ Description]
 
* vzctl-core in [https://apps.fedoraproject.org/packages/vzctl-core Fedora Linux] [https://fedoraproject.org/wiki/QA:Testcase_vzctl_base Description]
 
* sys-cluster/vzctl in [http://packages.gentoo.org/package/sys-cluster/vzctl Gentoo Linux]
 
* vzctl in [https://packages.debian.org/search?keywords=vzctl Debian Linux]
 
* vzctl in [http://packages.altlinux.org/vzctl ALT Linux] ([http://altlinux.org/OpenVZ description])
 
 
== Known issues and workarounds ==
 
 
=== A container doesn't boot and udevd is in a process list ===
 
udev doesn't work, because <code>uevent</code>s are not virtualized yet. If you don't know how to disable it, you can remove the udev package.
 
 
=== <code>vzctl enter</code> doesn't work ===
 
 
You see this when trying to use <code>vzctl enter</code>:
 
 
Unable to open pty: No such file or directory
 
 
If a CT is executed in a user namespace, devpts must be mounted with the newinstance option. You can add this option in container's <code>/etc/fstab</code> file.
 
 
== See also ==
 
 
* [[OpenVZ with upstream kernel]]
 

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)

Templates used on this page: