http://wiki.linux-vserver.org/api.php?action=feedcontributions&user=84.157.69.20&feedformat=atomLinux-VServer - User contributions [en]2024-03-29T09:14:20ZUser contributionsMediaWiki 1.20.2http://wiki.linux-vserver.org/DocumentationDocumentation2008-09-03T10:07:41Z<p>84.157.69.20: /* Guides and Howtos */</p>
<hr />
<div><div style="margin: 2em auto 2em auto; padding: 10px; background-color: #F9ECCD; border: 1px solid #004433; text-align: center;"><br />
[[Image:Icon-Caution.png|left]]<br />
We are currently migrating to MediaWiki from our old system, but not all content has been migrated yet. Take a look at the [[Wiki Team]] page for instructions how to help or look at the [http://oldwiki.linux-vserver.org old wiki] to find the information not migrated yet.<br />
<br />
'''To ease migration we created a [[List of old Documentation pages]].'''<br />
</div><br />
<br />
== Introduction ==<br />
<br />
* [[Overview|Virtualization Overview]]<br />
* [[Usage Scenarios]]<br />
* [[Feature Matrix]]<br />
<br />
== Installation ==<br />
<br />
* [[Installation Considerations]]<br />
* [[Installation on Linux 2.6]]<br />
* [[Installation on ArchLinux]]<br />
* [[Installation on CentOS]]<br />
* [[Installation on Debian]]<br />
* [[Installation on Fedora]]<br />
* [[Installation on Gentoo]]<br />
* [[Installation on Mandrake]]<br />
* [http://pld-linux.org/Vserver Installation on PLD-Linux]<br />
* [[Installation on Redhat]]<br />
* [[Installation on Slackware]]<br />
* [[Installation on SuSE/OpenSUSE]]<br />
* [[Installation on Ubuntu]]<br />
<br />
== Configuration ==<br />
<br />
* [[util-vserver:Documentation|util-vserver Documentation]]<br />
* [[vcd:Documentation|VServer Control Daemon Documentation]]<br />
* [[Share a directory among multiple guests]]<br />
<br />
== Guides and Howtos ==<br />
<br />
* [[Building Guest Systems]]<br />
* [[util-vserver:Howto virtualize an exisiting Linux server|Howto virtualize an existing Linux server]]<br />
* [[VCMD HowTo]]<br />
* [[Howto make bsd-style init sysv-compatible|Howto make Bsd-style init sysv-compatible (archlinux guest system)]]<br />
* [[Installing 32-bit Fedora on 64-bit Debian]]<br />
* [[Installing Ubuntu on Debian]]<br />
* [[Installing an openSUSE vserver guest]]<br />
* [[Networking vserver guests]]<br />
* [[Howto HostAuth]]<br />
* [[Fuse_GlusterFS| Fuse and GlusterFS]]<br />
* [[yum-patch|How to patch vyum]]<br />
* [[yum-upgrade-3.2.4|Upgrading existing installations to yum-3.2.4]]<br />
* [[Migrating from OpenVZ to Linux-Vserver]]<br />
<br />
== Lists &amp; Theory ==<br />
<br />
* Basic configuration<br />
** [[Capabilities and Flags]]<br />
** [[CPU Scheduler]]<br />
** [[Disk Limits and Quota]]<br />
** [[Resource Limits]]<br />
*** [[Memory Limits]]<br />
** [[Virtual System Information]]<br />
** [[Unification]]<br />
<br />
* Security Considerations<br />
** [[Secure Capabilities]]<br />
** [[Secure chroot Barrier]]<br />
** [[Secure Device Nodes]]<br />
** [[Secure ProcFS Entries]]<br />
<br />
* Performance and Stability<br />
** [[Virtualization Overhead]]<br />
<br />
* Implementation Details<br />
** [[Context Accounting]]<br />
** [[Filesystem Attributes]]<br />
** [[Filesystem Tagging]]<br />
** [[Filesystem Namespaces]]<br />
** [[Kernel Userspace Helper]]<br />
** [[Mainline Kernel Virtualization]]<br />
** [[ProcFS]]<br />
** [[Syscall Command Switch]]<br />
<br />
== External Resources ==</div>84.157.69.20http://wiki.linux-vserver.org/DocumentationDocumentation2008-09-03T10:07:23Z<p>84.157.69.20: /* Guides and Howtos */</p>
<hr />
<div><div style="margin: 2em auto 2em auto; padding: 10px; background-color: #F9ECCD; border: 1px solid #004433; text-align: center;"><br />
[[Image:Icon-Caution.png|left]]<br />
We are currently migrating to MediaWiki from our old system, but not all content has been migrated yet. Take a look at the [[Wiki Team]] page for instructions how to help or look at the [http://oldwiki.linux-vserver.org old wiki] to find the information not migrated yet.<br />
<br />
'''To ease migration we created a [[List of old Documentation pages]].'''<br />
</div><br />
<br />
== Introduction ==<br />
<br />
* [[Overview|Virtualization Overview]]<br />
* [[Usage Scenarios]]<br />
* [[Feature Matrix]]<br />
<br />
== Installation ==<br />
<br />
* [[Installation Considerations]]<br />
* [[Installation on Linux 2.6]]<br />
* [[Installation on ArchLinux]]<br />
* [[Installation on CentOS]]<br />
* [[Installation on Debian]]<br />
* [[Installation on Fedora]]<br />
* [[Installation on Gentoo]]<br />
* [[Installation on Mandrake]]<br />
* [http://pld-linux.org/Vserver Installation on PLD-Linux]<br />
* [[Installation on Redhat]]<br />
* [[Installation on Slackware]]<br />
* [[Installation on SuSE/OpenSUSE]]<br />
* [[Installation on Ubuntu]]<br />
<br />
== Configuration ==<br />
<br />
* [[util-vserver:Documentation|util-vserver Documentation]]<br />
* [[vcd:Documentation|VServer Control Daemon Documentation]]<br />
* [[Share a directory among multiple guests]]<br />
<br />
== Guides and Howtos ==<br />
<br />
* [[Building Guest Systems]]<br />
* [[util-vserver:Howto virtualize an existing Linux server|Howto virtualize an existing Linux server]]<br />
* [[VCMD HowTo]]<br />
* [[Howto make bsd-style init sysv-compatible|Howto make Bsd-style init sysv-compatible (archlinux guest system)]]<br />
* [[Installing 32-bit Fedora on 64-bit Debian]]<br />
* [[Installing Ubuntu on Debian]]<br />
* [[Installing an openSUSE vserver guest]]<br />
* [[Networking vserver guests]]<br />
* [[Howto HostAuth]]<br />
* [[Fuse_GlusterFS| Fuse and GlusterFS]]<br />
* [[yum-patch|How to patch vyum]]<br />
* [[yum-upgrade-3.2.4|Upgrading existing installations to yum-3.2.4]]<br />
* [[Migrating from OpenVZ to Linux-Vserver]]<br />
<br />
== Lists &amp; Theory ==<br />
<br />
* Basic configuration<br />
** [[Capabilities and Flags]]<br />
** [[CPU Scheduler]]<br />
** [[Disk Limits and Quota]]<br />
** [[Resource Limits]]<br />
*** [[Memory Limits]]<br />
** [[Virtual System Information]]<br />
** [[Unification]]<br />
<br />
* Security Considerations<br />
** [[Secure Capabilities]]<br />
** [[Secure chroot Barrier]]<br />
** [[Secure Device Nodes]]<br />
** [[Secure ProcFS Entries]]<br />
<br />
* Performance and Stability<br />
** [[Virtualization Overhead]]<br />
<br />
* Implementation Details<br />
** [[Context Accounting]]<br />
** [[Filesystem Attributes]]<br />
** [[Filesystem Tagging]]<br />
** [[Filesystem Namespaces]]<br />
** [[Kernel Userspace Helper]]<br />
** [[Mainline Kernel Virtualization]]<br />
** [[ProcFS]]<br />
** [[Syscall Command Switch]]<br />
<br />
== External Resources ==</div>84.157.69.20http://wiki.linux-vserver.org/Installation_ConsiderationsInstallation Considerations2008-09-03T09:37:03Z<p>84.157.69.20: /* Disk Partitioning */</p>
<hr />
<div>This guide will give you an idea about pre-requesites and installation considerations of the host system. It is targeted towards production systems, so some of the information provided here may or may not be important to your setup. Decide for your own demand.<br />
<br />
== Hardware Compatibility ==<br />
<br />
The Linux-VServer kernel runs on many platforms, including those listed below:<br />
<br />
* alpha<br />
* arm<br />
* ia64<br />
* m68k<br />
* mips<br />
* ppc<br />
* ppc64<br />
* s390<br />
* sparc<br />
* sparc64<br />
* x86<br />
* x86_64<br />
<br />
See [[Tested Configurations]] for details.<br />
<br />
== Hardware Availability ==<br />
<br />
The host system availability is more critical than the availability of a typical server. Since it runs multiple Virtual Private Servers providing a number of critical services each, the outage of the host system may be very costly. Additionally outage can be as disastrous as the simultaneous outage of a number of servers running critical services.<br />
<br />
Discussing all aspects of high-availability is out of the scope of this document, however the following considerations should be followed to have a clean and secure host system:<br />
<br />
* Use RAID storage for guest filesystems.<br />
* Do not run software on the host system. Instead create guest systems where you can host necessary services. The only needed service on the host system is probably sshd.<br />
* Do not create users on the host system. You can create as many users as you need in any guest system.<br />
<br />
== Hardware Requirements ==<br />
<br />
The exact hardware configuration depends on how many Virtual Private Servers you are going to run on the computer and what load these VPSs are going to produce. Thus, in order to choose the right configuration, you should follow the recommendations below:<br />
<br />
; CPUs<br />
: The more Virtual Private Servers you plan to run simultaneously, the more CPUs you need.<br />
<br />
; Memory<br />
: The more memory you have, the more Virtual Private Servers you can run. The exact figure depends on the number and nature of applications you are planning to run in your Virtual Private Servers. However, on the average, at least 1 GB of RAM is recommended for every 20-30 Virtual Private Servers<br />
<br />
; Disk space<br />
: Each Virtual Private Server occupies 10–500 MB of hard disk space for system files (depends on the use of [[Unification]]) in addition to the user data inside the Virtual Private Server (for example, web site content). You should consider it when planning disk partitioning and the number of Virtual Private Servers to run.<br />
<br />
== Choose Your Distribution ==<br />
<br />
There are many different Linux distributions, or versions. A distribution is the compiled Linux source code, usually combined with extra features and software. Some distributions are available for download at no charge while others are available at affordable prices on CD-ROM from Linux retailers worldwide.<br />
<br />
Each distribution has its own purpose, and a number of factors should go into deciding which distribution is best for each user. Some distributions are better suited to home users, others are excellent for commercial settings. Some are better suited for Intel or Macintosh PCs, other are excellent for use on high-performance computers.<br />
<br />
Any current Linux distribution most likely contains the software needed to do the job, including kernel and drivers, libraries, utilities and applications programs. Still, one of the most common questions people ask is "which distribution should I get?" This question is often answered by an assortment of people, each proclaiming their favorite distribution is better than all the rest.<br />
<br />
Probably most people favor the first distribution they successfully installed. Or, if they had problems with the first, they favor the next distribution they install which addresses the problems of the first, and so on.<br />
<br />
It is not in the scope of this document to discuss features of all the distributions out there, but nearly all should work with Linux-VServer, so it is up to you to decide which distribution fits your requirements. For an overview of available distributions checkout [http://www.distrowatch.com DistroWatch].<br />
<br />
== Choose Your Kernel Version ==<br />
<br />
=== Versioning explained ===<br />
<br />
The Linux-VServer project maintains several branches of the kernel patch. Since version 1.00 the versioning is similar to the kernel versioning scheme. Even numbered releases (a.X.z 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.<br />
<br />
Basically the stable and development releases should be similar in functionality, 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.Check out the [[Feature Matrix]] for a comparison.<br />
<br />
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.<br />
<br />
1.X.z 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.<br />
<br />
All downloads are available in the [[Downloads]] section. Also take a look at the [[ChangeLogs]].<br />
<br />
== Disk Partitioning ==<br />
<br />
Since each guest is a seperate root filesystem somewhere in the host system filesystem hierarchy, it is advisable to create a partitioning scheme that fits your needs. Discussing all possible disk configurations is surely out of the scope of this document, however you should take the following guidelines into account while setting up disk space for your guest systems:<br />
<br />
* Generally, one big partition for ''all'' guest systems should suffice<br />
* If you don't want to use [[Disk Limits and Quota|Disk Limits]] you can use one partition per guest system to limit its available disk space. However this will (in most cases) prevent an easy enlargement of disk space later on.<br />
* If you want to use [[Disk Limits and Quota|Quota]] ''inside'' your guest system you have to use seperate partitions per guest system. This will probably change in the future<br />
* You should take care of hard disk failure, e.g. use RAID systems, make regular backups, etc.<br />
* To obtain more flexible space management consider using some Volume Management solution like lvm, lvm2 or evms.<br />
<br />
== Networking ==<br />
<br />
As the host and guest system both share the same physical networkconnection it is advisable to<br />
have as little as possible networkdaemons using the same port on both the host and guest system. If, as with ssh, it is inavoidable to have both daemons share a port, one has to make sure the daemon on the host only listens to the hosts IP address. The guestsytem is isolated by default.<br />
<br />
== Final Notes ==<br />
<br />
If you think the information provided in this document is too vague, feel free to [[Communicate|contact]] the Linux-VServer community and ask for help on your specific setup.</div>84.157.69.20http://wiki.linux-vserver.org/Installation_ConsiderationsInstallation Considerations2008-09-03T09:36:16Z<p>84.157.69.20: /* Disk Partitioning */</p>
<hr />
<div>This guide will give you an idea about pre-requesites and installation considerations of the host system. It is targeted towards production systems, so some of the information provided here may or may not be important to your setup. Decide for your own demand.<br />
<br />
== Hardware Compatibility ==<br />
<br />
The Linux-VServer kernel runs on many platforms, including those listed below:<br />
<br />
* alpha<br />
* arm<br />
* ia64<br />
* m68k<br />
* mips<br />
* ppc<br />
* ppc64<br />
* s390<br />
* sparc<br />
* sparc64<br />
* x86<br />
* x86_64<br />
<br />
See [[Tested Configurations]] for details.<br />
<br />
== Hardware Availability ==<br />
<br />
The host system availability is more critical than the availability of a typical server. Since it runs multiple Virtual Private Servers providing a number of critical services each, the outage of the host system may be very costly. Additionally outage can be as disastrous as the simultaneous outage of a number of servers running critical services.<br />
<br />
Discussing all aspects of high-availability is out of the scope of this document, however the following considerations should be followed to have a clean and secure host system:<br />
<br />
* Use RAID storage for guest filesystems.<br />
* Do not run software on the host system. Instead create guest systems where you can host necessary services. The only needed service on the host system is probably sshd.<br />
* Do not create users on the host system. You can create as many users as you need in any guest system.<br />
<br />
== Hardware Requirements ==<br />
<br />
The exact hardware configuration depends on how many Virtual Private Servers you are going to run on the computer and what load these VPSs are going to produce. Thus, in order to choose the right configuration, you should follow the recommendations below:<br />
<br />
; CPUs<br />
: The more Virtual Private Servers you plan to run simultaneously, the more CPUs you need.<br />
<br />
; Memory<br />
: The more memory you have, the more Virtual Private Servers you can run. The exact figure depends on the number and nature of applications you are planning to run in your Virtual Private Servers. However, on the average, at least 1 GB of RAM is recommended for every 20-30 Virtual Private Servers<br />
<br />
; Disk space<br />
: Each Virtual Private Server occupies 10–500 MB of hard disk space for system files (depends on the use of [[Unification]]) in addition to the user data inside the Virtual Private Server (for example, web site content). You should consider it when planning disk partitioning and the number of Virtual Private Servers to run.<br />
<br />
== Choose Your Distribution ==<br />
<br />
There are many different Linux distributions, or versions. A distribution is the compiled Linux source code, usually combined with extra features and software. Some distributions are available for download at no charge while others are available at affordable prices on CD-ROM from Linux retailers worldwide.<br />
<br />
Each distribution has its own purpose, and a number of factors should go into deciding which distribution is best for each user. Some distributions are better suited to home users, others are excellent for commercial settings. Some are better suited for Intel or Macintosh PCs, other are excellent for use on high-performance computers.<br />
<br />
Any current Linux distribution most likely contains the software needed to do the job, including kernel and drivers, libraries, utilities and applications programs. Still, one of the most common questions people ask is "which distribution should I get?" This question is often answered by an assortment of people, each proclaiming their favorite distribution is better than all the rest.<br />
<br />
Probably most people favor the first distribution they successfully installed. Or, if they had problems with the first, they favor the next distribution they install which addresses the problems of the first, and so on.<br />
<br />
It is not in the scope of this document to discuss features of all the distributions out there, but nearly all should work with Linux-VServer, so it is up to you to decide which distribution fits your requirements. For an overview of available distributions checkout [http://www.distrowatch.com DistroWatch].<br />
<br />
== Choose Your Kernel Version ==<br />
<br />
=== Versioning explained ===<br />
<br />
The Linux-VServer project maintains several branches of the kernel patch. Since version 1.00 the versioning is similar to the kernel versioning scheme. Even numbered releases (a.X.z 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.<br />
<br />
Basically the stable and development releases should be similar in functionality, 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.Check out the [[Feature Matrix]] for a comparison.<br />
<br />
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.<br />
<br />
1.X.z 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.<br />
<br />
All downloads are available in the [[Downloads]] section. Also take a look at the [[ChangeLogs]].<br />
<br />
== Disk Partitioning ==<br />
<br />
Since each guest is a seperate root filesystem somewhere in the host system filesystem hierarchy, it is advisable to create a partitioning scheme that fits your needs. Discussing all possible disk configuration is surely out of the scope of this document, however you should take the following guidelines into account while setting up disk space for your guest systems:<br />
<br />
* Generally, one big partition for ''all'' guest systems should suffice<br />
* If you don't want to use [[Disk Limits and Quota|Disk Limits]] you can use one partition per guest system to limit its available disk space. However this will (in most cases) prevent an easy enlargement of disk space later on.<br />
* If you want to use [[Disk Limits and Quota|Quota]] ''inside'' your guest system you have to use seperate partitions per guest system. This will probably change in the future<br />
* You should take care of hard disk failure, e.g. use RAID systems, make regular backups, etc.<br />
* To obtain more flexible space management consider using some Volume Management solution like lvm, lvm2 or evms.<br />
<br />
== Networking ==<br />
<br />
As the host and guest system both share the same physical networkconnection it is advisable to<br />
have as little as possible networkdaemons using the same port on both the host and guest system. If, as with ssh, it is inavoidable to have both daemons share a port, one has to make sure the daemon on the host only listens to the hosts IP address. The guestsytem is isolated by default.<br />
<br />
== Final Notes ==<br />
<br />
If you think the information provided in this document is too vague, feel free to [[Communicate|contact]] the Linux-VServer community and ask for help on your specific setup.</div>84.157.69.20