Linux-VServer - User contributions [en]

Upstart issues

2010-01-07T04:44:14Z

X: /* fake low level events inside the guest */

== running an upstart based guest ==

currently upstart based guests need some manual tweaking to make them work inside a vserver guest.

=== prepare the host ===
First of all you need to set the init style of your vserver to plain
# echo plain > /etc/vservers/<vservername>/apps/init/style

I'd also strongly recommend to mount <code>/var/run</code> and <code>/var/lock</code> of the guest as tmpfs. So add the following lines to
<code>/etc/vservers/<vservername>/fstab</code>
none /var/run tmpfs size=16m,nosuid,mode=0755 0 0
none /var/lock tmpfs size=16m,noexec,nosuid,nodev 0 0

=== remove low level services inside the guest ===
Then you need to get rid of anything in <code>/etc/init/</code> that tries to fiddle with your Server's Hardware or other low-level Stuff that's already handled by your host's kernel/system. Having one such scriptlet still enabled might cause the whole upstart system to fail (like not beeing able to open <code>/dev/console</code> or failing to start the udev system).
Just remove these scriptlets, move them out of the way or rename them to something not ending in <code>.conf</code>. Be aware that upstart also parses subfolders of <code>/etc/init/</code> for <code>.conf</code> files.

This is what I deleted on a basic Ubuntu 9.10 guest:
dmesg.conf
hostname.conf
hwclock-save.conf
hwclock.conf
mountall-net.conf
mountall-reboot.conf
mountall-shell.conf
mountall.conf
network-interface.conf
networking.conf
procps.conf
rsyslog-kmsg.conf
tty1.conf
tty2.conf
tty3.conf
tty4.conf
tty5.conf
tty6.conf
upstart-udev-bridge.conf

=== fake low level events inside the guest ===
Finally you need to fake emit the events that some of these scripts would do during regular boot. Probably the cleanest approach is to add a scriptlet <code>vserver.conf</code> to <code>/etc/init/</code> with this content:
start on startup
script
touch /var/run/utmp
chown root:utmp /var/run/utmp
chmod 664 /var/run/utmp
initctl emit virtual-filesystems
initctl emit local-filesystems
initctl emit remote-filesystems
initctl emit filesystem
end script

The utmp stuff is needed if you mount <code>/var/run</code> as tmpfs and you don't create utmp anywhere else.

=== adapt /etc/init/rc-sysinit.conf inside the guest ===

This depends on net-device-up IFACE=lo, remove this from the start line so that it reads:<br/>
<code>start on filesystem</code>

This scriptlet tries to parse <code>/proc/cmdline</code> which will not work and probably isn't needed inside a vserver.<br/>
Simply comment out or delete the whole <code>for ARG in $(cat /proc/cmdline) do...done</code> loop.

=== Notes for older kernels ===
If you encounter upstart errors like this:

