Eugen Leitl wrote: > On Fri, Sep 12, 2008 at 10:43:12AM +1000, Jason Drage wrote: > > >> You mention that you've moved the guests from one host to another. Are >> both hosts running the same kernel and util-vserver versions? >> > > No, the new host is tracking lenny, the old sarge(backported). > Probably important, that.. > > >> perhaps you could post the output of vserver-info from both hosts. >> > > I've removed lines that are identical from both calls below so we can see the differences.. > Sure. Old host: > > nitrogen:~# vserver-info > Versions: > Kernel: 2.6.18-5-vserver-amd64 > VS-API: 0x00020002 > util-vserver: 0.30.213; Jun 23 2007, 06:49:07 > > Features: > CC: gcc, gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) > CXX: g++, g++ (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) > > Available APIs: compat,v11,fscompat,v13,net,v21,oldproc,olduts > > New host: > > lithium:~# vserver-info > Versions: > Kernel: 2.6.26-1-vserver-amd64 > VS-API: 0x00020303 > util-vserver: 0.30.216-pre2772; Aug 27 2008, 21:40:37 > > Features: > CC: gcc, gcc (Debian 4.3.1-9) 4.3.1 > CXX: g++, g++ (Debian 4.3.1-9) 4.3.1 > > Available APIs: v13,net,v21,v22,v23,netv2 > > crypto api: beecrypt > > There's significant differences in both "VS-API" and "Available APIs" but I can tell if these would cause you problem. A quick search of the linux-vserver site didn't get me any hits. From the symptoms you initially reported it seems as though localhost works fine in the guest on one host but not the other. You can confirm this by repeating your "telnet localhost 25" test on the other machine, if it works on one and not the other you've discovered the difference between the host that is giving you grief. Also the kernel names don't include the vserver patch used. On my servers the kernel version is "2.6.22.18-vs2.3.0.32" which tells me I'm running the development 2.3.0.32 patch (which solved all my localhost woes). Can you please tell us what the lenny and Sarge kernels are patched with? hth, Jason