-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

reopen #328209
severity #328209 grave
retitle #328209 util-vserver: built with wrong vserver syscall
thanks

Hi,

I found the util-vserver from sarge doesn't work on powerpc as well,
and it works after rebuilt on a patched vserver kernel.

My tests are on an ibook with a fresh installed sarge:
All tests use these scripts:
http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh
http://vserver.13thfloor.at/Stuff/SCRIPT/testfs.sh


#Test1
kernel: 2.6.8-16 (sarge)
vserver-patch: 1.9.5.3 (sarge)
util-vserver: 0.30.204-5sarge2 (sarge)

~# ./testme.sh
Linux-VServer Test [V0.13] Copyright (C) 2003-2005 H.Poetzl
chcontext: vc_new_s_context(): Function not implemented
chcontext failed!
chbind: vc_set_ipv4root(): Function not implemented
chbind failed!
Linux 2.6.8-16+vserver1.9.5.3 ppc/0.30.204/0.30.204 [Ea] (0)
VCI:  0001:0025 257 83000076
- ---
~# vserver-info - SYSINFO
Versions:
                   Kernel: 2.6.8-16+vserver1.9.5.3
                   VS-API: ???
             util-vserver: 0.30.204; May 26 2005, 02:11:52

Features:
                       CC: gcc, gcc (GCC) 3.3.5 (Debian 1:3.3.5-12)
                      CXX: g++, g++ (GCC) 3.3.5 (Debian 1:3.3.5-12)
                 CPPFLAGS: ''
                   CFLAGS: '-Wall -g  -O2 -std=c99 -Wall -pedantic -W'
                 CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W
- -fmessage-length=0'
               build/host:
powerpc-unknown-linux-gnu/powerpc-unknown-linux-gnu
             Use dietlibc: yes
       Build C++ programs: yes
       Build C99 programs: yes
           Available APIs: compat,v11,v13,fscompat,net,oldproc,olduts
            ext2fs Source: e2fsprogs
    syscall(2) invocation: fast
      vserver(2) syscall#: 273/default

Paths:
                   prefix: /usr
        sysconf-Directory: /etc
            cfg-Directory: /etc/vservers
         initrd-Directory: $(sysconfdir)/init.d
       pkgstate-Directory: /var/run/vservers
            Kernelheaders: /usr/include
          vserver-Rootdir: /var/lib/vservers

#Test2
Same kernel-image with test1, but with a rebuilt util-vserver.
kernel: 2.6.8-16 (sarge)
vserver-patch: 1.9.5.3 (sarge)
util-vserver: 0.30.204-5sarge2.local.0 (local rebuilt)


Linux-VServer Test [V0.13] Copyright (C) 2003-2005 H.Poetzl
chcontext is working.
chbind is working.
Linux 2.6.8-16+vserver1.9.5.3 ppc/0.30.204/0.30.204 [Ea] (0)
VCI:  0001:0025 257 83000076
- ---
[000]# succeeded.
[001]# succeeded.
[011]# succeeded.
[031]# succeeded.
[101]# succeeded.
[102]# succeeded.
[201]# succeeded.
[202]# succeeded.
~# ./testme.sh -L
Linux-VServer Test [V0.13] Copyright (C) 2003-2005 H.Poetzl
chcontext is working.
chbind is working.
Linux 2.6.8-16+vserver1.9.5.3 ppc/0.30.204/0.30.204 [Ea] (0)
VCI:  0001:0025 257 83000076
- ---
[000]# succeeded.
[001]# succeeded.
[011]# succeeded.
[031]# succeeded.
[101]# succeeded.
[102]# succeeded.
[201]# succeeded.
[202]# succeeded.
- ---
[L01]# succeeded.
[D01]# succeeded.
[L02]# succeeded.
[D02]# succeeded.
[L03]# succeeded.
[D03]# succeeded.
[L11]# succeeded.
[D11]# succeeded.
[L12]# succeeded.
[D12]# succeeded.
[L21]# succeeded.
[D21]# succeeded.
[L22]# succeeded.
[D22]# succeeded.

Prepare testfs.sh script for checks some filesystem functionality:

~# wget http://vserver.13thfloor.at/Stuff/SCRIPT/testfs.sh
~# chmod +x testfs.sh
~# dd bs=1024k count=1024 if=/dev/zero of=1gb.testfile
~# losetup /dev/loop0 1gb.testfile

Run the testfs.sh script for legacy mode and only test on ext3 filesystem:

~# ./testfs.sh -l -F ext3 -t -D /dev/loop0 -M /mnt
Linux-VServer FS Test [V0.10] Copyright (C) 2005 H.Poetzl
Linux 2.6.8-16+vserver1.9.5.3 ppc/0.30.204
VCI:  0001:0025 257 83000076 (ugid24)
- ---
testing ext3 filesystem ...
[000]. xattr related tests ...
[101]. [102]. [103]* [104]* [106]. [108]. [109]*
[112]. [113]* [114]* [115]. [116]. [117]. [118]. [119]*
[121]* [122]* [123]* [124]* [199].

Lots of errors in legacy mode checks.

Let's run the testfs.sh script for new-style config and only test on ext3
filesystem:

~# ./testfs.sh -F ext3 -t -D /dev/loop0 -M /mnt
Linux-VServer FS Test [V0.10] Copyright (C) 2005 H.Poetzl
Linux 2.6.8-16+vserver1.9.5.3 ppc/0.30.204
VCI:  0001:0025 257 83000076 (ugid24)
- ---
testing ext3 filesystem ...
[000]. xattr related tests ...
[101]. [102]. [103]. [104]. [106]. [108]. [109].
[112]. [113]. [114]. [115]. [116]. [117]. [118]. [119].
[121]. [122]. [123]. [124]. [199].

No error in new-style config, oh ye! :p

Let's see the correct vserver syscall:

~# vserver-info - SYSINFO
Versions:
                   Kernel: 2.6.8-16+vserver1.9.5.3
                   VS-API: 0x00010025
             util-vserver: 0.30.204; Oct 27 2005, 00:01:03

Features:
                       CC: gcc, gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
                      CXX: g++, g++ (GCC) 3.3.5 (Debian 1:3.3.5-13)
                 CPPFLAGS: ''
                   CFLAGS: '-Wall -g  -O2 -std=c99 -Wall -pedantic -W'
                 CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W
- -fmessage-length=0'
               build/host:
powerpc-unknown-linux-gnu/powerpc-unknown-linux-gnu
             Use dietlibc: yes
       Build C++ programs: yes
       Build C99 programs: yes
           Available APIs: compat,v11,v13,fscompat,net,oldproc,olduts
            ext2fs Source: e2fsprogs
    syscall(2) invocation: fast
      vserver(2) syscall#: 257/kernel

Paths:
                   prefix: /usr
        sysconf-Directory: /etc
            cfg-Directory: /etc/vservers
         initrd-Directory: $(sysconfdir)/init.d
       pkgstate-Directory: /var/run/vservers
            Kernelheaders:
/lib/modules/2.6.8-16+vserver1.9.5.3/build/include
          vserver-Rootdir: /var/lib/vservers

My Conclusions are:
1) Builds the util-vserver required a vserver patched kernel
2) Sarge's new-style config support better than legancy mode support
3) legancy mode support is broken in sarge

- -Andrew
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDX7ErnQYz4bYlCYURAmAWAJ0YSUeWUq+koAmkrRyMHyfFUow6jgCfU4nw
6Q958jK6xB6AGJhjsTvpqqk=
=8P7v
-----END PGP SIGNATURE-----



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to