1,734
edits
Changes
rename article
== Installation ==
=== Networking ===
{{Note|IP mode networking (--ipadd / --ipdel) is currently not supported}}
Networking is available through the switches <code>--netdev_add</code>, <code>--netif_add</code>, and their respective deletion counterparts.
Unfortunately now it requires some manual configuration.
== Bridged networking ==
The following example assumes
* you already have a bridge configured on the host system
* bridge interface name is virbr0
* CT is running Red Hat like distro (CentOS)
vzctl set $CTID --netif_add eth0,,,,virbr0 --save
echo "NETWORKING=yes" > /vz/private/$CTID/etc/sysconfig/network
After this, you can find CT IP mode networking (--ipadd / --ipdel) is currently not supported.using this: # ip netns exec $CTID ip address list
== Limitations ==
{{Note|We recommend using [[Download/kernel/rhel6|OpenVZ kernel]] for features, stability and security}} The following vzctl commands are not working at allwith the non-OpenVZ kernel:
* <code>quotaon</code>/<code>quotaoff</code>/<code>quotainit</code> (vzquota-specific)
* <code>convert</code>, <code>compact</code>, <code>snapshot*</code> (ploop-specific)
* <code>console</code> (needs a virtual /dev/console, /dev/ttyN device)
The following binaries are not ported to work on top of upstream kernel:
=== Resource management ===
* cpu.cfs_quota_us
* cpu.shares
* memory.kmem.tcp.limit_in_bytes
== Building ==
=== Dependencies ===
If you are living on the bleeding edge, get vzctl sources from git. Then run autogen.sh to recreate auto* files:
git clone git<nowiki>https://gitsrc.openvz.org/pubscm/ovzl/vzctl.git</nowiki>
cd vzctl
./autogen.sh
=== Compile ===
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] == 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.