From: BrandonHoult (BrandonHoult_at_netscape.net)
Date: Mon 19 Aug 2002 - 18:47:49 BST
I am trying to set up vserver with a debian woody host. I patched the
kernel and recompiled without any trouble then converted the rpms 0.19
to deb using alien, and that worked ok Ran "vserver test build" got a
bunch of errors (listed below ran with test2 to capture the errors)
modified the .conf file (also listed below). It seems that I can enter
the vserver without any trouble and it appears to work fine, but if I
start it then ssh or telnet to it I end up in the root directory of the
host server with the name of the computer reported (with telnet) being
the same as the host. I read in the changelog that debian is now
supported, does this mean only as a virtual server, or is it now suposed
to work as a host also?
I have since uninstalled the converted rpm's and compiled from source
but it still has the same problem.
Thanks for any help,
Brandon Hoult
dolt_at_lmistudios.homeip.net
-------------------------------------------------------------
-- Output of vserver test2 build
-------------------------------------------------------------
p300:~# vserver test2 build
/usr/sbin/vserver: cd: etc/rc.d/init.d: No such file or directory
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
No configuration for this vserver: /etc/vservers/test2.conf
Directory /vservers/test2 has been populated
/etc/vservers/test2.conf has been created. Look at it!
----------------------test.conf----------------------------
# Select an unused context (this is optional)
# The default is to allocate a free context on the fly
# In general you don't need to force a context
#S_CONTEXT=
# Select the IP number assigned to the virtual server
# This IP must be one IP of the server, either an interface
# or an IP alias
# A vserver may have more than one IP. Separate them with spaces.
# do not forget double quotes.
# Some examples:
# IPROOT="1.2.3.4 2.3.4.5"
# IPROOT="eth0:1.2.3.4 eth1:2.3.4.5"
# If the device is not specified, IPROOTDEV is used
IPROOT="eth0:192.168.0.55"
# The netmask and broadcast are computed by default from IPROOTDEV
#IPROOTMASK=
#IPROOTBCAST=
# You can define on which device the IP alias will be done
# The IP alias will be set when the server is started and unset
# when the server is stopped
#IPROOTDEV=eth0
# Uncomment the onboot line if you want to enable this
# virtual server at boot time
ONBOOT=yes
# You can set a different host name for the vserver
# If empty, the host name of the main server is used
S_HOSTNAME=test
# You can set a different NIS domain for the vserver
# If empty, the current on is kept
# Set it to "none" to have no NIS domain set
S_DOMAINNAME=
# You can set the priority level (nice) of all process in the vserver
# Even root won't be able to raise it
S_NICE=
# You can set various flags for the new security context
# lock: Prevent the vserver from setting new security context
# sched: Merge scheduler priority of all processes in the vserver
# so that it acts a like a single one.
# nproc: Limit the number of processes in the vserver according to ulimit
# (instead of a per user limit, this becomes a per vserver limit)
# private: No other process can join this security context. Even root
# Do not forget the quotes around the flags
S_FLAGS="lock nproc fakeinit"
# You can set various ulimit flags and they will be inherited by the
# vserver. You enter here various command line argument of ulimit
# ULIMIT="-H -u 200"
# The example above, combined with the nproc S_FLAGS will limit the
# vserver to a maximum of 200 processes
ULIMIT="-H -u 1000"
# You can set various capabilities. By default, the vserver are run
# with a limited set, so you can let root run in a vserver and not
# worry about it. He can't take over the machine. In some cases
# you can to give a little more capabilities (such as CAP_NET_RAW)
S_CAPS="CAP_NET_RAW"
#S_CAPS=""