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.

Syscall Switch

Starting with c17g the new syscall switch is in place.

Instead of creating a number of new syscalls, this uses a single syscall (sys_vserver) for several purposes (functions).

An overview of the current status/assignment is given in the [Syscall Matrix V2.8]
(older versions: [V2.7][V2.6][V2.4][V2.3][V2.2][V2.1][V2.0])

Syscall Numbers

depending on the architecture, the sys_vserver syscall was assigned a specific syscall number:

arch number maintainer
x86_64 236 [Andi Kleen]
s390 263 [Martin Schwidefsky]
sparc/64 267 [David S.Miller]
i386 273 [Rik/Linus/Andrew]
sh 273 [Kazumoto Kojima]
ppc/64 257 [Benjamin Herrenschmidt]
mips o32 277 [Ralf Baechle]
mips N64 236 [Ralf Baechle]
mips N32 240 [Ralf Baechle]
m68k 278 [Geert Uytterhoeven]
h8300 273 [Yoshinori Sato]
alpha 428 [Richard Henderson]
ia64 1269 [David Mosberger]
arm/arm26 313 [Russell M.King]
sh64 301 [Paul Mundt?]
cris 273 [??]
frv 273 [??]
m32r 273 [??]
hppa/64 263 [Grant Grundler]

Syscall Return Codes

sys_vserver syscall command return codes, and what they mean:

name cmd explanation
EPERM * Operation not permitted
ENOENT * No such file or directory
ESRCH * No such process or context
ENXIO * No such device or address
ENOMEM * Out of memory
EACCES * Permission denied (file/context)
EFAULT * Bad address (user/kernel mapping)
ENOTBLK * Block device required
EBUSY * Device or resource busy
EEXIST * File or context exists
ENODEV * No such device
ENOTDIR * Not a directory
EISDIR * Is a directory
EINVAL * Invalid argument
ENOTTY * Not a typewriter/Not supported
EROFS * Read-only file system
EDEADLK * Resource deadlock would occur
ENOSYS * Function not implemented

Reserved Experimental/Test Commands

For those calls the CATEGORY is fixed to 61

Simulators and Emulators

... to test the various implementations: