Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

Linux-VServer

From Wikipedia, the free encyclopedia
(Redirected fromVserver)
OS-level virtualisation
This article has multiple issues. Please helpimprove it or discuss these issues on thetalk page.(Learn how and when to remove these messages)
icon
This articlerelies excessively onreferences toprimary sources. Please improve this article by addingsecondary or tertiary sources.
Find sources: "Linux-VServer" – news ·newspapers ·books ·scholar ·JSTOR
(May 2014) (Learn how and when to remove this message)
This article includes alist of references,related reading, orexternal links,but its sources remain unclear because it lacksinline citations. Please helpimprove this article byintroducing more precise citations.(January 2014) (Learn how and when to remove this message)
(Learn how and when to remove this message)
Linux-VServer
Linux-VServer
DeveloperHerbert Pötzl (Community Project)
Stable release
2.6.22.19-vs2.2.0.7 / March 14, 2008; 17 years ago (2008-03-14)
Preview release
4.9.159-vs2.3.9.8 / October 5, 2019; 6 years ago (2019-10-05)
Operating systemLinux
Platformx86,SPARC/64,PA-RISC,s390x,MIPS/64,ARM,PowerPC/64,Itanium
TypeOS-level virtualization
LicenseGNU GPL v.2
Websitelinux-vserver.at
Repository

Linux-VServer is avirtual private server implementation that was created by addingoperating system-level virtualization capabilities to theLinux kernel. It is developed and distributed asopen-source software.

Details

[edit]

The project was started byJacques Gélinas. It is now maintained by Herbert Pötzl. It is not related to theLinux Virtual Server project, which implements networkload balancing.

Linux-VServer is ajail mechanism in that it can be used to securely partition resources on a computer system (such as thefile system, CPU time, network addresses and memory) in such a way thatprocesses cannot mount adenial-of-service attack on anything outside their partition.

Each partition is called asecurity context, and the virtualized system within it is thevirtual private server. Achroot-like utility for descending into security contexts is provided. Booting a virtual private server is then simply a matter of kickstartinginit 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 manyLinux distributions unmodified, includingDebian andFedora.

Virtual private servers are commonly used inweb hosting services, where they are useful for segregating customer accounts, pooling resources and containing any potential security breaches. To save space on such installations, each virtual server's file system can be created as a tree ofcopy-on-writehard links to a "template" file system. The hard link is marked with a special filesystem attribute and when modified, is securely and transparently replaced with a real copy of the file.

Linux-VServer provides two branches, stable (2.2.x), and devel (2.3.x) for 2.6-series kernels and a single stable branch for 2.4-series. A separate stable branch integrating thegrsecurity patch set is also available.

Since December 2025 the original website is under the control of a shady individual impersonating the current Linux-VServer maintainer and promoting (fictional?) Mobile Device Management software while instead collecting eMail addresses. Unfortunately this was possible because the domain expired after the death of Jacques Gélinas and nobody noticed.

Advantages

[edit]
  • Virtual servers share the samesystem call interface and do not have anyemulation overhead.
  • Virtual servers do not have to be backed by opaquedisk images, 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, although memory ballooning and modern VMs allow returning unused memory and sharing disk cache with the host and other virtual servers.
  • Processes within the virtual server are queued on the same scheduler as on the host, allowing guest's processes to run concurrently onSMP systems. This is not trivial to implement with whole-system emulation.
  • 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.
  • Rich Linux scheduling features such as real-time priorities.

Disadvantages

[edit]
  • Requires that the host kernel be patched.
  • Noclustering orprocess migration capability is included, so the host kernel and host computer is still a single point of failure for all virtual servers.
  • Networking is based on isolation, not virtualization. This prevents each virtual server from creating its own internal routing or firewalling setup.
  • Some system calls (mostly hardware-related: e.g.real-time clock) and parts of the/proc and/sys filesystems are left unvirtualized.
  • Does not allow disk I/O bandwidth to be allocated on a per-virtual server basis.

See also

[edit]

References

[edit]

External links

[edit]
Hardware
(hypervisors)
Native
Hosted
Specialized
Independent
Tools
Operating
system
OScontainers
Application containers
Virtual kernel architectures
Related kernel features
Orchestration
Desktop
Application
Network
See also
Organization
Kernel
Support
People
Technical
Debugging
Startup
ABIs
APIs
Kernel
System Call
Interface
In-kernel
Userspace
Daemons,
File systems
Wrapper
libraries
Components
Variants
Virtualization
Adoption
Range
of use
Adopters
Retrieved from "https://en.wikipedia.org/w/index.php?title=Linux-VServer&oldid=1339146373"
Categories:
Hidden categories:

[8]ページ先頭

©2009-2026 Movatter.jp