Since [[Download/Recent vzctl/4.0|releases (starting from version 4.0]], vzctl tool ) 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 start 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].

Running vzctl on upstream kernels is considered an experimental feature. See [[#LimitatonsLimitations]] below.

git clone git<nowiki>https://gitsrc.openvz.org/pubscm/ovzl/vzctl.git</nowiki>

Usual <code>./conficonfigure && make</code> should do. But you probably want to specify more options. It makes sense to: * enable cgroup support* add <code>--without-ploop</code> (unless you want [[ploop]] compiled it) because otherwise you will need ploop lib headers (available from [[Download/ploop]]).* enable bash completion support* set prefix to /usr See <code>./configure --help</code> output for more details and options available. So, the command will look like:  $ ./configure --with-cgroup --without-ploop --enable-bashcomp --prefix=/usr $ make -j4 === 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.

$ ./configure --* [[OpenVZ with-cgroup --without-ploopupstream kernel]]