PLDWWW: Vserver

[glen]

Author: glen   Date: Sat Jan  7 22:00:38 2006 GMT
Module: PLDWWW   URL: http://www.pld-linux.org/Vserver
---- Log message:


---- Page affected: Vserver

---- Diffs:

================================================================
New page:
= Linux VServer Project =

== Resources ==
 * [http://linux-vserver.org/ Project homepage]
 * [http://linux-vserver.org/short+presentation short presentation]
 * [http://www.nongnu.org/util-vserver/doc/conf/configuration.html doc of configuration items]. you should change the stylesheet in your browser if you care for your eyes ;)
 * [http://www.solucorp.qc.ca/miscprj/s_context.hc?prjstate=1 Introduction to vserver] an older document (for < 2.x), but still useful
 * [http://www.gentoo.org/doc/en/vserver-howto.xml Gentoo Linux-VServer Howto] you'll need this if you want to setup Gentoo guest vserver
 * [http://linux-vserver.org/index.php?page=Linux-VServer-Paper-08 Field of Application paper] reasons why to use vserver.

== Installing host PLD Linux Vserver ==

Build and install kernel
{{{
 ./builder -r kernel-2_6_12_6-0_1 --with vserver --without grsecurity kernel.spec
 poldek -u kernel-vserver
}}}

If you also run desktop on that host you might want to:
{{{
 poldek -u kernel-vserver-sound-{alsa,oss}
}}}

== Installing guest PLD Linux Vserver ==

=== preparing userspace tools ===
{{{
 poldek -u util-vserver{,-build,-init}
}}}

Prepare userspace
configure poldek.conf {{{/etc/vservers/.distributions/pld2.0/poldek/poldek.conf}}}

At this point you should have booted into vserver enabled kernel.
you must start vprocunhide or none of your vservers can start.
start vprocunhide
{{{
/etc/rc.d/init.d/vprocunhide start
}}}

=== actual guest creation ===

build it
{{{
vserver /etc/vservers/test build -m poldek -n test
}}}

install {{{rc-scripts}}} to {{{vpoldek test}}}:
{{{
 vpoldek test -- -u rc-scripts
}}}

and then start it
{{{
vserver test start
}}}

to enter that vserver
{{{
vserver test enter
}}}

note, if you don't run init style {{{plain}}} you must have at least one daemon running inside vserver or your vserver will be down shortly.