If you are living on the bleeding edge, get vzctl sources from git. Then run autogen.sh to recreate auto* files:
git clone <nowiki>githttps://gitsrc.openvz.org/pubscm/ovzl/vzctl.git</nowiki>
cd vzctl
./autogen.sh
# make install
=== FAQ ===
# 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] == 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.# You can=== <code>vzctl enter</code> doesn't work === You see this when trying to use <code>vzctl enter in CT and vzctl returns en error about pty</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]]
