http://www.linux-vserver.org/api.php?action=feedcontributions&user=Mstrobert&feedformat=atomLinux-VServer - User contributions [en]2024-03-28T19:13:06ZUser contributionsMediaWiki 1.20.2http://www.linux-vserver.org/DocumentationDocumentation2009-08-18T20:57:15Z<p>Mstrobert: /* Guides and Howtos */ hoary->hardy</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]]: from source, both the kernel and util-vserver<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 />
* [[Getting_high_with_lenny]]<br />
* [[Installing_Ubuntu_8.04_Hardy_as_guest]]<br />
* [[Applying CPU Limits]]<br />
* [[Upgrading from Etch to Lenny]]<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 />
*** [[Network Bandwidth Management]]<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 ==<br />
<br />
* [http://vserver.13thfloor.at/Remote-Reset/ Simple Remote reset] (remote reset/power your vserver box)<br />
* [http://vserver.13thfloor.at/Null-Modem/ NullModem cables] [http://www.loop-back.com/null-mod.html II] [http://www.tldp.org/HOWTO/Remote-Serial-Console-HOWTO/serial-pc-terminal.html III] (cable required for serial console)</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_8.04_Hardy_as_guestInstalling Ubuntu 8.04 Hardy as guest2009-08-18T20:55:59Z<p>Mstrobert: Installing Ubuntu Hoary as guest moved to Installing Ubuntu 8.04 Hardy as guest: This information is for Ubuntu 8.04 Hardy, not Hoary.</p>
<hr />
<div>Installing Ubuntu 8.04 (Hardy) as a Vserver guest<br />
<br />
As Ubuntu 8.04 (Hardy) is the latest LTS release of Ubuntu, it would be a good choice to install as a server. A lot of this information is from the OpenVZ guide at https://help.ubuntu.com/community/OpenVZ.<br />
<br />
This guide requires that you have configured your /etc/vservers/.default correctly<br />
<br />
__TOC__<br />
== Prerequisites ==<br />
* debootstrap <br />
<br />
[Vserver-host] $ sudo apt-get install debootstrap<br />
<br />
== Debootstraping in Ubuntu ==<br />
[Vserver-host] $ vserver hardy-guest build -m debootstrap \<br />
--context 42 --hostname hardy-guest --force \<br />
--interface eth0:10.0.0.123/8 \<br />
-- -d hardy -m http://us.archive.ubuntu.com/ubuntu/ \<br />
-- --arch=i386 --exclude=udev<br />
<br />
You will receive the following warning 5 times (obviously):<br />
<br />
W: Failure while configuring base packages. This will be attempted 5 times.<br />
<br />
You can safely ignore them, as we will fix this later<br />
<br />
== Removing unneeded services ==<br />
By default klogd and rmnologin runs at startup of the guest, it is not necessary, and will slow down the startup time of your guest, you better remove them<br />
<br />
[Vserver-host] $ cd /[path_of_vservers]/hardy-guest/etc/rc3.d<br />
[Vserver-host] $ rm S11klogd S99rmnologin<br />
<br />
You should also remove unneeded shutdown scripts<br />
<br />
[Vserver-host] $ cd /[path_of_vservers]/hardy-guest/etc/rc6.d<br />
[Vserver-host] $ rm *<br />
<br />
You should add a link for killing sysklogd<br />
<br />
[Vserver-host] $ ln -s ../init.d/sysklogd K11sysklogd<br />
<br />
== Starting guest and fixing group 11 issue ==<br />
Now it is time to start your new vserver and enter it:<br />
[Vserver-host] $ vserver hardy-guest start<br />
It will return the following:<br />
/etc/init.d/rc: 166: cannot open /dev/console: No such file<br />
* Starting system log daemon...<br />
...done.<br />
* Running local boot scripts (/etc/rc.local)<br />
...done.<br />
Then you can enter your vserver<br />
[Vserver-host] $ vserver hardy-guest enter<br />
It will return the following:<br />
id: cannot find name for group ID 11<br />
<br />
=== Fixing the "/etc/init.d/rc: 166: cannot open /dev/console: No such file" issue ===<br />
Open /etc/init.d/rc in your favorite editor<br />
root@hardy-guest:/# vim /etc/init.d/rc<br />
Find the following lines and comment them out by perpending them with an "#" (this has been done in the example) They will be at line 163-166<br />
# Set onlcr to avoid staircase effect.<br />
#if [ "$QUIET" != yes ]; then<br />
# stty onlcr </dev/console >/dev/console 2>&1<br />
#fi<br />
Save and quit<br />
<br />
=== Fixing the "id: cannot find name for group ID 11" issue ===<br />
I don't know what the group really shoud be, but I just added the group "void" as group 11. Someone who knows what it should be, could probably correct it.<br />
<br />
root@hardy-guest:/# groupadd -g 11 void<br />
<br />
== Removing unneeded packages ==<br />
There are some packages you obviously would not need in a vserver-guest:<br />
<br />
* DHCP3<br />
* busybox-initramfs<br />
* console-setup<br />
* dmidecode eject<br />
* ethtool<br />
* initramfs-tools<br />
* klibc-utils<br />
* laptop-detect<br />
* libiw29<br />
* libklibc<br />
* libvolume-id0<br />
* mii-diag<br />
* module-init-tools<br />
* ntpdate<br />
* pciutils<br />
* pcmciautils<br />
* ubuntu-minimal<br />
* udev usbutils<br />
* wireless-tools<br />
* wpasupplicant<br />
* xkb-data<br />
* tasksel<br />
* tasksel-data<br />
<br />
So you should start up your new guest and enter it and remove them.<br />
<br />
[hardy-guest] $ apt-get remove --purge busybox-initramfs console-setup dmidecode eject \<br />
ethtool initramfs-tools klibc-utils laptop-detect libiw29 libklibc \<br />
libvolume-id0 mii-diag module-init-tools ntpdate pciutils pcmciautils ubuntu-minimal \<br />
udev usbutils wireless-tools wpasupplicant xkb-data tasksel tasksel-data \<br />
dhcp3-client dhcp3-server<br />
<br />
== Finished ==<br />
Now you have installed hardy from debootstrap, and hopefully everything is working<br />
<br />
Remember that you will have to create symlinks to services in /etc/rc6.d in order for them to be stopped when running 'vserver [vservername] stop'</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_Hoary_as_guestInstalling Ubuntu Hoary as guest2009-08-18T20:55:59Z<p>Mstrobert: Installing Ubuntu Hoary as guest moved to Installing Ubuntu 8.04 Hardy as guest: This information is for Ubuntu 8.04 Hardy, not Hoary.</p>
<hr />
<div>#REDIRECT [[Installing Ubuntu 8.04 Hardy as guest]]</div>Mstroberthttp://www.linux-vserver.org/Installing_32-bit_Fedora_on_64-bit_DebianInstalling 32-bit Fedora on 64-bit Debian2008-06-16T23:11:09Z<p>Mstrobert: /* See also */ ln Building Guest Systems</p>
<hr />
<div>Guide to install a 32-bit Fedora guest into a 64-bit Debian host.<br />
__TOC__<br />
==Set up yum repository==<br />
host# mkdir /etc/rpm<br />
host# mkdir /var/lib/rpm<br />
host# apt-get install yum linux32<br />
host# cp -a /usr/lib/util-vserver/distributions/fc6/{yum,yum.repos.d} /etc/vservers/.distributions/fc6<br />
<br />
vserver build does not use /etc/yum*, though you will see an ignorable error message about it if it doesn't exist. <br />
<br />
Edit the files /etc/vservers/.distributions/fc6/yum.repos.d/fedora-{core,updates,extras}.repo<br />
* Uncomment the first baseurl= line of each file (by removing the leading # character)<br />
<br />
===Proxy===<br />
If you use a proxy, append to /etc/vservers/.distributions/fc6/yum/yum.conf (in the [main] section) a line of the form:<br />
proxy=http://proxy.yourcompany.com:3128<br />
<br />
==Build vserver==<br />
host# export ARCH=i386<br />
host# export http_proxy=http://proxy.yourcompany.com:3128<br />
host# linux32 vserver fedora-zod-32-gustname build -m yum --hostname=fedora-zod-32-guestname --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d fc6 -- --arch i386<br />
host# unset ARCH<br />
<br />
you may also create '''/etc/rpm/platform''' file:<br />
<br />
guest# vi /etc/rpm/platform<br />
i386-redhat-linux-gnu<br />
<br />
this way yum and rpm will use i386 packages<br />
<br />
==Verify==<br />
To observe the 32-bitness of the guest's applications, do:<br />
host# linux32 vyum fedora-zod-32-guestname -- install file<br />
host# vserver fedora-zod-32-guestname start<br />
host# vserver fedora-zod-32-guestname enter<br />
fedora-zod-32-guestname# file /bin/ls<br />
/bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped<br />
or<br />
host# file /var/lib/vservers/fedora-zod-32-guestname/bin/ls<br />
/var/lib/vservers/fedora-zod-32-guestname/bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped<br />
==See also==<br />
* [[Building Guest Systems]]<br />
* [[Installing Ubuntu on Debian]]</div>Mstroberthttp://www.linux-vserver.org/Building_Guest_SystemsBuilding Guest Systems2008-06-16T23:10:22Z<p>Mstrobert: /* See also */ ln Installing 32-bit Fedora on 64-bit Debian</p>
<hr />
<div>== Building a guest ==<br />
<br />
There are three parts to the <code>vserver ... build</code> command. Each part is separated by <code>--</code>. The first part are generic vserver options, such as hostname, available IP-addresses, and context id. The second part is specific to the chosen build method (by <code>-m <method></code> in the first part). The third part is completely optional and only implemented for a few build methods. These are options passed directly to whatever application is used to build guest.<br />
<br />
There are a lot of options not covered here (yet). Use <code>vserver - build --help</code> to see them all.<br />
<br />
=== Building guests using the debootstrap build method ===<br />
<br />
* Build a Debian lenny guest using the ftp.de.debian.org mirror.<br />
vserver vserver1 build -m debootstrap --hostname vserver1.mydomain.com --interface eth0:192.168.1.10/24 -- -d lenny -m http://ftp.de.debian.org/debian<br />
lenny can be replaced by e.g. etch for Debian etch, edgy for Ubuntu edgy, or sid for Debian sid. Anything your debootstrap version can handle will be fine.<br />
<br />
If you want to build a 32-bit guest on a 64-bit host, append <code>-- --arch i386</code> to the above command line.<br />
<br />
=== Building guests using the yum build method ===<br />
<br />
* Make sure that your host system already has yum installed, preferably one that has been patched to work better with chroots.<br />
<br />
* Build a CentOS 5-based guest using a minimal set of packages.<br />
vserver vserver2 build -m yum --hostname vserver2.mydomain.com --interface eth0:192.168.1.11/24 -- -d centos5<br />
centos5 can be replaced by e.g. f8 for Fedora 8, or fc6 for Fedora 6.<br />
<br />
If you want to build a 32-bit guest on a 64-bit, prepend <code>linux32</code> to this and subsequent yum commands.<br />
<br />
* If you want to manage the packages inside the guest, you will have to install some package management program(s) as well as internalize the RPM database. This can be achieved by<br />
vyum vserver2 -- install yum<br />
vserver vserver2 pkgmgmt internalize<br />
Internal package management means that commands such as rpm, yum and rpmbuild can be used from inside the guest, as opposed to requiring the host administrator to run vrpm or vyum. If you use rpmbuild, you'll need internal package management, or use --nodeps (but that's ''strongly'' discouraged).<br />
<br />
* Depending on your host's/guest's distribution, you may also need to do<br />
vserver vserver2 exec bash -c "rm -f /var/lib/rpm/__db*; rpm --rebuilddb"<br />
This is required if every rpm operation, for example ''rpm -qa'', complains about a database version mismatch.<br />
<br />
=== Building guests using the template build method ===<br />
<br />
A template is a file containing a complete guest filesystem. This can be a tar(1)ball, a cpio(1)-archive, or a dump(8). It can be compressed using either gzip or bzip2. Multiple templates can be used, to do e.g. guest-specific modifications.<br />
<br />
* Build a guest using a single template named stage4-i686-20070905.tar.bz2 located in /vservers/.templates.<br />
vserver vserver3 build -m template --hostname vserver3.mydomain.com --interface eth0:192.168.1.12/24 -- -d gentoo -t /vservers/.templates/stage4-i686-20070905.tar.bz2<br />
<br />
'''OR'''<br />
<br />
* Build a guest using multiple templates, one named stage4-i686-20070905.tar.bz2 and one named httpd.tar.bz2.<br />
vserver vserver3 build -m template --hostname vserver3.mydomain.com --interface eth0:192.168.1.12/24 -- -d gentoo -t /vservers/.templates/stage4-i686-20070905.tar.bz2 -t /vservers/.templates/httpd.tar.bz2<br />
<br />
=== Building guests using the rsync build method ===<br />
<br />
The rsync build method can be used to move a guest from one system to another. It is preferable for most guest distributions if the source guest is stopped when you create a one based on it, but it's not strictly required.<br />
<br />
* Build a guest by rsync'ing from vserver3 on host1.<br />
RSYNC_RSH=ssh vserver vserver4 build -m rsync --hostname vserver4.mydomain.com --interface eth0:192.168.1.13/24 -- --source root@host1:/vservers/vserver3<br />
<br />
'''OR'''<br />
<br />
* Build a guest by rsync'ing from vserver1 on the same host.<br />
vserver vserver4 build -m rsync --hostname vserver4.mydomain.com --interface eth0:192.168.1.13/24 -- --source vserver1<br />
<br />
=== Building guests using the clone build method ===<br />
<br />
The clone build method copies the filesystem from one guest to another, much like the rsync build method, but the thing that separates it is that it knows about unified/hashified files. This means that it only creates new links for such files, and copies the rest, which can lead to significantly speedier builds.<br />
<br />
* Build a guest by using vserver4 as a reference.<br />
vserver vserver5 build -m clone --hostname vserver5.mydomain.com --interface eth0:192.168.1.14/24 -- --source /vservers/vserver4<br />
<br />
== Post-build customization ==<br />
<br />
== Verifying guest functionality ==<br />
<br />
* Once the guest is built, it's time to start it.<br />
vserver vserverX start<br />
<br />
* At this point, you can use both<br />
vserver vserverX enter<br />
and<br />
vserver vserverX exec ...<br />
to do things inside the guest.<br />
<br />
* To stop it, simply use<br />
vserver vserverX stop<br />
<br />
== See also ==<br />
* [[Installing Ubuntu on Debian]]<br />
* [[Installing 32-bit Fedora on 64-bit Debian]]</div>Mstroberthttp://www.linux-vserver.org/Building_Guest_SystemsBuilding Guest Systems2008-06-16T23:08:27Z<p>Mstrobert: add section See also, and ln Installing Ubuntu on Debian</p>
<hr />
<div>== Building a guest ==<br />
<br />
There are three parts to the <code>vserver ... build</code> command. Each part is separated by <code>--</code>. The first part are generic vserver options, such as hostname, available IP-addresses, and context id. The second part is specific to the chosen build method (by <code>-m <method></code> in the first part). The third part is completely optional and only implemented for a few build methods. These are options passed directly to whatever application is used to build guest.<br />
<br />
There are a lot of options not covered here (yet). Use <code>vserver - build --help</code> to see them all.<br />
<br />
=== Building guests using the debootstrap build method ===<br />
<br />
* Build a Debian lenny guest using the ftp.de.debian.org mirror.<br />
vserver vserver1 build -m debootstrap --hostname vserver1.mydomain.com --interface eth0:192.168.1.10/24 -- -d lenny -m http://ftp.de.debian.org/debian<br />
lenny can be replaced by e.g. etch for Debian etch, edgy for Ubuntu edgy, or sid for Debian sid. Anything your debootstrap version can handle will be fine.<br />
<br />
If you want to build a 32-bit guest on a 64-bit host, append <code>-- --arch i386</code> to the above command line.<br />
<br />
=== Building guests using the yum build method ===<br />
<br />
* Make sure that your host system already has yum installed, preferably one that has been patched to work better with chroots.<br />
<br />
* Build a CentOS 5-based guest using a minimal set of packages.<br />
vserver vserver2 build -m yum --hostname vserver2.mydomain.com --interface eth0:192.168.1.11/24 -- -d centos5<br />
centos5 can be replaced by e.g. f8 for Fedora 8, or fc6 for Fedora 6.<br />
<br />
If you want to build a 32-bit guest on a 64-bit, prepend <code>linux32</code> to this and subsequent yum commands.<br />
<br />
* If you want to manage the packages inside the guest, you will have to install some package management program(s) as well as internalize the RPM database. This can be achieved by<br />
vyum vserver2 -- install yum<br />
vserver vserver2 pkgmgmt internalize<br />
Internal package management means that commands such as rpm, yum and rpmbuild can be used from inside the guest, as opposed to requiring the host administrator to run vrpm or vyum. If you use rpmbuild, you'll need internal package management, or use --nodeps (but that's ''strongly'' discouraged).<br />
<br />
* Depending on your host's/guest's distribution, you may also need to do<br />
vserver vserver2 exec bash -c "rm -f /var/lib/rpm/__db*; rpm --rebuilddb"<br />
This is required if every rpm operation, for example ''rpm -qa'', complains about a database version mismatch.<br />
<br />
=== Building guests using the template build method ===<br />
<br />
A template is a file containing a complete guest filesystem. This can be a tar(1)ball, a cpio(1)-archive, or a dump(8). It can be compressed using either gzip or bzip2. Multiple templates can be used, to do e.g. guest-specific modifications.<br />
<br />
* Build a guest using a single template named stage4-i686-20070905.tar.bz2 located in /vservers/.templates.<br />
vserver vserver3 build -m template --hostname vserver3.mydomain.com --interface eth0:192.168.1.12/24 -- -d gentoo -t /vservers/.templates/stage4-i686-20070905.tar.bz2<br />
<br />
'''OR'''<br />
<br />
* Build a guest using multiple templates, one named stage4-i686-20070905.tar.bz2 and one named httpd.tar.bz2.<br />
vserver vserver3 build -m template --hostname vserver3.mydomain.com --interface eth0:192.168.1.12/24 -- -d gentoo -t /vservers/.templates/stage4-i686-20070905.tar.bz2 -t /vservers/.templates/httpd.tar.bz2<br />
<br />
=== Building guests using the rsync build method ===<br />
<br />
The rsync build method can be used to move a guest from one system to another. It is preferable for most guest distributions if the source guest is stopped when you create a one based on it, but it's not strictly required.<br />
<br />
* Build a guest by rsync'ing from vserver3 on host1.<br />
RSYNC_RSH=ssh vserver vserver4 build -m rsync --hostname vserver4.mydomain.com --interface eth0:192.168.1.13/24 -- --source root@host1:/vservers/vserver3<br />
<br />
'''OR'''<br />
<br />
* Build a guest by rsync'ing from vserver1 on the same host.<br />
vserver vserver4 build -m rsync --hostname vserver4.mydomain.com --interface eth0:192.168.1.13/24 -- --source vserver1<br />
<br />
=== Building guests using the clone build method ===<br />
<br />
The clone build method copies the filesystem from one guest to another, much like the rsync build method, but the thing that separates it is that it knows about unified/hashified files. This means that it only creates new links for such files, and copies the rest, which can lead to significantly speedier builds.<br />
<br />
* Build a guest by using vserver4 as a reference.<br />
vserver vserver5 build -m clone --hostname vserver5.mydomain.com --interface eth0:192.168.1.14/24 -- --source /vservers/vserver4<br />
<br />
== Post-build customization ==<br />
<br />
== Verifying guest functionality ==<br />
<br />
* Once the guest is built, it's time to start it.<br />
vserver vserverX start<br />
<br />
* At this point, you can use both<br />
vserver vserverX enter<br />
and<br />
vserver vserverX exec ...<br />
to do things inside the guest.<br />
<br />
* To stop it, simply use<br />
vserver vserverX stop<br />
<br />
== See also ==<br />
* [[Installing Ubuntu on Debian]]</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2008-06-16T23:07:11Z<p>Mstrobert: /* See also */ ln Building Guest Systems</p>
<hr />
<div>How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Prepare debootstrap==<br />
You will need the debootstrap script for your desired Ubuntu release (eg dapper, feisty, gusty).<br />
<br />
Check that you have the debootstrap script in <code>/usr/lib/debootstrap/scripts/</code>, eg <code>/usr/lib/debootstrap/scripts/gusty</code>.<br />
<br />
If you do not have the debootstrap script for your desired Ubuntu release, the easiest way is to download and install the latest debootstrap deb from [http://packages.debian.org/sid/debootstrap Debian sid].<br />
<br />
If the script is not available in Debian sid, download Ubuntu's latest release from [http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=debootstrap&searchon=names&version=all&release=all here]. (eg, as of April 2007, download the debootstrap deb for feisty). You want the debootstrap from the latest release, even if you want to install a previous release Ubuntu vserver guest.<br />
Extract the Ubuntu scripts from the deb and place them in <code>/usr/lib/debootstrap/scripts/</code>.<br />
<br />
For example, do something like:<br />
$ cd /tmp<br />
$ wget http://mirrors.kernel.org/ubuntu/pool/main/d/debootstrap/debootstrap_0.3.3.2ubuntu3_all.deb<br />
$ dpkg --extract debootstrap_0.3.3.2ubuntu3_all.deb debootstrap-feisty<br />
$ sudo cp -P debootstrap-feisty/usr/lib/debootstrap/scripts/{warty,warty.buildd,hoary,hoary.buildd,breezy,dapper,edgy,edgy.fakechroot,feisty,feisty.fakechroot} /usr/lib/debootstrap/scripts/<br />
<br />
==Build==<br />
===Build with guest architecture the same as host===<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/ubuntu/<br />
<br />
===Build 32-bit guest on 64-bit host===<br />
# vserver feisty-guest-32 build -m debootstrap --hostname feisty-guest-32 --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/ubuntu/ -- --arch i386<br />
Verify 32-bitness of guest:<br />
host:# file /var/lib/vservers/feisty-guest-32/bin/ls<br />
/var/lib/vservers/feisty-guest-32/bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.0, dynamically linked (uses shared libs), for GNU/Linux 2.6.0, stripped<br />
<br />
==See also==<br />
* [[Building Guest Systems]]<br />
* [[Frequently_Asked_Questions#I_run_a_Debian_host_and_want_to_build_an_Ubuntu_guest._Howto.3F]]<br />
* [[Installing 32-bit Fedora on 64-bit Debian]]</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2008-06-16T23:04:53Z<p>Mstrobert: /* Prepare debootstrap */ using -P flag to cp since debian debootstrap_1.0.9_all has symlinks for some of the scripts</p>
<hr />
<div>How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Prepare debootstrap==<br />
You will need the debootstrap script for your desired Ubuntu release (eg dapper, feisty, gusty).<br />
<br />
Check that you have the debootstrap script in <code>/usr/lib/debootstrap/scripts/</code>, eg <code>/usr/lib/debootstrap/scripts/gusty</code>.<br />
<br />
If you do not have the debootstrap script for your desired Ubuntu release, the easiest way is to download and install the latest debootstrap deb from [http://packages.debian.org/sid/debootstrap Debian sid].<br />
<br />
If the script is not available in Debian sid, download Ubuntu's latest release from [http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=debootstrap&searchon=names&version=all&release=all here]. (eg, as of April 2007, download the debootstrap deb for feisty). You want the debootstrap from the latest release, even if you want to install a previous release Ubuntu vserver guest.<br />
Extract the Ubuntu scripts from the deb and place them in <code>/usr/lib/debootstrap/scripts/</code>.<br />
<br />
For example, do something like:<br />
$ cd /tmp<br />
$ wget http://mirrors.kernel.org/ubuntu/pool/main/d/debootstrap/debootstrap_0.3.3.2ubuntu3_all.deb<br />
$ dpkg --extract debootstrap_0.3.3.2ubuntu3_all.deb debootstrap-feisty<br />
$ sudo cp -P debootstrap-feisty/usr/lib/debootstrap/scripts/{warty,warty.buildd,hoary,hoary.buildd,breezy,dapper,edgy,edgy.fakechroot,feisty,feisty.fakechroot} /usr/lib/debootstrap/scripts/<br />
<br />
==Build==<br />
===Build with guest architecture the same as host===<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/ubuntu/<br />
<br />
===Build 32-bit guest on 64-bit host===<br />
# vserver feisty-guest-32 build -m debootstrap --hostname feisty-guest-32 --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/ubuntu/ -- --arch i386<br />
Verify 32-bitness of guest:<br />
host:# file /var/lib/vservers/feisty-guest-32/bin/ls<br />
/var/lib/vservers/feisty-guest-32/bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.0, dynamically linked (uses shared libs), for GNU/Linux 2.6.0, stripped<br />
<br />
==See also==<br />
* [[Frequently_Asked_Questions#I_run_a_Debian_host_and_want_to_build_an_Ubuntu_guest._Howto.3F]]<br />
* [[Installing 32-bit Fedora on 64-bit Debian]]</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2007-09-18T23:18:29Z<p>Mstrobert: /* Prepare debootstrap */ Added check since may already have the debootstrap script since it's in the debian testing/lenny version of debootstrap.</p>
<hr />
<div>How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Prepare debootstrap==<br />
You will need the debootstrap script for your desired Ubuntu release (eg dapper, feisty).<br />
<br />
Check that you have the debootstrap script in <code>/usr/lib/debootstrap/scripts/</code>, eg <code>/usr/lib/debootstrap/scripts/feisty</code>.<br />
<br />
If you do not have the debootstrap script for your desired Ubuntu release, download the debootstrap deb for Ubuntu's latest release from [http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=debootstrap&searchon=names&version=all&release=all here]. (eg, as of April 2007, download the debootstrap deb for feisty). You want the debootstrap from the latest release, even if you want to install a previous release Ubuntu vserver guest.<br />
Extract the Ubuntu scripts from the deb and place them in <code>/usr/lib/debootstrap/scripts/</code>.<br />
<br />
For example, do something like:<br />
$ cd /tmp<br />
$ wget http://mirrors.kernel.org/ubuntu/pool/main/d/debootstrap/debootstrap_0.3.3.2ubuntu3_all.deb<br />
$ dpkg --extract debootstrap_0.3.3.2ubuntu3_all.deb debootstrap-feisty<br />
$ sudo cp debootstrap-feisty/usr/lib/debootstrap/scripts/{warty,warty.buildd,hoary,hoary.buildd,breezy,dapper,edgy,edgy.fakechroot,feisty,feisty.fakechroot} /usr/lib/debootstrap/scripts/<br />
<br />
==Build==<br />
===Build with guest architecture the same as host===<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/ubuntu/<br />
<br />
===Build 32-bit guest on 64-bit host===<br />
# vserver feisty-guest-32 build -m debootstrap --hostname feisty-guest-32 --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/ubuntu/ -- --arch i386<br />
Verify 32-bitness of guest:<br />
host:# file /var/lib/vservers/feisty-guest-32/bin/ls<br />
/var/lib/vservers/feisty-guest-32/bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.0, dynamically linked (uses shared libs), for GNU/Linux 2.6.0, stripped<br />
<br />
==See also==<br />
* [[Frequently_Asked_Questions#I_run_a_Debian_host_and_want_to_build_an_Ubuntu_guest._Howto.3F]]<br />
* [[Installing 32-bit Fedora on 64-bit Debian]]</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2007-09-17T23:23:17Z<p>Mstrobert: /* Build 32-bit guest on 64-bit host */ applying previous /ubuntu/ edit to 32-bit version</p>
<hr />
<div>How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Prepare debootstrap==<br />
You will need the debootstrap script for your desired Ubuntu release (eg dapper, feisty).<br />
<br />
Download the debootstrap deb for Ubuntu's latest release from [http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=debootstrap&searchon=names&version=all&release=all here]. (eg, as of April 2007, download the debootstrap deb for feisty). You want the debootstrap from the latest release, even if you want to install a previous release Ubuntu vserver guest.<br />
Extract the Ubuntu scripts from the deb and place them in <code>/usr/lib/debootstrap/scripts/</code>.<br />
<br />
For example, do something like:<br />
$ cd /tmp<br />
$ wget http://mirrors.kernel.org/ubuntu/pool/main/d/debootstrap/debootstrap_0.3.3.2ubuntu3_all.deb<br />
$ dpkg --extract debootstrap_0.3.3.2ubuntu3_all.deb debootstrap-feisty<br />
$ sudo cp debootstrap-feisty/usr/lib/debootstrap/scripts/{warty,warty.buildd,hoary,hoary.buildd,breezy,dapper,edgy,edgy.fakechroot,feisty,feisty.fakechroot} /usr/lib/debootstrap/scripts/<br />
<br />
==Build==<br />
===Build with guest architecture the same as host===<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/ubuntu/<br />
<br />
===Build 32-bit guest on 64-bit host===<br />
# vserver feisty-guest-32 build -m debootstrap --hostname feisty-guest-32 --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/ubuntu/ -- --arch i386<br />
Verify 32-bitness of guest:<br />
host:# file /var/lib/vservers/feisty-guest-32/bin/ls<br />
/var/lib/vservers/feisty-guest-32/bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.0, dynamically linked (uses shared libs), for GNU/Linux 2.6.0, stripped<br />
<br />
==See also==<br />
* [[Frequently_Asked_Questions#I_run_a_Debian_host_and_want_to_build_an_Ubuntu_guest._Howto.3F]]<br />
* [[Installing 32-bit Fedora on 64-bit Debian]]</div>Mstroberthttp://www.linux-vserver.org/DocumentationDocumentation2007-09-14T23:11:33Z<p>Mstrobert: /* Configuration */ added link to Share a directory among multiple vserver guests</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 />
* [[some small howto for Fedorro TM os]]<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 />
* [[yum-patch|How to patch vyum]]<br />
* [[yum-upgrade-3.2.4|Upgrading existing installations to yum-3.2.4]]<br />
* [[Share a directory among multiple vserver guests]]<br />
<br />
== Guides and Howtos ==<br />
<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 />
<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>Mstroberthttp://www.linux-vserver.org/Share_a_directory_among_multiple_guestsShare a directory among multiple guests2007-09-14T23:09:30Z<p>Mstrobert: added sections Assumptions, Command, See also</p>
<hr />
<div>How to share a directory, such as <code>/home</code>, among multiple vserver guests.<br />
__TOC__<br />
==Assumptions==<br />
Suppose you have multiple vserver guests at locations such as <code>/var/lib/vservers/<guest>/</code>.<br />
You would like to share a directory, such as <code>/srv/common/home</code>, among multiple guests.<br />
Each guest will be able to write to the directory.<br />
==Command==<br />
$ for guest in /var/lib/vservers/*; do mount --bind /srv/common/home ${guest}/home; done<br />
==See also==<br />
* <code>$ man mount</code></div>Mstroberthttp://www.linux-vserver.org/Share_a_directory_among_multiple_guestsShare a directory among multiple guests2007-09-14T23:02:41Z<p>Mstrobert: Initial page</p>
<hr />
<div>How to share a directory, such as /home, among multiple vserver guests.<br />
__TOC__</div>Mstroberthttp://www.linux-vserver.org/Installing_a_Fedora_7_vserver_guestInstalling a Fedora 7 vserver guest2007-09-13T21:41:36Z<p>Mstrobert: Initial page</p>
<hr />
<div>Guide to installing Fedora 7 as a vserver guest.<br />
__TOC__</div>Mstroberthttp://www.linux-vserver.org/DocumentationDocumentation2007-09-06T15:53:18Z<p>Mstrobert: /* Guides and Howtos */ added link to Networking vserver guests</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 />
* [[some small howto for Fedorro TM os]]<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 />
* [[yum-patch:Documentation|How to patch vyum]]<br />
<br />
== Guides and Howtos ==<br />
<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 />
<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>Mstroberthttp://www.linux-vserver.org/Networking_vserver_guestsNetworking vserver guests2007-09-06T15:51:00Z<p>Mstrobert: HowtoPrivateNetworking moved to Networking vserver guests: changed name as part of migration from oldwiki</p>
<hr />
<div>Setting up network access to and from your vserver guests.<br />
__TOC__<br />
==Introduction==<br />
<br />
Lets imagine, you have only one external IP -- <code>$EXTIP</code>.<br />
<br />
You want to have several vservers running without worrying about port overlapping.<br />
<br />
Example:<br />
<br />
Two vservers run a default webserver, running on port 80. If each "guest" vserver shares an IP with the host, then the two webservers will confict.<br />
<br />
One solution is:<br />
<br />
* All vservers are contained in a "virtual lan", say 192.168.1.x<br />
* Each vserver has its own IP<br />
* Control port forwarding on "parent" host. That is, run a router.<br />
<br />
==Configuration==<br />
===Host===<br />
Set up <code>dummy0</code> interface on the parent host<br />
# /etc/network/interfaces on a Debian box, <br />
# configure on other distros with your preferred way<br />
auto dummy0<br />
iface dummy0 inet static<br />
address 192.168.1.250<br />
netmask 255.255.255.0<br />
<br />
===Guests===<br />
Set up each guest vserver:<br />
cd /etc/vservers/$VSERVER/interfaces/0<br />
echo dummy0 > dev<br />
echo 192.168.1.1 > ip<br />
echo 1 > name<br />
echo 24 > prefix<br />
Consider using a value of <code>name</code> equal to the last digit of the IP for easy separation.<br />
<br />
===Host as router===<br />
Configure the host to act as a router.<br />
<br />
For internal packets going outside, pretend each packet came from our external IP:<br />
# iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j SNAT --to-source $EXTIP<br />
For each service that runs on a vserver, map it to an external port. Vserver local address <code>$VHOST</code> and port <code>$INTPORT</code> you select one external port <code>$EXTPORT</code> and run the following:<br />
# iptables -t nat -A PREROUTING -s ! 192.168.1.0/24 -m tcp -p tcp --dport $EXTPORT -j DNAT --to-destination $VHOST:$INTPORT<br />
That's all!<br />
<br />
==Verifying==<br />
Try <code>ping pool.ntp.org</code> from your vserver -- it should ping fine.<br />
<br />
Try to connect to your <code>$EXTIP:$EXTPORT</code> (from another external host) -- you will successfully connect to service running on a guest vserver.<br />
==See also==<br />
* [[Frequently_Asked_Questions#If_my_host_has_only_one_a_single_public_IP.2C_can_I_use_RFC1918_IP_.28e.g._192.168.foo.bar.29_for_the_guest_vservers.3F |FAQ on private networking]]<br />
* [[Frequently_Asked_Questions#When_I_try_to_ssh_to_the_guest.2C_I_log_into_the_host.2C_even_if_I_installed_sshd_on_the_guest._What.27s_wrong_here.3F |Permit guest sshd to bind to its IP address's port 22]]</div>Mstroberthttp://www.linux-vserver.org/HowtoPrivateNetworkingHowtoPrivateNetworking2007-09-06T15:51:00Z<p>Mstrobert: HowtoPrivateNetworking moved to Networking vserver guests: changed name as part of migration from oldwiki</p>
<hr />
<div>#REDIRECT [[Networking vserver guests]]</div>Mstroberthttp://www.linux-vserver.org/DocumentationDocumentation2007-09-06T15:42:34Z<p>Mstrobert: /* Guides and Howtos */ added link to Installing an openSUSE vserver guest</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 />
* [[some small howto for Fedorro TM os]]<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 />
* [[yum-patch:Documentation|How to patch vyum]]<br />
<br />
== Guides and Howtos ==<br />
<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 />
<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>Mstroberthttp://www.linux-vserver.org/Installing_an_openSUSE_vserver_guestInstalling an openSUSE vserver guest2007-09-06T15:40:27Z<p>Mstrobert: SuseVserverHowTo moved to Installing an openSUSE vserver guest: updated name as part of migration from oldwiki</p>
<hr />
<div>Installing and running openSUSE (previously knows as SUSE Linux) as a vserver guest.<br />
__TOC__<br />
==Test configuration==<br />
Host:<br />
* Debian Etch AMD64, Kernel 2.6.15.4-vs2.0.2-rc9, util-vserver 0.30.210 + similar patch, or<br />
* Debian Etch AMD64, 2.6.18-4-vserver-amd64, util-vserver 0.30.212-1 + patch (see below)<br />
Guest:<br />
* SLES 9, or<br />
* openSUSE 10.2<br />
<br />
==Running openSUSE vservers on a Debian server==<br />
===Installation===<br />
Debian is lacking the required rpm tools to install an openSUSE or SLES system directly via vserver build (the required apt-rpm is available in source only for apt-0.5.xx, and Debian is already at 0.6.xx).<br />
<br />
Therefore, use the normal openSUSE installation procedure and then copy the system to a vserver directory:<br />
* Install openSUSE on raw metal or in a virtual machine (such as [http://www.virtualbox.org/ VirtualBox]).<br />
* Boot from CD (openSUSE or Debian - whatever you prefer), or just boot into the OS and log in as root.<br />
* tar the whole system, copy it to the vserver host and untar it to the desired vserver location, usually <code>/var/lib/vservers/<servername></code><br />
* Create <code>/etc/vservers/<servername></code> manually, or copy it from another vserver.<br />
<br />
===Post install cleanup===<br />
* remove some startup service, either delete the appropriate /etc/init.d/.... links or run the following from inside the vserver:<br />
# chkconfig -d -f boot.swap boot.isapnp boot.idedma boot.loadmodules \<br />
boot.device-mapper boot.md boot.proc boot.shm boot.sched \<br />
boot.rootfsck hotplug boot.localfs boot.crypto boot.clock \<br />
boot.scpm boot.ipconfig<br />
<br />
# chkconfig -d -f coldplug irq_balancer random network fbset powersaved kbd hwscan<br />
* remove unneeded packages:<br />
# rpm -e irqbalance kernel-smp grub reiserfs xfsprogs raidtools ntfsprogs \<br />
module-init-tools mkinitrd powersave hotplug mdadm<br />
'''Note:''' there are a number of redundant packages remaining that can not be removed due to yast2 depending on them.<br />
<br />
===initscripts===<br />
openSUSE's <code>/etc/init.d/rc</code> expects two environment variables: <code>RUNLEVEL</code> and <code>PREVLEVEL</code>. The vserver.start script fails to set those. There are a couple workarounds:<br />
* Edit <code>/etc/init.d/rc</code> to set those values (not recommended (why?)). For example, inserting these lines near the top of the file:<br />
PREVLEVEL="N"<br />
RUNLEVEL="$1"<br />
* Apply the following patch to <code>vserver.start</code> to set the values:<br />
--- vserver.start,orig 2006-12-09 12:37:58.000000000 -0700<br />
+++ vserver.start 2007-06-11 12:27:27.000000000 -0600<br />
@@ -141,7 +141,7 @@<br />
$_VUNAME --xid self --set -t context="$VSERVER_DIR" -- \<br />
$_VATTRIBUTE --set "${OPTS_VATTRIBUTE[@]}" -- \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i "${OPTS_ENV[@]}" \<br />
+ $_ENV -i "${OPTS_ENV[@]}" PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_VCONTEXT --migrate-self --endsetup --chroot $SILENT_OPT \<br />
"${OPTS_VCONTEXT_MIGRATE[@]}" "${OPTS_VCONTEXT_ENTER[@]}" -- \<br />
"${INITCMD_START[@]}"<br />
@@ -157,7 +157,7 @@<br />
$_EXEC_ULIMIT "$VSERVER_DIR/ulimits" \<br />
$_CHCONTEXT_COMPAT "${CHCONTEXT_OPTS[@]}" "${CHCONTEXT_INIT_OPTS[@]}" \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i "${OPTS_ENV[@]}" \<br />
+ $_ENV -i "${OPTS_ENV[@]}" PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_CHAINECHO "${_IS_FAKEINIT:+$startsync_pipe}" "" \<br />
$_CAPCHROOT "${CAPCHROOT_OPTS[@]}" . \<br />
"${INITCMD_START[@]}"<br />
'''edit me:''' do we need to modify the <code>vserver.stop</code> script as well?</div>Mstroberthttp://www.linux-vserver.org/SuseVserverHowToSuseVserverHowTo2007-09-06T15:40:27Z<p>Mstrobert: SuseVserverHowTo moved to Installing an openSUSE vserver guest: updated name as part of migration from oldwiki</p>
<hr />
<div>#REDIRECT [[Installing an openSUSE vserver guest]]</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2007-06-12T22:55:11Z<p>Mstrobert: /* Prepare debootstrap */ cp -a flag should not be used since preserves user ownership</p>
<hr />
<div>How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Prepare debootstrap==<br />
You will need the debootstrap script for your desired Ubuntu release (eg dapper, feisty).<br />
<br />
Download the debootstrap deb for Ubuntu's latest release from [http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=debootstrap&searchon=names&version=all&release=all here]. (eg, as of April 2007, download the debootstrap deb for feisty). You want the debootstrap from the latest release, even if you want to install a previous release Ubuntu vserver guest.<br />
Extract the Ubuntu scripts from the deb and place them in <code>/usr/lib/debootstrap/scripts/</code>.<br />
<br />
For example, do something like:<br />
$ cd /tmp<br />
$ wget http://mirrors.kernel.org/ubuntu/pool/main/d/debootstrap/debootstrap_0.3.3.2ubuntu3_all.deb<br />
$ dpkg --extract debootstrap_0.3.3.2ubuntu3_all.deb debootstrap-feisty<br />
$ sudo cp debootstrap-feisty/usr/lib/debootstrap/scripts/{warty,warty.buildd,hoary,hoary.buildd,breezy,dapper,edgy,edgy.fakechroot,feisty,feisty.fakechroot} /usr/lib/debootstrap/scripts/<br />
<br />
==Build==<br />
===Build with guest architecture the same as host===<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/<br />
===Build 32-bit guest on 64-bit host===<br />
# vserver feisty-guest-32 build -m debootstrap --hostname feisty-guest-32 --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/ -- --arch i386<br />
Verify 32-bitness of guest:<br />
host:# file /var/lib/vservers/feisty-guest-32/bin/ls<br />
/var/lib/vservers/feisty-guest-32/bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.0, dynamically linked (uses shared libs), for GNU/Linux 2.6.0, stripped<br />
<br />
==See also==<br />
* [[Frequently_Asked_Questions#I_run_a_Debian_host_and_want_to_build_an_Ubuntu_guest._Howto.3F]]<br />
* [[Installing 32-bit Fedora on 64-bit Debian]]</div>Mstroberthttp://www.linux-vserver.org/Installing_32-bit_Fedora_on_64-bit_DebianInstalling 32-bit Fedora on 64-bit Debian2007-06-12T22:40:34Z<p>Mstrobert: /* Verify */ added section See also</p>
<hr />
<div>Guide to install a 32-bit Fedora guest into a 64-bit Debian host.<br />
__TOC__<br />
==Set up yum repository==<br />
host# mkdir /etc/rpm<br />
host# mkdir /var/lib/rpm<br />
host# apt-get install yum linux32<br />
host# cp -a /usr/lib/util-vserver/distributions/fc6/{yum,yum.repos.d} /etc/vservers/.distributions/fc6<br />
<br />
vserver build does not use /etc/yum*, though you will see an ignorable error message about it if it doesn't exist. <br />
<br />
Edit the files /etc/vservers/.distributions/fc6/yum.repos.d/fedora-{core,updates,extras}.repo<br />
* Uncomment the first baseurl= line of each file (by removing the leading # character)<br />
<br />
===Proxy===<br />
If you use a proxy, append to /etc/vservers/.distributions/fc6/yum/yum.conf (in the [main] section) a line of the form:<br />
proxy=http://proxy.yourcompany.com:3128<br />
<br />
==Build vserver==<br />
host# export ARCH=i386<br />
host# export http_proxy=http://proxy.yourcompany.com:3128<br />
host# linux32 vserver fedora-zod-32-gustname build -m yum --hostname=fedora-zod-32-guestname --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d fc6 -- --arch i386<br />
host# unset ARCH<br />
<br />
==Verify==<br />
To observe the 32-bitness of the guest's applications, do:<br />
host# linux32 vyum fedora-zod-32-guestname -- install file<br />
host# vserver fedora-zod-32-guestname start<br />
host# vserver fedora-zod-32-guestname enter<br />
fedora-zod-32-guestname# file /bin/ls<br />
/bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped<br />
or<br />
host# file /var/lib/vservers/fedora-zod-32-guestname/bin/ls<br />
/var/lib/vservers/fedora-zod-32-guestname/bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped<br />
==See also==<br />
* [[Installing Ubuntu on Debian]]</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2007-06-12T22:39:02Z<p>Mstrobert: /* See also */ added reference to Installing 32-bit Fedora on 64-bit Debian</p>
<hr />
<div>How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Prepare debootstrap==<br />
You will need the debootstrap script for your desired Ubuntu release (eg dapper, feisty).<br />
<br />
Download the debootstrap deb for Ubuntu's latest release from [http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=debootstrap&searchon=names&version=all&release=all here]. (eg, as of April 2007, download the debootstrap deb for feisty). You want the debootstrap from the latest release, even if you want to install a previous release Ubuntu vserver guest.<br />
Extract the Ubuntu scripts from the deb and place them in <code>/usr/lib/debootstrap/scripts/</code>.<br />
<br />
For example, do something like:<br />
$ cd /tmp<br />
$ wget http://mirrors.kernel.org/ubuntu/pool/main/d/debootstrap/debootstrap_0.3.3.2ubuntu3_all.deb<br />
$ dpkg --extract debootstrap_0.3.3.2ubuntu3_all.deb debootstrap-feisty<br />
$ sudo cp -a debootstrap-feisty/usr/lib/debootstrap/scripts/{warty,warty.buildd,hoary,hoary.buildd,breezy,dapper,edgy,edgy.fakechroot,feisty,feisty.fakechroot} /usr/lib/debootstrap/scripts/<br />
<br />
==Build==<br />
===Build with guest architecture the same as host===<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/<br />
===Build 32-bit guest on 64-bit host===<br />
# vserver feisty-guest-32 build -m debootstrap --hostname feisty-guest-32 --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/ -- --arch i386<br />
Verify 32-bitness of guest:<br />
host:# file /var/lib/vservers/feisty-guest-32/bin/ls<br />
/var/lib/vservers/feisty-guest-32/bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.0, dynamically linked (uses shared libs), for GNU/Linux 2.6.0, stripped<br />
<br />
==See also==<br />
* [[Frequently_Asked_Questions#I_run_a_Debian_host_and_want_to_build_an_Ubuntu_guest._Howto.3F]]<br />
* [[Installing 32-bit Fedora on 64-bit Debian]]</div>Mstroberthttp://www.linux-vserver.org/DocumentationDocumentation2007-06-12T22:37:10Z<p>Mstrobert: /* Guides and Howtos */ added link to Installing Ubuntu on Debian</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 />
* [[some small howto for Fedorro TM os]]<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 />
* [[yum-patch:Documentation|How to patch vyum]]<br />
<br />
== Guides and Howtos ==<br />
<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 />
<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>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2007-06-12T22:35:00Z<p>Mstrobert: /* Build 32-bit guest on 64-bit host */ added how to verify 32bitness</p>
<hr />
<div>How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Prepare debootstrap==<br />
You will need the debootstrap script for your desired Ubuntu release (eg dapper, feisty).<br />
<br />
Download the debootstrap deb for Ubuntu's latest release from [http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=debootstrap&searchon=names&version=all&release=all here]. (eg, as of April 2007, download the debootstrap deb for feisty). You want the debootstrap from the latest release, even if you want to install a previous release Ubuntu vserver guest.<br />
Extract the Ubuntu scripts from the deb and place them in <code>/usr/lib/debootstrap/scripts/</code>.<br />
<br />
For example, do something like:<br />
$ cd /tmp<br />
$ wget http://mirrors.kernel.org/ubuntu/pool/main/d/debootstrap/debootstrap_0.3.3.2ubuntu3_all.deb<br />
$ dpkg --extract debootstrap_0.3.3.2ubuntu3_all.deb debootstrap-feisty<br />
$ sudo cp -a debootstrap-feisty/usr/lib/debootstrap/scripts/{warty,warty.buildd,hoary,hoary.buildd,breezy,dapper,edgy,edgy.fakechroot,feisty,feisty.fakechroot} /usr/lib/debootstrap/scripts/<br />
<br />
==Build==<br />
===Build with guest architecture the same as host===<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/<br />
===Build 32-bit guest on 64-bit host===<br />
# vserver feisty-guest-32 build -m debootstrap --hostname feisty-guest-32 --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/ -- --arch i386<br />
Verify 32-bitness of guest:<br />
host:# file /var/lib/vservers/feisty-guest-32/bin/ls<br />
/var/lib/vservers/feisty-guest-32/bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.0, dynamically linked (uses shared libs), for GNU/Linux 2.6.0, stripped<br />
<br />
==See also==<br />
[[Frequently_Asked_Questions#I_run_a_Debian_host_and_want_to_build_an_Ubuntu_guest._Howto.3F]]</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2007-06-12T22:30:10Z<p>Mstrobert: /* Build */ added 32bit on 64bit</p>
<hr />
<div>How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Prepare debootstrap==<br />
You will need the debootstrap script for your desired Ubuntu release (eg dapper, feisty).<br />
<br />
Download the debootstrap deb for Ubuntu's latest release from [http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=debootstrap&searchon=names&version=all&release=all here]. (eg, as of April 2007, download the debootstrap deb for feisty). You want the debootstrap from the latest release, even if you want to install a previous release Ubuntu vserver guest.<br />
Extract the Ubuntu scripts from the deb and place them in <code>/usr/lib/debootstrap/scripts/</code>.<br />
<br />
For example, do something like:<br />
$ cd /tmp<br />
$ wget http://mirrors.kernel.org/ubuntu/pool/main/d/debootstrap/debootstrap_0.3.3.2ubuntu3_all.deb<br />
$ dpkg --extract debootstrap_0.3.3.2ubuntu3_all.deb debootstrap-feisty<br />
$ sudo cp -a debootstrap-feisty/usr/lib/debootstrap/scripts/{warty,warty.buildd,hoary,hoary.buildd,breezy,dapper,edgy,edgy.fakechroot,feisty,feisty.fakechroot} /usr/lib/debootstrap/scripts/<br />
<br />
==Build==<br />
===Build with guest architecture the same as host===<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/<br />
===Build 32-bit guest on 64-bit host===<br />
# vserver feisty-guest-32 build -m debootstrap --hostname feisty-guest-32 --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/ -- --arch i386<br />
<br />
==See also==<br />
[[Frequently_Asked_Questions#I_run_a_Debian_host_and_want_to_build_an_Ubuntu_guest._Howto.3F]]</div>Mstroberthttp://www.linux-vserver.org/Installing_32-bit_Fedora_on_64-bit_DebianInstalling 32-bit Fedora on 64-bit Debian2007-06-12T21:54:28Z<p>Mstrobert: /* Verify */ added another verification method</p>
<hr />
<div>Guide to install a 32-bit Fedora guest into a 64-bit Debian host.<br />
__TOC__<br />
==Set up yum repository==<br />
host# mkdir /etc/rpm<br />
host# mkdir /var/lib/rpm<br />
host# apt-get install yum linux32<br />
host# cp -a /usr/lib/util-vserver/distributions/fc6/{yum,yum.repos.d} /etc/vservers/.distributions/fc6<br />
<br />
vserver build does not use /etc/yum*, though you will see an ignorable error message about it if it doesn't exist. <br />
<br />
Edit the files /etc/vservers/.distributions/fc6/yum.repos.d/fedora-{core,updates,extras}.repo<br />
* Uncomment the first baseurl= line of each file (by removing the leading # character)<br />
<br />
===Proxy===<br />
If you use a proxy, append to /etc/vservers/.distributions/fc6/yum/yum.conf (in the [main] section) a line of the form:<br />
proxy=http://proxy.yourcompany.com:3128<br />
<br />
==Build vserver==<br />
host# export ARCH=i386<br />
host# export http_proxy=http://proxy.yourcompany.com:3128<br />
host# linux32 vserver fedora-zod-32-gustname build -m yum --hostname=fedora-zod-32-guestname --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d fc6 -- --arch i386<br />
host# unset ARCH<br />
<br />
==Verify==<br />
To observe the 32-bitness of the guest's applications, do:<br />
host# linux32 vyum fedora-zod-32-guestname -- install file<br />
host# vserver fedora-zod-32-guestname start<br />
host# vserver fedora-zod-32-guestname enter<br />
fedora-zod-32-guestname# file /bin/ls<br />
/bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped<br />
or<br />
host# file /var/lib/vservers/fedora-zod-32-guestname/bin/ls<br />
/var/lib/vservers/fedora-zod-32-guestname/bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2007-06-12T21:22:50Z<p>Mstrobert: /* Prepare debootstrap */ what to do with the deb</p>
<hr />
<div>How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Prepare debootstrap==<br />
You will need the debootstrap script for your desired Ubuntu release (eg dapper, feisty).<br />
<br />
Download the debootstrap deb for Ubuntu's latest release from [http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=debootstrap&searchon=names&version=all&release=all here]. (eg, as of April 2007, download the debootstrap deb for feisty). You want the debootstrap from the latest release, even if you want to install a previous release Ubuntu vserver guest.<br />
Extract the Ubuntu scripts from the deb and place them in <code>/usr/lib/debootstrap/scripts/</code>.<br />
<br />
For example, do something like:<br />
$ cd /tmp<br />
$ wget http://mirrors.kernel.org/ubuntu/pool/main/d/debootstrap/debootstrap_0.3.3.2ubuntu3_all.deb<br />
$ dpkg --extract debootstrap_0.3.3.2ubuntu3_all.deb debootstrap-feisty<br />
$ sudo cp -a debootstrap-feisty/usr/lib/debootstrap/scripts/{warty,warty.buildd,hoary,hoary.buildd,breezy,dapper,edgy,edgy.fakechroot,feisty,feisty.fakechroot} /usr/lib/debootstrap/scripts/<br />
<br />
==Build==<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/<br />
<br />
==See also==<br />
[[Frequently_Asked_Questions#I_run_a_Debian_host_and_want_to_build_an_Ubuntu_guest._Howto.3F]]</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2007-06-11T23:55:04Z<p>Mstrobert: Removed the warning-unfinished line, as the procedure works.</p>
<hr />
<div>How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Prepare debootstrap==<br />
You will need the debootstrap script for your desired Ubuntu release (eg dapper, feisty).<br />
<br />
Download the debootstrap deb for Ubuntu's latest release from [http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=debootstrap&searchon=names&version=all&release=all here]. (eg, as of April 2007, download the debootstrap deb for feisty). You want the debootstrap from the latest release, even if you want to install a previous release vserver guest.<br />
<br />
==Build==<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/<br />
<br />
==See also==<br />
[[Frequently_Asked_Questions#I_run_a_Debian_host_and_want_to_build_an_Ubuntu_guest._Howto.3F]]</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2007-06-11T23:44:23Z<p>Mstrobert: /* Build */ fixed bad command line</p>
<hr />
<div>[ A WORK IN PROGRESS - STILL WRITING ]<br />
<br />
How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Prepare debootstrap==<br />
You will need the debootstrap script for your desired Ubuntu release (eg dapper, feisty).<br />
<br />
Download the debootstrap deb for Ubuntu's latest release from [http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=debootstrap&searchon=names&version=all&release=all here]. (eg, as of April 2007, download the debootstrap deb for feisty). You want the debootstrap from the latest release, even if you want to install a previous release vserver guest.<br />
<br />
==Build==<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -m http://us.archive.ubuntu.com/<br />
<br />
==See also==<br />
[[Frequently_Asked_Questions#I_run_a_Debian_host_and_want_to_build_an_Ubuntu_guest._Howto.3F]]</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2007-06-11T23:15:54Z<p>Mstrobert: /* Prepare debootstrap */ added instruction to download ubuntu debootstrap</p>
<hr />
<div>[ A WORK IN PROGRESS - STILL WRITING ]<br />
<br />
How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Prepare debootstrap==<br />
You will need the debootstrap script for your desired Ubuntu release (eg dapper, feisty).<br />
<br />
Download the debootstrap deb for Ubuntu's latest release from [http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=debootstrap&searchon=names&version=all&release=all here]. (eg, as of April 2007, download the debootstrap deb for feisty). You want the debootstrap from the latest release, even if you want to install a previous release vserver guest.<br />
<br />
==Build==<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -- --mirror http://us.archive.ubuntu.com/<br />
==See also==<br />
[[Frequently_Asked_Questions#I_run_a_Debian_host_and_want_to_build_an_Ubuntu_guest._Howto.3F]]</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2007-06-11T23:02:49Z<p>Mstrobert: /* Prepare debootstrap */</p>
<hr />
<div>[ A WORK IN PROGRESS - STILL WRITING ]<br />
<br />
How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Prepare debootstrap==<br />
You will need the debootstrap script for your desired Ubuntu release (eg dapper, feisty).<br />
<br />
==Build==<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -- --mirror http://us.archive.ubuntu.com/<br />
==See also==<br />
[[Frequently_Asked_Questions#I_run_a_Debian_host_and_want_to_build_an_Ubuntu_guest._Howto.3F]]</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2007-06-11T23:01:18Z<p>Mstrobert: Added section Prepare debootstrap</p>
<hr />
<div>[ A WORK IN PROGRESS - STILL WRITING ]<br />
<br />
How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Prepare debootstrap==<br />
==Build==<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -- --mirror http://us.archive.ubuntu.com/<br />
==See also==<br />
[[Frequently_Asked_Questions#I_run_a_Debian_host_and_want_to_build_an_Ubuntu_guest._Howto.3F]]</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2007-06-11T22:50:23Z<p>Mstrobert: /* See also */ made it a proper wiki link</p>
<hr />
<div>[ A WORK IN PROGRESS - STILL WRITING ]<br />
<br />
How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Build==<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -- --mirror http://us.archive.ubuntu.com/<br />
==See also==<br />
[[Frequently_Asked_Questions#I_run_a_Debian_host_and_want_to_build_an_Ubuntu_guest._Howto.3F]]</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2007-06-11T22:48:02Z<p>Mstrobert: /* Build */ added See also section</p>
<hr />
<div>[ A WORK IN PROGRESS - STILL WRITING ]<br />
<br />
How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Build==<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -- --mirror http://us.archive.ubuntu.com/<br />
==See also==<br />
[http://linux-vserver.org/Frequently_Asked_Questions#I_run_a_Debian_host_and_want_to_build_an_Ubuntu_guest._Howto.3F Related FAQ]</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2007-06-11T22:14:36Z<p>Mstrobert: Added Build section</p>
<hr />
<div>[ A WORK IN PROGRESS - STILL WRITING ]<br />
<br />
How to install an Ubuntu vserver guest on Debian.<br />
__TOC__<br />
==Build==<br />
# vserver feisty-guest build -m debootstrap --hostname feisty-guest --interface dummy0=eth0:10.0.0.123/8 --rootdir /var/lib/vservers -- -d feisty -- --mirror http://us.archive.ubuntu.com/</div>Mstroberthttp://www.linux-vserver.org/Installing_Ubuntu_on_DebianInstalling Ubuntu on Debian2007-06-11T22:02:52Z<p>Mstrobert: Initial page</p>
<hr />
<div>[ A WORK IN PROGRESS - STILL WRITING ]<br />
<br />
How to install an Ubuntu vserver guest on Debian.<br />
__TOC__</div>Mstroberthttp://www.linux-vserver.org/Installing_an_openSUSE_vserver_guestInstalling an openSUSE vserver guest2007-06-11T20:07:11Z<p>Mstrobert: /* Post install cleanup */ introduced prompt</p>
<hr />
<div>Installing and running openSUSE (previously knows as SUSE Linux) as a vserver guest.<br />
__TOC__<br />
==Test configuration==<br />
Host:<br />
* Debian Etch AMD64, Kernel 2.6.15.4-vs2.0.2-rc9, util-vserver 0.30.210 + similar patch, or<br />
* Debian Etch AMD64, 2.6.18-4-vserver-amd64, util-vserver 0.30.212-1 + patch (see below)<br />
Guest:<br />
* SLES 9, or<br />
* openSUSE 10.2<br />
<br />
==Running openSUSE vservers on a Debian server==<br />
===Installation===<br />
Debian is lacking the required rpm tools to install an openSUSE or SLES system directly via vserver build (the required apt-rpm is available in source only for apt-0.5.xx, and Debian is already at 0.6.xx).<br />
<br />
Therefore, use the normal openSUSE installation procedure and then copy the system to a vserver directory:<br />
* Install openSUSE on raw metal or in a virtual machine (such as [http://www.virtualbox.org/ VirtualBox]).<br />
* Boot from CD (openSUSE or Debian - whatever you prefer), or just boot into the OS and log in as root.<br />
* tar the whole system, copy it to the vserver host and untar it to the desired vserver location, usually <code>/var/lib/vservers/<servername></code><br />
* Create <code>/etc/vservers/<servername></code> manually, or copy it from another vserver.<br />
<br />
===Post install cleanup===<br />
* remove some startup service, either delete the appropriate /etc/init.d/.... links or run the following from inside the vserver:<br />
# chkconfig -d -f boot.swap boot.isapnp boot.idedma boot.loadmodules \<br />
boot.device-mapper boot.md boot.proc boot.shm boot.sched \<br />
boot.rootfsck hotplug boot.localfs boot.crypto boot.clock \<br />
boot.scpm boot.ipconfig<br />
<br />
# chkconfig -d -f coldplug irq_balancer random network fbset powersaved kbd hwscan<br />
* remove unneeded packages:<br />
# rpm -e irqbalance kernel-smp grub reiserfs xfsprogs raidtools ntfsprogs \<br />
module-init-tools mkinitrd powersave hotplug mdadm<br />
'''Note:''' there are a number of redundant packages remaining that can not be removed due to yast2 depending on them.<br />
<br />
===initscripts===<br />
openSUSE's <code>/etc/init.d/rc</code> expects two environment variables: <code>RUNLEVEL</code> and <code>PREVLEVEL</code>. The vserver.start script fails to set those. There are a couple workarounds:<br />
* Edit <code>/etc/init.d/rc</code> to set those values (not recommended (why?)). For example, inserting these lines near the top of the file:<br />
PREVLEVEL="N"<br />
RUNLEVEL="$1"<br />
* Apply the following patch to <code>vserver.start</code> to set the values:<br />
--- vserver.start,orig 2006-12-09 12:37:58.000000000 -0700<br />
+++ vserver.start 2007-06-11 12:27:27.000000000 -0600<br />
@@ -141,7 +141,7 @@<br />
$_VUNAME --xid self --set -t context="$VSERVER_DIR" -- \<br />
$_VATTRIBUTE --set "${OPTS_VATTRIBUTE[@]}" -- \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i "${OPTS_ENV[@]}" \<br />
+ $_ENV -i "${OPTS_ENV[@]}" PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_VCONTEXT --migrate-self --endsetup --chroot $SILENT_OPT \<br />
"${OPTS_VCONTEXT_MIGRATE[@]}" "${OPTS_VCONTEXT_ENTER[@]}" -- \<br />
"${INITCMD_START[@]}"<br />
@@ -157,7 +157,7 @@<br />
$_EXEC_ULIMIT "$VSERVER_DIR/ulimits" \<br />
$_CHCONTEXT_COMPAT "${CHCONTEXT_OPTS[@]}" "${CHCONTEXT_INIT_OPTS[@]}" \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i "${OPTS_ENV[@]}" \<br />
+ $_ENV -i "${OPTS_ENV[@]}" PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_CHAINECHO "${_IS_FAKEINIT:+$startsync_pipe}" "" \<br />
$_CAPCHROOT "${CAPCHROOT_OPTS[@]}" . \<br />
"${INITCMD_START[@]}"<br />
'''edit me:''' do we need to modify the <code>vserver.stop</code> script as well?</div>Mstroberthttp://www.linux-vserver.org/Installing_an_openSUSE_vserver_guestInstalling an openSUSE vserver guest2007-06-11T19:39:48Z<p>Mstrobert: Adding the word SUSE into the page so it shows up on suse searches</p>
<hr />
<div>Installing and running openSUSE (previously knows as SUSE Linux) as a vserver guest.<br />
__TOC__<br />
==Test configuration==<br />
Host:<br />
* Debian Etch AMD64, Kernel 2.6.15.4-vs2.0.2-rc9, util-vserver 0.30.210 + similar patch, or<br />
* Debian Etch AMD64, 2.6.18-4-vserver-amd64, util-vserver 0.30.212-1 + patch (see below)<br />
Guest:<br />
* SLES 9, or<br />
* openSUSE 10.2<br />
<br />
==Running openSUSE vservers on a Debian server==<br />
===Installation===<br />
Debian is lacking the required rpm tools to install an openSUSE or SLES system directly via vserver build (the required apt-rpm is available in source only for apt-0.5.xx, and Debian is already at 0.6.xx).<br />
<br />
Therefore, use the normal openSUSE installation procedure and then copy the system to a vserver directory:<br />
* Install openSUSE on raw metal or in a virtual machine (such as [http://www.virtualbox.org/ VirtualBox]).<br />
* Boot from CD (openSUSE or Debian - whatever you prefer), or just boot into the OS and log in as root.<br />
* tar the whole system, copy it to the vserver host and untar it to the desired vserver location, usually <code>/var/lib/vservers/<servername></code><br />
* Create <code>/etc/vservers/<servername></code> manually, or copy it from another vserver.<br />
<br />
===Post install cleanup===<br />
* remove some startup service, either delete the appropriate /etc/init.d/.... links or run the following from inside the vserver:<br />
chkconfig -d -f boot.swap boot.isapnp boot.idedma boot.loadmodules \<br />
boot.device-mapper boot.md boot.proc boot.shm boot.sched \<br />
boot.rootfsck hotplug boot.localfs boot.crypto boot.clock \<br />
boot.scpm boot.ipconfig<br />
<br />
chkconfig -d -f coldplug irq_balancer random network fbset powersaved kbd hwscan<br />
* remove unneeded packages:<br />
rpm -e irqbalance kernel-smp grub reiserfs xfsprogs raidtools ntfsprogs \<br />
module-init-tools mkinitrd powersave hotplug mdadm<br />
'''Note:''' there are a number of redundant packages remaining that can not be removed due to yast2 depending on them.<br />
<br />
===initscripts===<br />
openSUSE's <code>/etc/init.d/rc</code> expects two environment variables: <code>RUNLEVEL</code> and <code>PREVLEVEL</code>. The vserver.start script fails to set those. There are a couple workarounds:<br />
* Edit <code>/etc/init.d/rc</code> to set those values (not recommended (why?)). For example, inserting these lines near the top of the file:<br />
PREVLEVEL="N"<br />
RUNLEVEL="$1"<br />
* Apply the following patch to <code>vserver.start</code> to set the values:<br />
--- vserver.start,orig 2006-12-09 12:37:58.000000000 -0700<br />
+++ vserver.start 2007-06-11 12:27:27.000000000 -0600<br />
@@ -141,7 +141,7 @@<br />
$_VUNAME --xid self --set -t context="$VSERVER_DIR" -- \<br />
$_VATTRIBUTE --set "${OPTS_VATTRIBUTE[@]}" -- \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i "${OPTS_ENV[@]}" \<br />
+ $_ENV -i "${OPTS_ENV[@]}" PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_VCONTEXT --migrate-self --endsetup --chroot $SILENT_OPT \<br />
"${OPTS_VCONTEXT_MIGRATE[@]}" "${OPTS_VCONTEXT_ENTER[@]}" -- \<br />
"${INITCMD_START[@]}"<br />
@@ -157,7 +157,7 @@<br />
$_EXEC_ULIMIT "$VSERVER_DIR/ulimits" \<br />
$_CHCONTEXT_COMPAT "${CHCONTEXT_OPTS[@]}" "${CHCONTEXT_INIT_OPTS[@]}" \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i "${OPTS_ENV[@]}" \<br />
+ $_ENV -i "${OPTS_ENV[@]}" PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_CHAINECHO "${_IS_FAKEINIT:+$startsync_pipe}" "" \<br />
$_CAPCHROOT "${CAPCHROOT_OPTS[@]}" . \<br />
"${INITCMD_START[@]}"<br />
'''edit me:''' do we need to modify the <code>vserver.stop</code> script as well?</div>Mstroberthttp://www.linux-vserver.org/Installing_an_openSUSE_vserver_guestInstalling an openSUSE vserver guest2007-06-11T19:36:25Z<p>Mstrobert: /* Test configuration */ reflect updated patch</p>
<hr />
<div>Installing and running openSUSE as a vserver guest.<br />
__TOC__<br />
==Test configuration==<br />
Host:<br />
* Debian Etch AMD64, Kernel 2.6.15.4-vs2.0.2-rc9, util-vserver 0.30.210 + similar patch, or<br />
* Debian Etch AMD64, 2.6.18-4-vserver-amd64, util-vserver 0.30.212-1 + patch (see below)<br />
Guest:<br />
* SLES 9, or<br />
* openSUSE 10.2<br />
<br />
==Running openSUSE vservers on a Debian server==<br />
===Installation===<br />
Debian is lacking the required rpm tools to install an openSUSE or SLES system directly via vserver build (the required apt-rpm is available in source only for apt-0.5.xx, and Debian is already at 0.6.xx).<br />
<br />
Therefore, use the normal openSUSE installation procedure and then copy the system to a vserver directory:<br />
* Install openSUSE on raw metal or in a virtual machine (such as [http://www.virtualbox.org/ VirtualBox]).<br />
* Boot from CD (openSUSE or Debian - whatever you prefer), or just boot into the OS and log in as root.<br />
* tar the whole system, copy it to the vserver host and untar it to the desired vserver location, usually <code>/var/lib/vservers/<servername></code><br />
* Create <code>/etc/vservers/<servername></code> manually, or copy it from another vserver.<br />
<br />
===Post install cleanup===<br />
* remove some startup service, either delete the appropriate /etc/init.d/.... links or run the following from inside the vserver:<br />
chkconfig -d -f boot.swap boot.isapnp boot.idedma boot.loadmodules \<br />
boot.device-mapper boot.md boot.proc boot.shm boot.sched \<br />
boot.rootfsck hotplug boot.localfs boot.crypto boot.clock \<br />
boot.scpm boot.ipconfig<br />
<br />
chkconfig -d -f coldplug irq_balancer random network fbset powersaved kbd hwscan<br />
* remove unneeded packages:<br />
rpm -e irqbalance kernel-smp grub reiserfs xfsprogs raidtools ntfsprogs \<br />
module-init-tools mkinitrd powersave hotplug mdadm<br />
'''Note:''' there are a number of redundant packages remaining that can not be removed due to yast2 depending on them.<br />
<br />
===initscripts===<br />
openSUSE's <code>/etc/init.d/rc</code> expects two environment variables: <code>RUNLEVEL</code> and <code>PREVLEVEL</code>. The vserver.start script fails to set those. There are a couple workarounds:<br />
* Edit <code>/etc/init.d/rc</code> to set those values (not recommended (why?)). For example, inserting these lines near the top of the file:<br />
PREVLEVEL="N"<br />
RUNLEVEL="$1"<br />
* Apply the following patch to <code>vserver.start</code> to set the values:<br />
--- vserver.start,orig 2006-12-09 12:37:58.000000000 -0700<br />
+++ vserver.start 2007-06-11 12:27:27.000000000 -0600<br />
@@ -141,7 +141,7 @@<br />
$_VUNAME --xid self --set -t context="$VSERVER_DIR" -- \<br />
$_VATTRIBUTE --set "${OPTS_VATTRIBUTE[@]}" -- \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i "${OPTS_ENV[@]}" \<br />
+ $_ENV -i "${OPTS_ENV[@]}" PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_VCONTEXT --migrate-self --endsetup --chroot $SILENT_OPT \<br />
"${OPTS_VCONTEXT_MIGRATE[@]}" "${OPTS_VCONTEXT_ENTER[@]}" -- \<br />
"${INITCMD_START[@]}"<br />
@@ -157,7 +157,7 @@<br />
$_EXEC_ULIMIT "$VSERVER_DIR/ulimits" \<br />
$_CHCONTEXT_COMPAT "${CHCONTEXT_OPTS[@]}" "${CHCONTEXT_INIT_OPTS[@]}" \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i "${OPTS_ENV[@]}" \<br />
+ $_ENV -i "${OPTS_ENV[@]}" PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_CHAINECHO "${_IS_FAKEINIT:+$startsync_pipe}" "" \<br />
$_CAPCHROOT "${CAPCHROOT_OPTS[@]}" . \<br />
"${INITCMD_START[@]}"<br />
'''edit me:''' do we need to modify the <code>vserver.stop</code> script as well?</div>Mstroberthttp://www.linux-vserver.org/Installing_an_openSUSE_vserver_guestInstalling an openSUSE vserver guest2007-06-11T18:32:44Z<p>Mstrobert: /* initscripts */ updated patch for newer vserver version</p>
<hr />
<div>Installing and running openSUSE as a vserver guest.<br />
__TOC__<br />
==Test configuration==<br />
Host:<br />
* Debian Etch AMD64, Kernel 2.6.15.4-vs2.0.2-rc9, util-vserver 0.30.210 + patch (see below), or<br />
* Debian Etch AMD64, 2.6.18-4-vserver-amd64, util-vserver 0.30.212-1 (+patch)<br />
Guest:<br />
* SLES 9, or<br />
* openSUSE 10.2<br />
<br />
==Running openSUSE vservers on a Debian server==<br />
===Installation===<br />
Debian is lacking the required rpm tools to install an openSUSE or SLES system directly via vserver build (the required apt-rpm is available in source only for apt-0.5.xx, and Debian is already at 0.6.xx).<br />
<br />
Therefore, use the normal openSUSE installation procedure and then copy the system to a vserver directory:<br />
* Install openSUSE on raw metal or in a virtual machine (such as [http://www.virtualbox.org/ VirtualBox]).<br />
* Boot from CD (openSUSE or Debian - whatever you prefer), or just boot into the OS and log in as root.<br />
* tar the whole system, copy it to the vserver host and untar it to the desired vserver location, usually <code>/var/lib/vservers/<servername></code><br />
* Create <code>/etc/vservers/<servername></code> manually, or copy it from another vserver.<br />
<br />
===Post install cleanup===<br />
* remove some startup service, either delete the appropriate /etc/init.d/.... links or run the following from inside the vserver:<br />
chkconfig -d -f boot.swap boot.isapnp boot.idedma boot.loadmodules \<br />
boot.device-mapper boot.md boot.proc boot.shm boot.sched \<br />
boot.rootfsck hotplug boot.localfs boot.crypto boot.clock \<br />
boot.scpm boot.ipconfig<br />
<br />
chkconfig -d -f coldplug irq_balancer random network fbset powersaved kbd hwscan<br />
* remove unneeded packages:<br />
rpm -e irqbalance kernel-smp grub reiserfs xfsprogs raidtools ntfsprogs \<br />
module-init-tools mkinitrd powersave hotplug mdadm<br />
'''Note:''' there are a number of redundant packages remaining that can not be removed due to yast2 depending on them.<br />
<br />
===initscripts===<br />
openSUSE's <code>/etc/init.d/rc</code> expects two environment variables: <code>RUNLEVEL</code> and <code>PREVLEVEL</code>. The vserver.start script fails to set those. There are a couple workarounds:<br />
* Edit <code>/etc/init.d/rc</code> to set those values (not recommended (why?)). For example, inserting these lines near the top of the file:<br />
PREVLEVEL="N"<br />
RUNLEVEL="$1"<br />
* Apply the following patch to <code>vserver.start</code> to set the values:<br />
--- vserver.start,orig 2006-12-09 12:37:58.000000000 -0700<br />
+++ vserver.start 2007-06-11 12:27:27.000000000 -0600<br />
@@ -141,7 +141,7 @@<br />
$_VUNAME --xid self --set -t context="$VSERVER_DIR" -- \<br />
$_VATTRIBUTE --set "${OPTS_VATTRIBUTE[@]}" -- \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i "${OPTS_ENV[@]}" \<br />
+ $_ENV -i "${OPTS_ENV[@]}" PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_VCONTEXT --migrate-self --endsetup --chroot $SILENT_OPT \<br />
"${OPTS_VCONTEXT_MIGRATE[@]}" "${OPTS_VCONTEXT_ENTER[@]}" -- \<br />
"${INITCMD_START[@]}"<br />
@@ -157,7 +157,7 @@<br />
$_EXEC_ULIMIT "$VSERVER_DIR/ulimits" \<br />
$_CHCONTEXT_COMPAT "${CHCONTEXT_OPTS[@]}" "${CHCONTEXT_INIT_OPTS[@]}" \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i "${OPTS_ENV[@]}" \<br />
+ $_ENV -i "${OPTS_ENV[@]}" PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_CHAINECHO "${_IS_FAKEINIT:+$startsync_pipe}" "" \<br />
$_CAPCHROOT "${CAPCHROOT_OPTS[@]}" . \<br />
"${INITCMD_START[@]}"<br />
'''edit me:''' do we need to modify the <code>vserver.stop</code> script as well?</div>Mstroberthttp://www.linux-vserver.org/Installing_an_openSUSE_vserver_guestInstalling an openSUSE vserver guest2007-06-07T23:32:23Z<p>Mstrobert: /* initscripts */ added example of a case</p>
<hr />
<div>Installing and running openSUSE as a vserver guest.<br />
__TOC__<br />
==Test configuration==<br />
Host:<br />
* Debian Etch AMD64, Kernel 2.6.15.4-vs2.0.2-rc9, util-vserver 0.30.210 + patch (see below), or<br />
* Debian Etch AMD64, 2.6.18-4-vserver-amd64, util-vserver 0.30.212-1 (+patch)<br />
Guest:<br />
* SLES 9, or<br />
* openSUSE 10.2<br />
<br />
==Running openSUSE vservers on a Debian server==<br />
===Installation===<br />
Debian is lacking the required rpm tools to install an openSUSE or SLES system directly via vserver build (the required apt-rpm is available in source only for apt-0.5.xx, and Debian is already at 0.6.xx).<br />
<br />
Therefore, use the normal openSUSE installation procedure and then copy the system to a vserver directory:<br />
* Install openSUSE on raw metal or in a virtual machine (such as [http://www.virtualbox.org/ VirtualBox]).<br />
* Boot from CD (openSUSE or Debian - whatever you prefer), or just boot into the OS and log in as root.<br />
* tar the whole system, copy it to the vserver host and untar it to the desired vserver location, usually <code>/var/lib/vservers/<servername></code><br />
* Create <code>/etc/vservers/<servername></code> manually, or copy it from another vserver.<br />
<br />
===Post install cleanup===<br />
* remove some startup service, either delete the appropriate /etc/init.d/.... links or run the following from inside the vserver:<br />
chkconfig -d -f boot.swap boot.isapnp boot.idedma boot.loadmodules \<br />
boot.device-mapper boot.md boot.proc boot.shm boot.sched \<br />
boot.rootfsck hotplug boot.localfs boot.crypto boot.clock \<br />
boot.scpm boot.ipconfig<br />
<br />
chkconfig -d -f coldplug irq_balancer random network fbset powersaved kbd hwscan<br />
* remove unneeded packages:<br />
rpm -e irqbalance kernel-smp grub reiserfs xfsprogs raidtools ntfsprogs \<br />
module-init-tools mkinitrd powersave hotplug mdadm<br />
'''Note:''' there are a number of redundant packages remaining that can not be removed due to yast2 depending on them.<br />
<br />
===initscripts===<br />
openSUSE's <code>/etc/init.d/rc</code> expects two environment variables: <code>RUNLEVEL</code> and <code>PREVLEVEL</code>. The vserver.start script fails to set those. There are a couple workarounds:<br />
* Edit <code>/etc/init.d/rc</code> to set those values (not recommended). For example, inserting these lines near the top of the file:<br />
PREVLEVEL="N"<br />
RUNLEVEL="$1"<br />
* Apply the following patch to <code>vserver.start</code> to set the values:<br />
--- vserver.start.orig 2006-03-02 10:37:49.000000000 +0000<br />
+++ vserver.start 2006-03-02 10:10:36.000000000 +0000<br />
@@ -135,7 +134,7 @@<br />
$_VUNAME --xid self --set -t context="$VSERVER_DIR" -- \<br />
$_VATTRIBUTE --set "${OPTS_VATTRIBUTE[@]}" -- \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_VCONTEXT --migrate-self --endsetup --chroot $SILENT_OPT \<br />
"${OPTS_VCONTEXT_MIGRATE[@]}" "${OPTS_VCONTEXT_ENTER[@]}" -- \<br />
"${INITCMD_START[@]}"<br />
@@ -151,7 +150,7 @@<br />
$_EXEC_ULIMIT "$VSERVER_DIR/ulimits" \<br />
$_CHCONTEXT_COMPAT "${CHCONTEXT_OPTS[@]}" "${CHCONTEXT_INIT_OPTS[@]}" \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_CHAINECHO "${_IS_FAKEINIT:+$startsync_pipe}" "" \<br />
$_CAPCHROOT "${CAPCHROOT_OPTS[@]}" . \<br />
"${INITCMD_START[@]}"<br />
'''edit me:''' do we need to modify the <code>vserver.stop</code> script as well?</div>Mstroberthttp://www.linux-vserver.org/Installing_an_openSUSE_vserver_guestInstalling an openSUSE vserver guest2007-06-07T23:30:03Z<p>Mstrobert: /* initscripts */ case, styles</p>
<hr />
<div>Installing and running openSUSE as a vserver guest.<br />
__TOC__<br />
==Test configuration==<br />
Host:<br />
* Debian Etch AMD64, Kernel 2.6.15.4-vs2.0.2-rc9, util-vserver 0.30.210 + patch (see below), or<br />
* Debian Etch AMD64, 2.6.18-4-vserver-amd64, util-vserver 0.30.212-1 (+patch)<br />
Guest:<br />
* SLES 9, or<br />
* openSUSE 10.2<br />
<br />
==Running openSUSE vservers on a Debian server==<br />
===Installation===<br />
Debian is lacking the required rpm tools to install an openSUSE or SLES system directly via vserver build (the required apt-rpm is available in source only for apt-0.5.xx, and Debian is already at 0.6.xx).<br />
<br />
Therefore, use the normal openSUSE installation procedure and then copy the system to a vserver directory:<br />
* Install openSUSE on raw metal or in a virtual machine (such as [http://www.virtualbox.org/ VirtualBox]).<br />
* Boot from CD (openSUSE or Debian - whatever you prefer), or just boot into the OS and log in as root.<br />
* tar the whole system, copy it to the vserver host and untar it to the desired vserver location, usually <code>/var/lib/vservers/<servername></code><br />
* Create <code>/etc/vservers/<servername></code> manually, or copy it from another vserver.<br />
<br />
===Post install cleanup===<br />
* remove some startup service, either delete the appropriate /etc/init.d/.... links or run the following from inside the vserver:<br />
chkconfig -d -f boot.swap boot.isapnp boot.idedma boot.loadmodules \<br />
boot.device-mapper boot.md boot.proc boot.shm boot.sched \<br />
boot.rootfsck hotplug boot.localfs boot.crypto boot.clock \<br />
boot.scpm boot.ipconfig<br />
<br />
chkconfig -d -f coldplug irq_balancer random network fbset powersaved kbd hwscan<br />
* remove unneeded packages:<br />
rpm -e irqbalance kernel-smp grub reiserfs xfsprogs raidtools ntfsprogs \<br />
module-init-tools mkinitrd powersave hotplug mdadm<br />
'''Note:''' there are a number of redundant packages remaining that can not be removed due to yast2 depending on them.<br />
<br />
===initscripts===<br />
openSUSE's <code>/etc/init.d/rc</code> expects two environment variables: <code>RUNLEVEL</code> and <code>PREVLEVEL</code>. The vserver.start script fails to set those. There are a couple workarounds:<br />
* Edit <code>/etc/init.d/rc</code> to set those values (not recommended)<br />
* Apply the following patch to <code>vserver.start</code> to set the values:<br />
--- vserver.start.orig 2006-03-02 10:37:49.000000000 +0000<br />
+++ vserver.start 2006-03-02 10:10:36.000000000 +0000<br />
@@ -135,7 +134,7 @@<br />
$_VUNAME --xid self --set -t context="$VSERVER_DIR" -- \<br />
$_VATTRIBUTE --set "${OPTS_VATTRIBUTE[@]}" -- \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_VCONTEXT --migrate-self --endsetup --chroot $SILENT_OPT \<br />
"${OPTS_VCONTEXT_MIGRATE[@]}" "${OPTS_VCONTEXT_ENTER[@]}" -- \<br />
"${INITCMD_START[@]}"<br />
@@ -151,7 +150,7 @@<br />
$_EXEC_ULIMIT "$VSERVER_DIR/ulimits" \<br />
$_CHCONTEXT_COMPAT "${CHCONTEXT_OPTS[@]}" "${CHCONTEXT_INIT_OPTS[@]}" \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_CHAINECHO "${_IS_FAKEINIT:+$startsync_pipe}" "" \<br />
$_CAPCHROOT "${CAPCHROOT_OPTS[@]}" . \<br />
"${INITCMD_START[@]}"<br />
'''edit me:''' do we need to modify the <code>vserver.stop</code> script as well?</div>Mstroberthttp://www.linux-vserver.org/Installing_an_openSUSE_vserver_guestInstalling an openSUSE vserver guest2007-06-07T23:27:49Z<p>Mstrobert: /* initscripts */ styles, typos</p>
<hr />
<div>Installing and running openSUSE as a vserver guest.<br />
__TOC__<br />
==Test configuration==<br />
Host:<br />
* Debian Etch AMD64, Kernel 2.6.15.4-vs2.0.2-rc9, util-vserver 0.30.210 + patch (see below), or<br />
* Debian Etch AMD64, 2.6.18-4-vserver-amd64, util-vserver 0.30.212-1 (+patch)<br />
Guest:<br />
* SLES 9, or<br />
* openSUSE 10.2<br />
<br />
==Running openSUSE vservers on a Debian server==<br />
===Installation===<br />
Debian is lacking the required rpm tools to install an openSUSE or SLES system directly via vserver build (the required apt-rpm is available in source only for apt-0.5.xx, and Debian is already at 0.6.xx).<br />
<br />
Therefore, use the normal openSUSE installation procedure and then copy the system to a vserver directory:<br />
* Install openSUSE on raw metal or in a virtual machine (such as [http://www.virtualbox.org/ VirtualBox]).<br />
* Boot from CD (openSUSE or Debian - whatever you prefer), or just boot into the OS and log in as root.<br />
* tar the whole system, copy it to the vserver host and untar it to the desired vserver location, usually <code>/var/lib/vservers/<servername></code><br />
* Create <code>/etc/vservers/<servername></code> manually, or copy it from another vserver.<br />
<br />
===Post install cleanup===<br />
* remove some startup service, either delete the appropriate /etc/init.d/.... links or run the following from inside the vserver:<br />
chkconfig -d -f boot.swap boot.isapnp boot.idedma boot.loadmodules \<br />
boot.device-mapper boot.md boot.proc boot.shm boot.sched \<br />
boot.rootfsck hotplug boot.localfs boot.crypto boot.clock \<br />
boot.scpm boot.ipconfig<br />
<br />
chkconfig -d -f coldplug irq_balancer random network fbset powersaved kbd hwscan<br />
* remove unneeded packages:<br />
rpm -e irqbalance kernel-smp grub reiserfs xfsprogs raidtools ntfsprogs \<br />
module-init-tools mkinitrd powersave hotplug mdadm<br />
'''Note:''' there are a number of redundant packages remaining that can not be removed due to yast2 depending on them.<br />
<br />
===initscripts===<br />
openSUSE's /etc/init.d/rc expects two environment variables: <code>RUNLEVEL</code> and <code>PREVLEVEL</code>. The vserver.start script fails to set those. We've got workarounds:<br />
a) edit /etc/init.d/rc to set those values (not recommended)<br />
b) apply the following patch to vserver.start to set the values:<br />
--- vserver.start.orig 2006-03-02 10:37:49.000000000 +0000<br />
+++ vserver.start 2006-03-02 10:10:36.000000000 +0000<br />
@@ -135,7 +134,7 @@<br />
$_VUNAME --xid self --set -t context="$VSERVER_DIR" -- \<br />
$_VATTRIBUTE --set "${OPTS_VATTRIBUTE[@]}" -- \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_VCONTEXT --migrate-self --endsetup --chroot $SILENT_OPT \<br />
"${OPTS_VCONTEXT_MIGRATE[@]}" "${OPTS_VCONTEXT_ENTER[@]}" -- \<br />
"${INITCMD_START[@]}"<br />
@@ -151,7 +150,7 @@<br />
$_EXEC_ULIMIT "$VSERVER_DIR/ulimits" \<br />
$_CHCONTEXT_COMPAT "${CHCONTEXT_OPTS[@]}" "${CHCONTEXT_INIT_OPTS[@]}" \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_CHAINECHO "${_IS_FAKEINIT:+$startsync_pipe}" "" \<br />
$_CAPCHROOT "${CAPCHROOT_OPTS[@]}" . \<br />
"${INITCMD_START[@]}"<br />
'''edit me:''' do we need to modify the vserver.stop script as well?</div>Mstroberthttp://www.linux-vserver.org/Installing_an_openSUSE_vserver_guestInstalling an openSUSE vserver guest2007-06-07T23:15:44Z<p>Mstrobert: /* initscripts */ distro naming</p>
<hr />
<div>Installing and running openSUSE as a vserver guest.<br />
__TOC__<br />
==Test configuration==<br />
Host:<br />
* Debian Etch AMD64, Kernel 2.6.15.4-vs2.0.2-rc9, util-vserver 0.30.210 + patch (see below), or<br />
* Debian Etch AMD64, 2.6.18-4-vserver-amd64, util-vserver 0.30.212-1 (+patch)<br />
Guest:<br />
* SLES 9, or<br />
* openSUSE 10.2<br />
<br />
==Running openSUSE vservers on a Debian server==<br />
===Installation===<br />
Debian is lacking the required rpm tools to install an openSUSE or SLES system directly via vserver build (the required apt-rpm is available in source only for apt-0.5.xx, and Debian is already at 0.6.xx).<br />
<br />
Therefore, use the normal openSUSE installation procedure and then copy the system to a vserver directory:<br />
* Install openSUSE on raw metal or in a virtual machine (such as [http://www.virtualbox.org/ VirtualBox]).<br />
* Boot from CD (openSUSE or Debian - whatever you prefer), or just boot into the OS and log in as root.<br />
* tar the whole system, copy it to the vserver host and untar it to the desired vserver location, usually <code>/var/lib/vservers/<servername></code><br />
* Create <code>/etc/vservers/<servername></code> manually, or copy it from another vserver.<br />
<br />
===Post install cleanup===<br />
* remove some startup service, either delete the appropriate /etc/init.d/.... links or run the following from inside the vserver:<br />
chkconfig -d -f boot.swap boot.isapnp boot.idedma boot.loadmodules \<br />
boot.device-mapper boot.md boot.proc boot.shm boot.sched \<br />
boot.rootfsck hotplug boot.localfs boot.crypto boot.clock \<br />
boot.scpm boot.ipconfig<br />
<br />
chkconfig -d -f coldplug irq_balancer random network fbset powersaved kbd hwscan<br />
* remove unneeded packages:<br />
rpm -e irqbalance kernel-smp grub reiserfs xfsprogs raidtools ntfsprogs \<br />
module-init-tools mkinitrd powersave hotplug mdadm<br />
'''Note:''' there are a number of redundant packages remaining that can not be removed due to yast2 depending on them.<br />
<br />
===initscripts===<br />
openSUSE's /etc/init.d/rc expects two enviromnet variables: RUNLEVEL and PREVLEVEL. the vserver.start scripts failes to set those. We've got workarrounds:<br />
a) edit /etc/init.d/rc to set those values (not recomended)<br />
b) apply the following patch to vserver.start to set the values:<br />
--- vserver.start.orig 2006-03-02 10:37:49.000000000 +0000<br />
+++ vserver.start 2006-03-02 10:10:36.000000000 +0000<br />
@@ -135,7 +134,7 @@<br />
$_VUNAME --xid self --set -t context="$VSERVER_DIR" -- \<br />
$_VATTRIBUTE --set "${OPTS_VATTRIBUTE[@]}" -- \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_VCONTEXT --migrate-self --endsetup --chroot $SILENT_OPT \<br />
"${OPTS_VCONTEXT_MIGRATE[@]}" "${OPTS_VCONTEXT_ENTER[@]}" -- \<br />
"${INITCMD_START[@]}"<br />
@@ -151,7 +150,7 @@<br />
$_EXEC_ULIMIT "$VSERVER_DIR/ulimits" \<br />
$_CHCONTEXT_COMPAT "${CHCONTEXT_OPTS[@]}" "${CHCONTEXT_INIT_OPTS[@]}" \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_CHAINECHO "${_IS_FAKEINIT:+$startsync_pipe}" "" \<br />
$_CAPCHROOT "${CAPCHROOT_OPTS[@]}" . \<br />
"${INITCMD_START[@]}"<br />
'''edit me:''' do we need to modify the vserver.stop script as well?</div>Mstroberthttp://www.linux-vserver.org/Installing_an_openSUSE_vserver_guestInstalling an openSUSE vserver guest2007-06-07T23:15:05Z<p>Mstrobert: /* Post install cleanup */ wording</p>
<hr />
<div>Installing and running openSUSE as a vserver guest.<br />
__TOC__<br />
==Test configuration==<br />
Host:<br />
* Debian Etch AMD64, Kernel 2.6.15.4-vs2.0.2-rc9, util-vserver 0.30.210 + patch (see below), or<br />
* Debian Etch AMD64, 2.6.18-4-vserver-amd64, util-vserver 0.30.212-1 (+patch)<br />
Guest:<br />
* SLES 9, or<br />
* openSUSE 10.2<br />
<br />
==Running openSUSE vservers on a Debian server==<br />
===Installation===<br />
Debian is lacking the required rpm tools to install an openSUSE or SLES system directly via vserver build (the required apt-rpm is available in source only for apt-0.5.xx, and Debian is already at 0.6.xx).<br />
<br />
Therefore, use the normal openSUSE installation procedure and then copy the system to a vserver directory:<br />
* Install openSUSE on raw metal or in a virtual machine (such as [http://www.virtualbox.org/ VirtualBox]).<br />
* Boot from CD (openSUSE or Debian - whatever you prefer), or just boot into the OS and log in as root.<br />
* tar the whole system, copy it to the vserver host and untar it to the desired vserver location, usually <code>/var/lib/vservers/<servername></code><br />
* Create <code>/etc/vservers/<servername></code> manually, or copy it from another vserver.<br />
<br />
===Post install cleanup===<br />
* remove some startup service, either delete the appropriate /etc/init.d/.... links or run the following from inside the vserver:<br />
chkconfig -d -f boot.swap boot.isapnp boot.idedma boot.loadmodules \<br />
boot.device-mapper boot.md boot.proc boot.shm boot.sched \<br />
boot.rootfsck hotplug boot.localfs boot.crypto boot.clock \<br />
boot.scpm boot.ipconfig<br />
<br />
chkconfig -d -f coldplug irq_balancer random network fbset powersaved kbd hwscan<br />
* remove unneeded packages:<br />
rpm -e irqbalance kernel-smp grub reiserfs xfsprogs raidtools ntfsprogs \<br />
module-init-tools mkinitrd powersave hotplug mdadm<br />
'''Note:''' there are a number of redundant packages remaining that can not be removed due to yast2 depending on them.<br />
<br />
===initscripts===<br />
SuSE's /etc/init.d/rc expects two enviromnet variables: RUNLEVEL and PREVLEVEL. the vserver.start scripts failes to set those. We've got workarrounds:<br />
a) edit /etc/init.d/rc to set those values (not recomended)<br />
b) apply the following patch to vserver.start to set the values:<br />
--- vserver.start.orig 2006-03-02 10:37:49.000000000 +0000<br />
+++ vserver.start 2006-03-02 10:10:36.000000000 +0000<br />
@@ -135,7 +134,7 @@<br />
$_VUNAME --xid self --set -t context="$VSERVER_DIR" -- \<br />
$_VATTRIBUTE --set "${OPTS_VATTRIBUTE[@]}" -- \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_VCONTEXT --migrate-self --endsetup --chroot $SILENT_OPT \<br />
"${OPTS_VCONTEXT_MIGRATE[@]}" "${OPTS_VCONTEXT_ENTER[@]}" -- \<br />
"${INITCMD_START[@]}"<br />
@@ -151,7 +150,7 @@<br />
$_EXEC_ULIMIT "$VSERVER_DIR/ulimits" \<br />
$_CHCONTEXT_COMPAT "${CHCONTEXT_OPTS[@]}" "${CHCONTEXT_INIT_OPTS[@]}" \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_CHAINECHO "${_IS_FAKEINIT:+$startsync_pipe}" "" \<br />
$_CAPCHROOT "${CAPCHROOT_OPTS[@]}" . \<br />
"${INITCMD_START[@]}"<br />
'''edit me:''' do we need to modify the vserver.stop script as well?</div>Mstroberthttp://www.linux-vserver.org/Installing_an_openSUSE_vserver_guestInstalling an openSUSE vserver guest2007-06-07T23:13:25Z<p>Mstrobert: /* post install cleanup */ case</p>
<hr />
<div>Installing and running openSUSE as a vserver guest.<br />
__TOC__<br />
==Test configuration==<br />
Host:<br />
* Debian Etch AMD64, Kernel 2.6.15.4-vs2.0.2-rc9, util-vserver 0.30.210 + patch (see below), or<br />
* Debian Etch AMD64, 2.6.18-4-vserver-amd64, util-vserver 0.30.212-1 (+patch)<br />
Guest:<br />
* SLES 9, or<br />
* openSUSE 10.2<br />
<br />
==Running openSUSE vservers on a Debian server==<br />
===Installation===<br />
Debian is lacking the required rpm tools to install an openSUSE or SLES system directly via vserver build (the required apt-rpm is available in source only for apt-0.5.xx, and Debian is already at 0.6.xx).<br />
<br />
Therefore, use the normal openSUSE installation procedure and then copy the system to a vserver directory:<br />
* Install openSUSE on raw metal or in a virtual machine (such as [http://www.virtualbox.org/ VirtualBox]).<br />
* Boot from CD (openSUSE or Debian - whatever you prefer), or just boot into the OS and log in as root.<br />
* tar the whole system, copy it to the vserver host and untar it to the desired vserver location, usually <code>/var/lib/vservers/<servername></code><br />
* Create <code>/etc/vservers/<servername></code> manually, or copy it from another vserver.<br />
<br />
===Post install cleanup===<br />
* remove some startup service, either delete the /etc/init.d/.... links or run the following from inside the vserver:<br />
chkconfig -d -f boot.swap boot.isapnp boot.idedma boot.loadmodules \<br />
boot.device-mapper boot.md boot.proc boot.shm boot.sched \<br />
boot.rootfsck hotplug boot.localfs boot.crypto boot.clock \<br />
boot.scpm boot.ipconfig<br />
<br />
chkconfig -d -f coldplug irq_balancer random network fbset powersaved kbd hwscan<br />
* remove unneeded packages:<br />
rpm -e irqbalance kernel-smp grub reiserfs xfsprogs raidtools ntfsprogs \<br />
module-init-tools mkinitrd powersave hotplug mdadm<br />
'''Note:''' there are a number of redundant packages remaining that can not be removed due to yast2 depending on them.<br />
<br />
===initscripts===<br />
SuSE's /etc/init.d/rc expects two enviromnet variables: RUNLEVEL and PREVLEVEL. the vserver.start scripts failes to set those. We've got workarrounds:<br />
a) edit /etc/init.d/rc to set those values (not recomended)<br />
b) apply the following patch to vserver.start to set the values:<br />
--- vserver.start.orig 2006-03-02 10:37:49.000000000 +0000<br />
+++ vserver.start 2006-03-02 10:10:36.000000000 +0000<br />
@@ -135,7 +134,7 @@<br />
$_VUNAME --xid self --set -t context="$VSERVER_DIR" -- \<br />
$_VATTRIBUTE --set "${OPTS_VATTRIBUTE[@]}" -- \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_VCONTEXT --migrate-self --endsetup --chroot $SILENT_OPT \<br />
"${OPTS_VCONTEXT_MIGRATE[@]}" "${OPTS_VCONTEXT_ENTER[@]}" -- \<br />
"${INITCMD_START[@]}"<br />
@@ -151,7 +150,7 @@<br />
$_EXEC_ULIMIT "$VSERVER_DIR/ulimits" \<br />
$_CHCONTEXT_COMPAT "${CHCONTEXT_OPTS[@]}" "${CHCONTEXT_INIT_OPTS[@]}" \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_CHAINECHO "${_IS_FAKEINIT:+$startsync_pipe}" "" \<br />
$_CAPCHROOT "${CAPCHROOT_OPTS[@]}" . \<br />
"${INITCMD_START[@]}"<br />
'''edit me:''' do we need to modify the vserver.stop script as well?</div>Mstroberthttp://www.linux-vserver.org/Installing_an_openSUSE_vserver_guestInstalling an openSUSE vserver guest2007-06-07T23:12:51Z<p>Mstrobert: /* Installation */ typos</p>
<hr />
<div>Installing and running openSUSE as a vserver guest.<br />
__TOC__<br />
==Test configuration==<br />
Host:<br />
* Debian Etch AMD64, Kernel 2.6.15.4-vs2.0.2-rc9, util-vserver 0.30.210 + patch (see below), or<br />
* Debian Etch AMD64, 2.6.18-4-vserver-amd64, util-vserver 0.30.212-1 (+patch)<br />
Guest:<br />
* SLES 9, or<br />
* openSUSE 10.2<br />
<br />
==Running openSUSE vservers on a Debian server==<br />
===Installation===<br />
Debian is lacking the required rpm tools to install an openSUSE or SLES system directly via vserver build (the required apt-rpm is available in source only for apt-0.5.xx, and Debian is already at 0.6.xx).<br />
<br />
Therefore, use the normal openSUSE installation procedure and then copy the system to a vserver directory:<br />
* Install openSUSE on raw metal or in a virtual machine (such as [http://www.virtualbox.org/ VirtualBox]).<br />
* Boot from CD (openSUSE or Debian - whatever you prefer), or just boot into the OS and log in as root.<br />
* tar the whole system, copy it to the vserver host and untar it to the desired vserver location, usually <code>/var/lib/vservers/<servername></code><br />
* Create <code>/etc/vservers/<servername></code> manually, or copy it from another vserver.<br />
<br />
===post install cleanup===<br />
* remove some startup service, either delete the /etc/init.d/.... links or run the following from inside the vserver:<br />
chkconfig -d -f boot.swap boot.isapnp boot.idedma boot.loadmodules \<br />
boot.device-mapper boot.md boot.proc boot.shm boot.sched \<br />
boot.rootfsck hotplug boot.localfs boot.crypto boot.clock \<br />
boot.scpm boot.ipconfig<br />
<br />
chkconfig -d -f coldplug irq_balancer random network fbset powersaved kbd hwscan<br />
* remove unneeded packages:<br />
rpm -e irqbalance kernel-smp grub reiserfs xfsprogs raidtools ntfsprogs \<br />
module-init-tools mkinitrd powersave hotplug mdadm<br />
'''Note:''' there are a number of redundant packages remaining that can not be removed due to yast2 depending on them.<br />
===initscripts===<br />
SuSE's /etc/init.d/rc expects two enviromnet variables: RUNLEVEL and PREVLEVEL. the vserver.start scripts failes to set those. We've got workarrounds:<br />
a) edit /etc/init.d/rc to set those values (not recomended)<br />
b) apply the following patch to vserver.start to set the values:<br />
--- vserver.start.orig 2006-03-02 10:37:49.000000000 +0000<br />
+++ vserver.start 2006-03-02 10:10:36.000000000 +0000<br />
@@ -135,7 +134,7 @@<br />
$_VUNAME --xid self --set -t context="$VSERVER_DIR" -- \<br />
$_VATTRIBUTE --set "${OPTS_VATTRIBUTE[@]}" -- \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_VCONTEXT --migrate-self --endsetup --chroot $SILENT_OPT \<br />
"${OPTS_VCONTEXT_MIGRATE[@]}" "${OPTS_VCONTEXT_ENTER[@]}" -- \<br />
"${INITCMD_START[@]}"<br />
@@ -151,7 +150,7 @@<br />
$_EXEC_ULIMIT "$VSERVER_DIR/ulimits" \<br />
$_CHCONTEXT_COMPAT "${CHCONTEXT_OPTS[@]}" "${CHCONTEXT_INIT_OPTS[@]}" \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_CHAINECHO "${_IS_FAKEINIT:+$startsync_pipe}" "" \<br />
$_CAPCHROOT "${CAPCHROOT_OPTS[@]}" . \<br />
"${INITCMD_START[@]}"<br />
'''edit me:''' do we need to modify the vserver.stop script as well?</div>Mstroberthttp://www.linux-vserver.org/Installing_an_openSUSE_vserver_guestInstalling an openSUSE vserver guest2007-06-07T23:08:20Z<p>Mstrobert: /* Installation */ distro naming</p>
<hr />
<div>Installing and running openSUSE as a vserver guest.<br />
__TOC__<br />
==Test configuration==<br />
Host:<br />
* Debian Etch AMD64, Kernel 2.6.15.4-vs2.0.2-rc9, util-vserver 0.30.210 + patch (see below), or<br />
* Debian Etch AMD64, 2.6.18-4-vserver-amd64, util-vserver 0.30.212-1 (+patch)<br />
Guest:<br />
* SLES 9, or<br />
* openSUSE 10.2<br />
<br />
==Running openSUSE vservers on a Debian server==<br />
===Installation===<br />
Debian is lacking the required rpm tools to install an openSUSE or SLES system directly via vserver build (the required apt-rpm is available in source only for apt-0.5.xx, and Debian is already at 0.6.xx).<br />
<br />
Therefore, use the normal openSUSE installation procedure and then copy the system to a vserver directory:<br />
* Install openSUSE on raw metal or in a virtual machine (such as [http://www.virtualbox.org/ VirtualBox]).<br />
* Boot from CD (openSUSE or Debian - whatever you prefer), or just boot into the OS and log in as root.<br />
* tar the whole system, copy it to the vserver host and untar it to the desired vserver location, usually <code>/var/lib/vservers/<servername></code><br />
* Create <code>/etc/vservers/<servername></code> manual (or copy from other vserver)<br />
<br />
===post install cleanup===<br />
* remove some startup service, either delete the /etc/init.d/.... links or run the following from inside the vserver:<br />
chkconfig -d -f boot.swap boot.isapnp boot.idedma boot.loadmodules \<br />
boot.device-mapper boot.md boot.proc boot.shm boot.sched \<br />
boot.rootfsck hotplug boot.localfs boot.crypto boot.clock \<br />
boot.scpm boot.ipconfig<br />
<br />
chkconfig -d -f coldplug irq_balancer random network fbset powersaved kbd hwscan<br />
* remove unneeded packages:<br />
rpm -e irqbalance kernel-smp grub reiserfs xfsprogs raidtools ntfsprogs \<br />
module-init-tools mkinitrd powersave hotplug mdadm<br />
'''Note:''' there are a number of redundant packages remaining that can not be removed due to yast2 depending on them.<br />
===initscripts===<br />
SuSE's /etc/init.d/rc expects two enviromnet variables: RUNLEVEL and PREVLEVEL. the vserver.start scripts failes to set those. We've got workarrounds:<br />
a) edit /etc/init.d/rc to set those values (not recomended)<br />
b) apply the following patch to vserver.start to set the values:<br />
--- vserver.start.orig 2006-03-02 10:37:49.000000000 +0000<br />
+++ vserver.start 2006-03-02 10:10:36.000000000 +0000<br />
@@ -135,7 +134,7 @@<br />
$_VUNAME --xid self --set -t context="$VSERVER_DIR" -- \<br />
$_VATTRIBUTE --set "${OPTS_VATTRIBUTE[@]}" -- \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_VCONTEXT --migrate-self --endsetup --chroot $SILENT_OPT \<br />
"${OPTS_VCONTEXT_MIGRATE[@]}" "${OPTS_VCONTEXT_ENTER[@]}" -- \<br />
"${INITCMD_START[@]}"<br />
@@ -151,7 +150,7 @@<br />
$_EXEC_ULIMIT "$VSERVER_DIR/ulimits" \<br />
$_CHCONTEXT_COMPAT "${CHCONTEXT_OPTS[@]}" "${CHCONTEXT_INIT_OPTS[@]}" \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_CHAINECHO "${_IS_FAKEINIT:+$startsync_pipe}" "" \<br />
$_CAPCHROOT "${CAPCHROOT_OPTS[@]}" . \<br />
"${INITCMD_START[@]}"<br />
'''edit me:''' do we need to modify the vserver.stop script as well?</div>Mstroberthttp://www.linux-vserver.org/Installing_an_openSUSE_vserver_guestInstalling an openSUSE vserver guest2007-06-07T23:06:34Z<p>Mstrobert: /* Running SuSE vservers on a Debian server */ distro naming</p>
<hr />
<div>Installing and running openSUSE as a vserver guest.<br />
__TOC__<br />
==Test configuration==<br />
Host:<br />
* Debian Etch AMD64, Kernel 2.6.15.4-vs2.0.2-rc9, util-vserver 0.30.210 + patch (see below), or<br />
* Debian Etch AMD64, 2.6.18-4-vserver-amd64, util-vserver 0.30.212-1 (+patch)<br />
Guest:<br />
* SLES 9, or<br />
* openSUSE 10.2<br />
<br />
==Running openSUSE vservers on a Debian server==<br />
===Installation===<br />
Debian is lacking the required rpm tools to install a SuSE/SLES system directly via vserver build (the required apt-rpm is available in source only for apt-0.5.xx, and Debian is already at 0.6.xx).<br />
<br />
Therefore, use the normal SuSE installation procedure and then copy the system to a vserver directory:<br />
* Install SuSE on raw metal or in a virtual machine (such as [http://www.virtualbox.org/ VirtualBox]).<br />
* Boot from CD (SuSE or Debian whatever you prefer), or just boot into the OS and log in as root.<br />
* tar the whole system, copy it to the vserver host and untar it to the desired vserver location, usually <code>/var/lib/vservers/<servername></code><br />
* Create <code>/etc/vservers/<servername></code> manual (or copy from other vserver)<br />
<br />
===post install cleanup===<br />
* remove some startup service, either delete the /etc/init.d/.... links or run the following from inside the vserver:<br />
chkconfig -d -f boot.swap boot.isapnp boot.idedma boot.loadmodules \<br />
boot.device-mapper boot.md boot.proc boot.shm boot.sched \<br />
boot.rootfsck hotplug boot.localfs boot.crypto boot.clock \<br />
boot.scpm boot.ipconfig<br />
<br />
chkconfig -d -f coldplug irq_balancer random network fbset powersaved kbd hwscan<br />
* remove unneeded packages:<br />
rpm -e irqbalance kernel-smp grub reiserfs xfsprogs raidtools ntfsprogs \<br />
module-init-tools mkinitrd powersave hotplug mdadm<br />
'''Note:''' there are a number of redundant packages remaining that can not be removed due to yast2 depending on them.<br />
===initscripts===<br />
SuSE's /etc/init.d/rc expects two enviromnet variables: RUNLEVEL and PREVLEVEL. the vserver.start scripts failes to set those. We've got workarrounds:<br />
a) edit /etc/init.d/rc to set those values (not recomended)<br />
b) apply the following patch to vserver.start to set the values:<br />
--- vserver.start.orig 2006-03-02 10:37:49.000000000 +0000<br />
+++ vserver.start 2006-03-02 10:10:36.000000000 +0000<br />
@@ -135,7 +134,7 @@<br />
$_VUNAME --xid self --set -t context="$VSERVER_DIR" -- \<br />
$_VATTRIBUTE --set "${OPTS_VATTRIBUTE[@]}" -- \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_VCONTEXT --migrate-self --endsetup --chroot $SILENT_OPT \<br />
"${OPTS_VCONTEXT_MIGRATE[@]}" "${OPTS_VCONTEXT_ENTER[@]}" -- \<br />
"${INITCMD_START[@]}"<br />
@@ -151,7 +150,7 @@<br />
$_EXEC_ULIMIT "$VSERVER_DIR/ulimits" \<br />
$_CHCONTEXT_COMPAT "${CHCONTEXT_OPTS[@]}" "${CHCONTEXT_INIT_OPTS[@]}" \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_CHAINECHO "${_IS_FAKEINIT:+$startsync_pipe}" "" \<br />
$_CAPCHROOT "${CAPCHROOT_OPTS[@]}" . \<br />
"${INITCMD_START[@]}"<br />
'''edit me:''' do we need to modify the vserver.stop script as well?</div>Mstroberthttp://www.linux-vserver.org/Installing_an_openSUSE_vserver_guestInstalling an openSUSE vserver guest2007-06-07T23:01:42Z<p>Mstrobert: +'and running'</p>
<hr />
<div>Installing and running openSUSE as a vserver guest.<br />
__TOC__<br />
==Test configuration==<br />
Host:<br />
* Debian Etch AMD64, Kernel 2.6.15.4-vs2.0.2-rc9, util-vserver 0.30.210 + patch (see below), or<br />
* Debian Etch AMD64, 2.6.18-4-vserver-amd64, util-vserver 0.30.212-1 (+patch)<br />
Guest:<br />
* SLES 9, or<br />
* openSUSE 10.2<br />
<br />
==Running SuSE vservers on a Debian server==<br />
===Installation===<br />
Debian is lacking the required rpm tools to install a SuSE/SLES system directly via vserver build (the required apt-rpm is available in source only for apt-0.5.xx, and Debian is already at 0.6.xx).<br />
<br />
Therefore, use the normal SuSE installation procedure and then copy the system to a vserver directory:<br />
* Install SuSE on raw metal or in a virtual machine (such as [http://www.virtualbox.org/ VirtualBox]).<br />
* Boot from CD (SuSE or Debian whatever you prefer), or just boot into the OS and log in as root.<br />
* tar the whole system, copy it to the vserver host and untar it to the desired vserver location, usually <code>/var/lib/vservers/<servername></code><br />
* Create <code>/etc/vservers/<servername></code> manual (or copy from other vserver)<br />
<br />
===post install cleanup===<br />
* remove some startup service, either delete the /etc/init.d/.... links or run the following from inside the vserver:<br />
chkconfig -d -f boot.swap boot.isapnp boot.idedma boot.loadmodules \<br />
boot.device-mapper boot.md boot.proc boot.shm boot.sched \<br />
boot.rootfsck hotplug boot.localfs boot.crypto boot.clock \<br />
boot.scpm boot.ipconfig<br />
<br />
chkconfig -d -f coldplug irq_balancer random network fbset powersaved kbd hwscan<br />
* remove unneeded packages:<br />
rpm -e irqbalance kernel-smp grub reiserfs xfsprogs raidtools ntfsprogs \<br />
module-init-tools mkinitrd powersave hotplug mdadm<br />
'''Note:''' there are a number of redundant packages remaining that can not be removed due to yast2 depending on them.<br />
===initscripts===<br />
SuSE's /etc/init.d/rc expects two enviromnet variables: RUNLEVEL and PREVLEVEL. the vserver.start scripts failes to set those. We've got workarrounds:<br />
a) edit /etc/init.d/rc to set those values (not recomended)<br />
b) apply the following patch to vserver.start to set the values:<br />
--- vserver.start.orig 2006-03-02 10:37:49.000000000 +0000<br />
+++ vserver.start 2006-03-02 10:10:36.000000000 +0000<br />
@@ -135,7 +134,7 @@<br />
$_VUNAME --xid self --set -t context="$VSERVER_DIR" -- \<br />
$_VATTRIBUTE --set "${OPTS_VATTRIBUTE[@]}" -- \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_VCONTEXT --migrate-self --endsetup --chroot $SILENT_OPT \<br />
"${OPTS_VCONTEXT_MIGRATE[@]}" "${OPTS_VCONTEXT_ENTER[@]}" -- \<br />
"${INITCMD_START[@]}"<br />
@@ -151,7 +150,7 @@<br />
$_EXEC_ULIMIT "$VSERVER_DIR/ulimits" \<br />
$_CHCONTEXT_COMPAT "${CHCONTEXT_OPTS[@]}" "${CHCONTEXT_INIT_OPTS[@]}" \<br />
$_SAVE_CTXINFO "$VSERVER_DIR" \<br />
- $_ENV -i -- \<br />
+ $_ENV -i -- PREVLEVEL="N" RUNLEVEL="$RUNLEVEL_START" \<br />
$_CHAINECHO "${_IS_FAKEINIT:+$startsync_pipe}" "" \<br />
$_CAPCHROOT "${CAPCHROOT_OPTS[@]}" . \<br />
"${INITCMD_START[@]}"<br />
'''edit me:''' do we need to modify the vserver.stop script as well?</div>Mstrobert