Difference between revisions of "Sandbox"

From Linux-VServer

Jump to: navigation, search
Line 1: Line 1:
 
 
 
== General ==
 
== General ==
  
{{Question
+
Question
 
|Question=What is a 'Guest'?
 
|Question=What is a 'Guest'?
 
||Details=To talk about stuff, we need some naming. The physical machine is called 'Host' and the 'main' context running the Host Distro is called 'Host Context'. The virtual machine/distro is called 'Guest' and basically is a Distribution (Userspace) running inside a 'Guest Context'.
 
||Details=To talk about stuff, we need some naming. The physical machine is called 'Host' and the 'main' context running the Host Distro is called 'Host Context'. The virtual machine/distro is called 'Guest' and basically is a Distribution (Userspace) running inside a 'Guest Context'.
|Signature=derjohn}}
+
|Signature=derjohn
  
  
{{Question
+
Question
 
|Question=What kind of Operating System (OS) can I run as guest?
 
|Question=What kind of Operating System (OS) can I run as guest?
 
||Details=With VServer you can only run Linux guests. The trick is that a guest does not run a kernel on its own (as XEN and UML do), it merely uses a virtualized host kernel-interface. VServer offers so called security contexts which make it possible to seperate one guest from each other, i.e. they cannot get data from each other. Imagine it as a chroot environment with much more security and features.
 
||Details=With VServer you can only run Linux guests. The trick is that a guest does not run a kernel on its own (as XEN and UML do), it merely uses a virtualized host kernel-interface. VServer offers so called security contexts which make it possible to seperate one guest from each other, i.e. they cannot get data from each other. Imagine it as a chroot environment with much more security and features.
|Signature=derjohn}}
+
|Signature=derjohn
  
 
== Resources usage ==
 
== Resources usage ==
  
{{Question
+
Question
 
|Question=Resource sharing?
 
|Question=Resource sharing?
 
||Details=Yes ....
 
||Details=Yes ....
 
* memory: Dynamically.
 
* memory: Dynamically.
 
* CPU usage: Dynamically (token bucket)
 
* CPU usage: Dynamically (token bucket)
|Signature=derjohn}}
+
|Signature=derjohn
  
{{Question
+
Question
 
|Question=Resource limiting?
 
|Question=Resource limiting?
 
||Details=You can put limits per guest on different subsystems.
 
||Details=You can put limits per guest on different subsystems.
Line 30: Line 28:
 
* disk space usage : see [[Disk Limits and Quota]]
 
* disk space usage : see [[Disk Limits and Quota]]
 
Note that you can only offer guaranteed resource availability with some ticks at the time.
 
Note that you can only offer guaranteed resource availability with some ticks at the time.
|Signature=derjohn&xm}}
+
|Signature=derjohn&xm
  
 
== Title ==
 
== Title ==
 
Content
 
Content

Revision as of 11:01, 4 September 2008

General

Question |Question=What is a 'Guest'? ||Details=To talk about stuff, we need some naming. The physical machine is called 'Host' and the 'main' context running the Host Distro is called 'Host Context'. The virtual machine/distro is called 'Guest' and basically is a Distribution (Userspace) running inside a 'Guest Context'. |Signature=derjohn


Question |Question=What kind of Operating System (OS) can I run as guest? ||Details=With VServer you can only run Linux guests. The trick is that a guest does not run a kernel on its own (as XEN and UML do), it merely uses a virtualized host kernel-interface. VServer offers so called security contexts which make it possible to seperate one guest from each other, i.e. they cannot get data from each other. Imagine it as a chroot environment with much more security and features. |Signature=derjohn

Resources usage

Question |Question=Resource sharing? ||Details=Yes ....

  • memory: Dynamically.
  • CPU usage: Dynamically (token bucket)

|Signature=derjohn

Question |Question=Resource limiting? ||Details=You can put limits per guest on different subsystems.

  • using ulimits and rlimits (rlimit is a new feature of kernel 2.6/vs2.0.) per guest, to limit the memory consumption, the number of processes or file-handles, ... : see Resource Limits
  • CPU usage : see CPU Scheduler
  • disk space usage : see Disk Limits and Quota

Note that you can only offer guaranteed resource availability with some ticks at the time. |Signature=derjohn&xm

Title

Content

Personal tools