Content deleted Content added
No edit summary |
Guy Harris (talk | contribs) I've no idea whose invention "S390/X" is, but, unlike the other XXX/64, which at least suggest that it's the 64-bit version of XXX, "S390/X" doesn't do that. "s390x" does, at least in the context of Linux. And, if it's 64-bit, link to z/Architecture, which is the name for the 64-bit version of System/3x0, not to anythign 32-bit. |
||
(31 intermediate revisions by 24 users not shown) | |||
Line 1:
{{Short description|OS-level virtualisation}}
{{multiple|
{{primary sources|date=May 2014}}
{{Citations|date=January 2014}}
}}
{{Infobox software
| name =
| logo = [[Image:Linux-VServer-logo.png|Linux-VServer]]
| screenshot =
| caption =
| developer = Herbert Pötzl (Community Project)
| latest release version = 2.6.22.19-vs2.2.0.7
| latest release date = {{start date and age|2008|03|14}}
| latest preview version = 4.9.159-vs2.3.9.8
| latest preview date = {{start date and age|2019|10|05}}
| operating_system = [[Linux]]
| platform = [[x86
| genre = [[Operating system-level virtualization|OS-level virtualization]]
| license = [[GNU General Public License|GNU GPL]] v.2
| website =
}}
'''Linux-VServer''' is a [[virtual private server]] implementation that was created by adding [[operating system-level virtualization]] capabilities to the [[Linux kernel]]. It is developed and distributed as [[open-source software]].
==Details==
The project was started by [[Jacques Gélinas]]. It is now maintained by Herbert Pötzl.
Linux-VServer is a [[
Each partition is called a ''security context'', and the virtualized system within it is the ''virtual private server''. A [[chroot]]-like utility for descending into security contexts is provided. Booting a virtual private server is then simply a matter of kickstarting [[init]] in a new security context; likewise, shutting it down simply entails killing all processes with that security context. The contexts themselves are robust enough to boot many [[Linux distribution]]s unmodified, including [[Debian]] and [[Fedora (operating system)|Fedora]].
Line 28 ⟶ 37:
* Virtual servers share the same [[system call]] interface and do not have any [[emulator|emulation]] overhead.
* Virtual servers do not have to be backed by opaque [[disk image]]s, but can share a common file system and common sets of files (through copy-on-write hard links). This makes it easier to back up a system and to pool disk space amongst virtual servers.
* Processes within the virtual server run as regular processes on the host system. This is somewhat more memory-efficient and I/O-efficient than whole-system emulation,
* Processes within the virtual server are queued on the same scheduler as on the host, allowing
* Networking is based on isolation rather than virtualization, so there is no additional overhead for packets.
* Smaller plane for security bugs. Only one kernel with small additional code-base compared to 2+ kernels and large interfaces between them.
Line 42 ⟶ 51:
==See also==
{{Portal|Free and open-source software}}
* [[Comparison of platform
* [[Operating system-level virtualization]]
==References==
{{Reflist}}
==External links==
* {{Official website
* [http://www.13thfloor.at/vserver/project/ Official releases]
* [http://linux-vserver.org/Linux-VServer-Paper Implementation paper]
{{Virtualization software}}
{{Linux kernel}}
{{DEFAULTSORT:Linux-Vserver}}
Line 61 ⟶ 70:
[[Category:Linux kernel features]]
[[Category:Free virtualization software]]
[[Category:Linux-only free software]]
[[Category:Virtualization software for Linux]]
|