$ vserver foo start
init: missing runlevel
Try `init --help' for more information.

or

$ vserver foo start
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused

then you're probably running the current stable version <code>2.6.22.19-vs2.2.0.7</code>.

Upstart's <code>/sbin/init</code> implementation requires to be PID 1. It is linked against NPTL (in contrast to sysvinit), which has a bug in it's caching <code>getpid(2)</code> wrapper. With this kernel version <code>getpid(2)</code> returns the cached PID to init, resulting in init replacing itself with telinit. You can fix this by upgrading to a <code>2.6.26+</code> kernel and a newer vserver patch, or by patching upstart:

diff --git a/init/main.c b/init/main.c
index bfcd528..c6c9304 100644
--- a/init/main.c
+++ b/init/main.c
@@ -37,6 +37,7 @@
#include <string.h>
#include <syslog.h>
#include <unistd.h>
+#include <syscall.h>

#include <linux/kd.h>

@@ -131,7 +132,7 @@ main (int argc,
}

/* Check we're process #1 */
- if (getpid () > 1) {
+ if (syscall(SYS_getpid) > 1) {
execv (TELINIT, argv);
/* Ignore failure, probably just that telinit doesn't exist */

For more information see the man pages of <code>getpid(2)</code> (NOTES) and <code>clone(2)</code> (BUGS).

Upstart issues

2010-01-07T04:40:59Z

X: /* prepare the host */

== running an upstart based guest ==

currently upstart based guests need some manual tweaking to make them work inside a vserver guest.

=== prepare the host ===
First of all you need to set the init style of your vserver to plain
# echo plain > /etc/vservers/<vservername>/apps/init/style

I'd also strongly recommend to mount <code>/var/run</code> and <code>/var/lock</code> of the guest as tmpfs. So add the following lines to
<code>/etc/vservers/<vservername>/fstab</code>
none /var/run tmpfs size=16m,nosuid,mode=0755 0 0
none /var/lock tmpfs size=16m,noexec,nosuid,nodev 0 0

=== remove low level services inside the guest ===
Then you need to get rid of anything in <code>/etc/init/</code> that tries to fiddle with your Server's Hardware or other low-level Stuff that's already handled by your host's kernel/system. Having one such scriptlet still enabled might cause the whole upstart system to fail (like not beeing able to open <code>/dev/console</code> or failing to start the udev system).
Just remove these scriptlets, move them out of the way or rename them to something not ending in <code>.conf</code>. Be aware that upstart also parses subfolders of <code>/etc/init/</code> for <code>.conf</code> files.

This is what I deleted on a basic Ubuntu 9.10 guest:
dmesg.conf
hostname.conf
hwclock-save.conf
hwclock.conf
mountall-net.conf
mountall-reboot.conf
mountall-shell.conf
mountall.conf
network-interface.conf
networking.conf
procps.conf
rsyslog-kmsg.conf
tty1.conf
tty2.conf
tty3.conf
tty4.conf
tty5.conf
tty6.conf
upstart-udev-bridge.conf

=== fake low level events inside the guest ===
Finally you need to fake emit the events that some of these scripts would do during regular boot. Probably the cleanest approach is to add a scriptlet <code>vserver.conf</code> to <code>/etc/init/</code> with this content:
start on startup
script
initctl emit virtual-filesystems
initctl emit local-filesystems
initctl emit remote-filesystems
initctl emit filesystem
end script

=== adapt /etc/init/rc-sysinit.conf inside the guest ===

This depends on net-device-up IFACE=lo, remove this from the start line so that it reads:<br/>
<code>start on filesystem</code>

This scriptlet tries to parse <code>/proc/cmdline</code> which will not work and probably isn't needed inside a vserver.<br/>
Simply comment out or delete the whole <code>for ARG in $(cat /proc/cmdline) do...done</code> loop.

=== Notes for older kernels ===
If you encounter upstart errors like this:

$ vserver foo start
init: missing runlevel
Try `init --help' for more information.

or

$ vserver foo start
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused

then you're probably running the current stable version <code>2.6.22.19-vs2.2.0.7</code>.

Upstart's <code>/sbin/init</code> implementation requires to be PID 1. It is linked against NPTL (in contrast to sysvinit), which has a bug in it's caching <code>getpid(2)</code> wrapper. With this kernel version <code>getpid(2)</code> returns the cached PID to init, resulting in init replacing itself with telinit. You can fix this by upgrading to a <code>2.6.26+</code> kernel and a newer vserver patch, or by patching upstart:

diff --git a/init/main.c b/init/main.c
index bfcd528..c6c9304 100644
--- a/init/main.c
+++ b/init/main.c
@@ -37,6 +37,7 @@
#include <string.h>
#include <syslog.h>
#include <unistd.h>
+#include <syscall.h>

#include <linux/kd.h>

@@ -131,7 +132,7 @@ main (int argc,
}

