From: Christian Mayrhuber (christian.mayrhuber_at_osiris.at)
Date: Thu 21 Aug 2003 - 07:57:52 BST
You need vserver-0.23 for a ctx-17a kernel.
vserver-0.22 only works with kernels up to ctx-17.
Unstable debian vserver-0.23 packages are available from:
"Martin List-Petersen" <martin_at_list-petersen.dk>
See his mail:
>Until Ola releases new packages to Debian and for the ones, that wont
>wait, i've prepared a Debian package with the 0.23 tools.
>
>They can be found at:
>ftp://debian.marlow.dk/dists/unstable/custom/pool/vserver/vserver_0.23-2_i3
86.deb
>
>A few notes to these packages:
>- The config option VSERVERS_ROOT in /etc/vserver.conf was moved to
>/etc/vservers.conf (which also holds the BACKGROUND option).
>If you changed your path from /var/lib/vservers to somewhere else,
>please correct that after install.
>
>- Please remove the /etc/vserver.conf file to avoid confusion. The
>package will not do that for you
>
>- I applied Klavs Klavsens patch for running Gentoo in vservsers. This
>gives you two new options in the individual vservers config files:
>S_START= and S_STOP. For more info check README.Debian or
>http://bugs.gentoo.org/show_bug.cgi?id=19230
>
>Please consider this package unstable. It is working for me, but still
>needs tweaking and was more or less a quick hack, because i'm allready
>running ctx17a.
>
>Regards,
>Martin List-Petersen
>martin at list-petersen dot dk
>--
>If food be the music of love, eat up, eat up.
-- Chris----- Original Message ----- From: "David MacKinnon" <davidm_at_obsidian.com.au> To: <vserver_at_solucorp.qc.ca> Sent: Thursday, August 21, 2003 4:13 AM Subject: [vserver] Weirdness..
> I''m running Linux version 2.4.21-c17a under Debian, using the vserver > 0.22 tools. Things were running fine, but now, a vserver is bound to > anything other than 0.0.0.0 it can't seem to send anything other than > icmp packets (can ping, nothing else), get "invalid argument" errors > when I try and connect to anything. > > Likewise, vservers that are bound to 0.0.0.0 can only bind to 0.0.0.0, > not specific IP's, and within the vservers an ifconfig shows all primary > interfaces (no aliases) but no IP's. Needless to say this is a bit of a > problem. I've been pulling my hair our over this for a while, tried > setting up a fresh vserver, but it had the same problem. Anyone have > any ideas or seen anything like this before? > > -David > > >