Starting a vserver (with "gentoo" init style) fails under sys-cluster/util-vserver-0.30.213. The problem can be solved by changing the INITCMD_START at line 306 within /usr/lib/util-vserver/vserver.functions from: INITCMD_START=( /lib/rcscripts/sh/init-vserver.sh "$RUNLEVEL_START" to: INITCMD_START=( /sbin/rc "$RUNLEVEL_START" ) Reproducible: Always Steps to Reproduce: 1. echo "gentoo" > /etc/vservers/[vserver name]/apps/init/style 2. vserver [vserver name] start Actual Results: vcontext: execvp("/lib/rcscripts/sh/init-vserver.sh"): No such file or directory An error occured while executing the vserver startup sequence; when there are no other messages, it is very likely that the init-script (/lib/rcscripts/sh/init-vserver.sh default) failed. Common causes are: * /etc/rc.d/rc on Fedora Core 1 and RH9 fails always; the 'apt-rpm' build method knows how to deal with this, but on existing installations, appending 'true' to this file will help. Failed to start vserver '[vserver name]' Expected Results: a running vserver ;) This happens together with sys-apps/baselayout-1.13.0_alpha12
you did not setup your guest with "vserver ... build ... -- -d gentoo" which would have installed int-vserver.sh, a simple /sbin/rc won't work... in case of an upgrade copy init-vserver.sh from /usr/lib/util-vserver/distribution/gentoo from the host... and btw, please use baselayout-2, it contains a lot of fixes and will be the next stable...
(In reply to comment #1) > you did not setup your guest with "vserver ... build ... -- -d gentoo" which > would have installed int-vserver.sh, a simple /sbin/rc won't work... in case of > an upgrade copy init-vserver.sh from /usr/lib/util-vserver/distribution/gentoo > from the host... Thanks! > and btw, please use baselayout-2, it contains a lot of fixes and will be the > next stable... I installed the latest baselayout-2 and filed some bugreports at http://bugs.gentoo.org/show_bug.cgi?id=186521#c5