/* Check we're process #1 */
- if (getpid () > 1) {
+ if (syscall(SYS_getpid) > 1) {
execv (TELINIT, argv);
/* Ignore failure, probably just that telinit doesn't exist */

For more information see the man pages of <code>getpid(2)</code> (NOTES) and <code>clone(2)</code> (BUGS).

Upstart issues

2010-01-07T03:09:58Z

X: /* adapt /etc/init/rc-sysinit.conf inside the guest */

== running an upstart based guest ==

currently upstart based guests need some manual tweaking to make them work inside a vserver guest.

=== prepare the host ===
First of all you need to set the init style of your vserver to plain
# echo plain > /etc/vservers/<vservername>/apps/init/style

=== remove low level services inside the guest ===
Then you need to get rid of anything in <code>/etc/init/</code> that tries to fiddle with your Server's Hardware or other low-level Stuff that's already handled by your host's kernel/system. Having one such scriptlet still enabled might cause the whole upstart system to fail (like not beeing able to open <code>/dev/console</code> or failing to start the udev system).
Just remove these scriptlets, move them out of the way or rename them to something not ending in <code>.conf</code>. Be aware that upstart also parses subfolders of <code>/etc/init/</code> for <code>.conf</code> files.

This is what I deleted on a basic Ubuntu 9.10 guest:
dmesg.conf
hostname.conf
hwclock-save.conf
hwclock.conf
mountall-net.conf
mountall-reboot.conf
mountall-shell.conf
mountall.conf
network-interface.conf
networking.conf
procps.conf
rsyslog-kmsg.conf
tty1.conf
tty2.conf
tty3.conf
tty4.conf
tty5.conf
tty6.conf
upstart-udev-bridge.conf

=== fake low level events inside the guest ===
Finally you need to fake emit the events that some of these scripts would do during regular boot. Probably the cleanest approach is to add a scriptlet <code>vserver.conf</code> to <code>/etc/init/</code> with this content:
start on startup
script
initctl emit virtual-filesystems
initctl emit local-filesystems
initctl emit remote-filesystems
initctl emit filesystem
end script

=== adapt /etc/init/rc-sysinit.conf inside the guest ===

This depends on net-device-up IFACE=lo, remove this from the start line so that it reads:<br/>
<code>start on filesystem</code>

This scriptlet tries to parse <code>/proc/cmdline</code> which will not work and probably isn't needed inside a vserver.<br/>
Simply comment out or delete the whole <code>for ARG in $(cat /proc/cmdline) do...done</code> loop.

=== Notes for older kernels ===
If you encounter upstart errors like this:

$ vserver foo start
init: missing runlevel
Try `init --help' for more information.

or

$ vserver foo start
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused

then you're probably running the current stable version <code>2.6.22.19-vs2.2.0.7</code>.

Upstart's <code>/sbin/init</code> implementation requires to be PID 1. It is linked against NPTL (in contrast to sysvinit), which has a bug in it's caching <code>getpid(2)</code> wrapper. With this kernel version <code>getpid(2)</code> returns the cached PID to init, resulting in init replacing itself with telinit. You can fix this by upgrading to a <code>2.6.26+</code> kernel and a newer vserver patch, or by patching upstart:

diff --git a/init/main.c b/init/main.c
index bfcd528..c6c9304 100644
--- a/init/main.c
+++ b/init/main.c
@@ -37,6 +37,7 @@
#include <string.h>
#include <syslog.h>
#include <unistd.h>
+#include <syscall.h>

#include <linux/kd.h>

@@ -131,7 +132,7 @@ main (int argc,
}

/* Check we're process #1 */
- if (getpid () > 1) {
+ if (syscall(SYS_getpid) > 1) {
execv (TELINIT, argv);
/* Ignore failure, probably just that telinit doesn't exist */

For more information see the man pages of <code>getpid(2)</code> (NOTES) and <code>clone(2)</code> (BUGS).

Upstart issues

2010-01-07T02:57:07Z

X: new rc-sysinit.conf section

== running an upstart based guest ==

currently upstart based guests need some manual tweaking to make them work inside a vserver guest.

=== prepare the host ===
First of all you need to set the init style of your vserver to plain
# echo plain > /etc/vservers/<vservername>/apps/init/style

=== remove low level services inside the guest ===
Then you need to get rid of anything in <code>/etc/init/</code> that tries to fiddle with your Server's Hardware or other low-level Stuff that's already handled by your host's kernel/system. Having one such scriptlet still enabled might cause the whole upstart system to fail (like not beeing able to open <code>/dev/console</code> or failing to start the udev system).
Just remove these scriptlets, move them out of the way or rename them to something not ending in <code>.conf</code>. Be aware that upstart also parses subfolders of <code>/etc/init/</code> for <code>.conf</code> files.

This is what I deleted on a basic Ubuntu 9.10 guest:
dmesg.conf
hostname.conf
hwclock-save.conf
hwclock.conf
mountall-net.conf
mountall-reboot.conf
mountall-shell.conf
mountall.conf
network-interface.conf
networking.conf
procps.conf
rsyslog-kmsg.conf
tty1.conf
tty2.conf
tty3.conf
tty4.conf
tty5.conf
tty6.conf
upstart-udev-bridge.conf

=== fake low level events inside the guest ===
Finally you need to fake emit the events that some of these scripts would do during regular boot. Probably the cleanest approach is to add a scriptlet <code>vserver.conf</code> to <code>/etc/init/</code> with this content:
start on startup
script
initctl emit virtual-filesystems
initctl emit local-filesystems
initctl emit remote-filesystems
initctl emit filesystem
end script

=== adapt /etc/init/rc-sysinit.conf inside the guest ===
This scriptlet tries to parse <code>/proc/cmdline</code> which will not work and probably isn't needed inside a vserver.

Simply comment out or delete the whole <code>for ARG in $(cat /proc/cmdline) do...done</code> loop.

=== Notes for older kernels ===
If you encounter upstart errors like this:

$ vserver foo start
init: missing runlevel
Try `init --help' for more information.

or

$ vserver foo start
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused

then you're probably running the current stable version <code>2.6.22.19-vs2.2.0.7</code>.

Upstart's <code>/sbin/init</code> implementation requires to be PID 1. It is linked against NPTL (in contrast to sysvinit), which has a bug in it's caching <code>getpid(2)</code> wrapper. With this kernel version <code>getpid(2)</code> returns the cached PID to init, resulting in init replacing itself with telinit. You can fix this by upgrading to a <code>2.6.26+</code> kernel and a newer vserver patch, or by patching upstart:

diff --git a/init/main.c b/init/main.c
index bfcd528..c6c9304 100644
--- a/init/main.c
+++ b/init/main.c
@@ -37,6 +37,7 @@
#include <string.h>
#include <syslog.h>
#include <unistd.h>
+#include <syscall.h>

#include <linux/kd.h>

@@ -131,7 +132,7 @@ main (int argc,
}

/* Check we're process #1 */
- if (getpid () > 1) {
+ if (syscall(SYS_getpid) > 1) {
execv (TELINIT, argv);
/* Ignore failure, probably just that telinit doesn't exist */

For more information see the man pages of <code>getpid(2)</code> (NOTES) and <code>clone(2)</code> (BUGS).

Documentation

2009-11-09T20:14:09Z

X: /* Guides and Howtos */ removed underscore in Upstart issues Link

<div style="margin: 2em auto 2em auto; padding: 10px; background-color: #F9ECCD; border: 1px solid #004433; text-align: center;">
[[Image:Icon-Caution.png|left]]
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.

'''To ease migration we created a [[List of old Documentation pages]].'''
</div>

== Introduction ==

* [[Overview|Virtualization Overview]]
* [[Usage Scenarios]]
* [[Feature Matrix]]

== Installation ==

* [[Installation Considerations]]
* [[Installation on Linux 2.6]]: from source, both the kernel and util-vserver
* [[Installation on ArchLinux]]
* [[Installation on CentOS]]
* [[Installation on Debian]]
* [[Installation on Fedora]]
* [[Installation on Gentoo]]
* [[Installation on Mandrake]]
* [http://pld-linux.org/Vserver Installation on PLD-Linux]
* [[Installation on Redhat]]
* [[Installation on Slackware]]
* [[Installation on SuSE/OpenSUSE]]
* [[Installation on Ubuntu]]

== Configuration ==

* [[Util-vserver:Documentation|util-vserver Documentation]]
* [[vcd:Documentation|VServer Control Daemon Documentation]]
* [[Share a directory among multiple guests]]

== Guides and Howtos ==

* [[Building Guest Systems]]
* [[util-vserver:Howto virtualize an exisiting Linux server|Howto virtualize an existing Linux server]]
* [[VCMD HowTo]]
* [[Howto make bsd-style init sysv-compatible|Howto make Bsd-style init sysv-compatible (archlinux guest system)]]
* [[Installing 32-bit Fedora on 64-bit Debian]]
* [[Installing Ubuntu on Debian]]
* [[Installing an openSUSE vserver guest]]
* [[Networking vserver guests]]
* [[Howto HostAuth]]
* [[Fuse_GlusterFS| Fuse and GlusterFS]]
* [[yum-patch|How to patch vyum]]
* [[yum-upgrade-3.2.4|Upgrading existing installations to yum-3.2.4]]
* [[Migrating from OpenVZ to Linux-Vserver]]
* [[Getting_high_with_lenny]]
* [[Installing_Ubuntu_8.04_Hardy_as_guest]]
* [[Applying CPU Limits]]
* [[Upgrading from Etch to Lenny]]
* [[Upstart issues]]

== Lists & Theory ==

* Basic configuration
** [[Capabilities and Flags]]
** [[CPU Scheduler]]
** [[Disk Limits and Quota]]
** [[Resource Limits]]
*** [[Memory Limits]]
*** [[Network Bandwidth Management]]
** [[Virtual System Information]]
** [[Unification]]

* Security Considerations
** [[Secure Capabilities]]
** [[Secure chroot Barrier]]
** [[Secure Device Nodes]]
** [[Secure ProcFS Entries]]

* Performance and Stability
** [[Virtualization Overhead]]

* Implementation Details
** [[Context Accounting]]
** [[Filesystem Attributes]]
** [[Filesystem Tagging]]
** [[Filesystem Namespaces]]
** [[Kernel Userspace Helper]]
** [[Mainline Kernel Virtualization]]
** [[ProcFS]]
** [[Syscall Command Switch]]

== External Resources ==

* [http://vserver.13thfloor.at/Remote-Reset/ Simple Remote reset] (remote reset/power your vserver box)
* [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)

Documentation

2009-11-09T20:13:23Z

X: /* Guides and Howtos */ added Link to Upstart Issues

<div style="margin: 2em auto 2em auto; padding: 10px; background-color: #F9ECCD; border: 1px solid #004433; text-align: center;">
[[Image:Icon-Caution.png|left]]
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.

'''To ease migration we created a [[List of old Documentation pages]].'''
</div>

== Introduction ==

* [[Overview|Virtualization Overview]]
* [[Usage Scenarios]]
* [[Feature Matrix]]

== Installation ==

* [[Installation Considerations]]
* [[Installation on Linux 2.6]]: from source, both the kernel and util-vserver
* [[Installation on ArchLinux]]
* [[Installation on CentOS]]
* [[Installation on Debian]]
* [[Installation on Fedora]]
* [[Installation on Gentoo]]
* [[Installation on Mandrake]]
* [http://pld-linux.org/Vserver Installation on PLD-Linux]
* [[Installation on Redhat]]
* [[Installation on Slackware]]
* [[Installation on SuSE/OpenSUSE]]
* [[Installation on Ubuntu]]

== Configuration ==

* [[Util-vserver:Documentation|util-vserver Documentation]]
* [[vcd:Documentation|VServer Control Daemon Documentation]]
* [[Share a directory among multiple guests]]

== Guides and Howtos ==

* [[Building Guest Systems]]
* [[util-vserver:Howto virtualize an exisiting Linux server|Howto virtualize an existing Linux server]]
* [[VCMD HowTo]]
* [[Howto make bsd-style init sysv-compatible|Howto make Bsd-style init sysv-compatible (archlinux guest system)]]
* [[Installing 32-bit Fedora on 64-bit Debian]]
* [[Installing Ubuntu on Debian]]
* [[Installing an openSUSE vserver guest]]
* [[Networking vserver guests]]
* [[Howto HostAuth]]
* [[Fuse_GlusterFS| Fuse and GlusterFS]]
* [[yum-patch|How to patch vyum]]
* [[yum-upgrade-3.2.4|Upgrading existing installations to yum-3.2.4]]
* [[Migrating from OpenVZ to Linux-Vserver]]
* [[Getting_high_with_lenny]]
* [[Installing_Ubuntu_8.04_Hardy_as_guest]]
* [[Applying CPU Limits]]
* [[Upgrading from Etch to Lenny]]
* [[Upstart_issues]]

== Lists & Theory ==

* Basic configuration
** [[Capabilities and Flags]]
** [[CPU Scheduler]]
** [[Disk Limits and Quota]]
** [[Resource Limits]]
*** [[Memory Limits]]
*** [[Network Bandwidth Management]]
** [[Virtual System Information]]
** [[Unification]]

* Security Considerations
** [[Secure Capabilities]]
** [[Secure chroot Barrier]]
** [[Secure Device Nodes]]
** [[Secure ProcFS Entries]]

* Performance and Stability
** [[Virtualization Overhead]]

* Implementation Details
** [[Context Accounting]]
** [[Filesystem Attributes]]
** [[Filesystem Tagging]]
** [[Filesystem Namespaces]]
** [[Kernel Userspace Helper]]
** [[Mainline Kernel Virtualization]]
** [[ProcFS]]
** [[Syscall Command Switch]]

== External Resources ==

* [http://vserver.13thfloor.at/Remote-Reset/ Simple Remote reset] (remote reset/power your vserver box)
* [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)

Upstart issues

2009-11-09T20:10:38Z

X: page created