We currently migrate to MediaWiki from our old installation, but not all content has been migrated yet. Take a look at the Wiki Team page for instructions how to help or browse through our new wiki at wiki.linux-vserver.org to find the information already migrated.

VServer Release FAQ

Q. How does the Versioning work?

A. Since version 1.00 the versioning is similar to the kernel versioning scheme. Even numbered releases (a.Xz with even X) are stable, reasonably well tested and expected not to change feature-wise. Odd numbered (a.Y.z with odd Y) releases are development releases. The last digit/number (z) is a subversion identifier. Experimental versions and Release Candidates might add a fourth identifier to that scheme.

Q. What is a Stable vs. a Development Release?

A. Basically the stable (2.Xz) and development (2.Y.z) releases should be similar in functionality for Y = X+1, but the development releases will include features and enhancements not present in the stable branch. Once those features mature (and get well tested ;), they will be incorporated by the stable branch.

For example the first stable release (1.00) uses two systemcalls as the previous releases did. However, the vserver system calls have been changed in the first development release (1.1.0). Linus assigned the vserver project a single system call, so a System Call Switch has been implemented. Running a development release usually requires using recent (latest) tools from the util-vserver development branch.

Q. What Branch do I need for which Kernel?

A. 1.Xz, and 1.Y.z releases are for the 2.4 kernels, while 1.9.x (obsoleted by now), and 2.X.y releases are for the 2.6 series.

Q. What features are supported in which branch/release?

A. The following matrix tries to give an overview

Feature 1.00 1.20 1.2.10 1.3.8 0.09 1.9.0 1.9.2 2.0 2.1
Legacy Kernel API (vs1.2x) YES YES YES part part part part part part
Legacy Proc Filesystem YES YES YES part part part part part part
Immutable Link Invert YES YES YES YES YES YES YES YES YES
Initpid and Fakeinit YES YES YES YES yes yes YES YES YES
Syscall Command Switch - YES YES YES YES YES YES YES YES
Syscall vkill commands - yes yes YES YES YES YES YES YES
Syscall rlimit commands - YES YES YES YES YES YES YES YES
Syscall ctx_wait support - - - - - - - YES YES
Syscall iattr commands - - - YES YES YES YES YES YES
Syscall namespace commands - - - YES YES YES YES YES YES
Syscall context flags - - - - YES YES YES YES YES
Syscall context caps - - - - YES YES YES YES YES
Syscall scheduler tuning - - - - - YES YES YES YES
Syscall 32bit compat - - - - - - - YES YES
Next gen. Proc Filesystem - - - YES YES YES YES YES YES
Chroot Barrier Flag - - - YES YES YES YES YES YES
Proc Security Flags - - yes YES YES YES YES YES YES
Userspace Reboot Helper - yes yes YES YES YES YES YES YES
Userspace Startup/Shutdown Helper - - - - - - - YES YES
VRoot Device - YES YES YES - - - YES YES
Advanced IP Selection - - - YES YES YES YES YES YES
Advanced uts_name config - - - YES YES YES YES YES YES
Fake Memory Display - - - - YES YES YES YES YES
Hard CPU limits - - - - - YES YES YES YES
Context File Tagging - - - - - YES YES YES YES
Context ID Propagation - - - - - - - - YES
NFS based File Tagging - - - - - - yes YES YES
Per Context Disk Limits - - - - - - YES YES YES
Network Context Support - - - - - YES YES YES YES
Socket Accounting - - - - - YES YES YES YES
Advanced Sysctl Debug System - - - - - - YES YES YES
Extended proc/devpts Security - - - - - - YES YES YES
Flag: Pause Context - - - - - YES YES YES YES
Flag: Hide proc/mounts - - - - - YES YES YES YES
CCap: Secure Mount - - - - - YES YES YES YES
CCap: Change host/domainname - - - - - YES YES YES YES
CCap: Modify rlimits - - - - - YES YES YES YES
CCap: Raw ICMP for Ping - - - - - - YES YES YES
Bind Mount Extensions - - - - - - - - YES
Copy on Write Link Breaking - - - - - - - - YES
Quota Hashes - - - - - - - - YES
Persistent Context Support - - - - - - - - YES