Subject: Re: [vserver] Conditional start
From: Manfred Heubach <entwicklung@heubach-edv.de>
Date: Tue, 02 Sep 2008 22:44:08 +0200
Tue, 02 Sep 2008 22:44:08 +0200


Herbert Poetzl schrieb:
> On Tue, Sep 02, 2008 at 03:50:46PM +0200, entwicklung@heubach-edv.de wrote:
>   
>> Hi Gilles,
>>
>> I've had the same problem on my testing machine yesterday. Now I
>> should remember how I solved it.
>>
>> There is a thread on Debian Bug Reports about this. The problem may be
>> that your util-vserver is too "old" for the kernel. You have to use
>> the util-vserver from unstable (sid) - they work with lenny too.
>>     
>
> well, "old" might be misleading, but yeah
>
>   
Hey - that's why I used the doublequotes :-)
> you are most likely using the 0.30.216~something,
> with a recent (2.6.25/26) kernel, and unfortunately
> debian picked up a broken pre release of the
> 0.30.216 utils, which causes those issues ...
>
> solution is quite simple, get the recent version
> (either from mainline or from debian) and you should
> be fine
>
> HTH,
> Herbert
>
>   
>> Best regards
>> Manfred
>>
>> I downloaded the
>>     
>>> Hello.
>>>
>>>       
>>>> Any news about this thread?
>>>>         
>>> I was the orignator of this thread. I've just started to experiment with
>>> my
>>> test vserver named "i386" below. And I already got into troubles...
>>>
>>> # vserver i386 start
>>> vc_migrate_context(): Function not implemented
>>> /proc/uptime can not be accessed. Usually, this is caused by
>>> procfs-security. Please read the FAQ for more details
>>> http://linux-vserver.org/Proc-Security
>>>
>>>
>>> Failed to start vserver 'i386'
>>>
>>> [I hadn't tried that recently but I think that that behaviour wasn't there
>>> a few weeks ago.  Also, last time I booted the host system, all vservers
>>> started fine.]
>>>
>>>
>>> # vserver-info
>>> Versions:
>>>                    Kernel: 2.6.25.11-vs2.3.0.34.14+g1
>>>                    VS-API: 0x00020303
>>>              util-vserver: 0.30.215; Aug  1 2008, 13:20:16
>>>
>>> Features:
>>>                        CC: gcc, gcc (Debian 4.3.1-8) 4.3.1
>>>                       CXX: g++, g++ (Debian 4.3.1-8) 4.3.1
>>>                  CPPFLAGS: ''
>>>                    CFLAGS: '-Wall -g  -O2 -std=c99 -Wall -pedantic -W
>>> -funit-at-a-time'
>>>                  CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W
>>> -fmessage-length=0 -funit-at-a-time'
>>>                build/host: x86_64-pc-linux-gnu/x86_64-pc-linux-gnu
>>>              Use dietlibc: yes
>>>        Build C++ programs: yes
>>>        Build C99 programs: yes
>>>            Available APIs: v13,net,v21,v22,v23,netv2
>>>             ext2fs Source: e2fsprogs
>>>     syscall(2) invocation: alternative
>>>       vserver(2) syscall#: 236/glibc
>>>                crypto api: beecrypt
>>>
>>> Paths:
>>>                    prefix: /usr
>>>         sysconf-Directory: /etc
>>>             cfg-Directory: /etc/vservers
>>>          initrd-Directory: $(sysconfdir)/init.d
>>>        pkgstate-Directory: /var/run/vservers
>>>           vserver-Rootdir: /var/lib/vservers
>>>
>>>
>>> Assumed 'SYSINFO' as no other option given; try '--help' for more
>>> information.
>>>
>>>
>>> Best,
>>> Gilles
>>>
>>>       




Herbert Poetzl schrieb:
On Tue, Sep 02, 2008 at 03:50:46PM +0200, entwicklung@heubach-edv.de wrote:
  
Hi Gilles,

I've had the same problem on my testing machine yesterday. Now I
should remember how I solved it.

There is a thread on Debian Bug Reports about this. The problem may be
that your util-vserver is too "old" for the kernel. You have to use
the util-vserver from unstable (sid) - they work with lenny too.
    

well, "old" might be misleading, but yeah

  
Hey - that's why I used the doublequotes :-)
you are most likely using the 0.30.216~something,
with a recent (2.6.25/26) kernel, and unfortunately
debian picked up a broken pre release of the
0.30.216 utils, which causes those issues ...

solution is quite simple, get the recent version
(either from mainline or from debian) and you should
be fine

HTH,
Herbert

  
Best regards
Manfred

I downloaded the
    
Hello.

      
Any news about this thread?
        
I was the orignator of this thread. I've just started to experiment with
my
test vserver named "i386" below. And I already got into troubles...

# vserver i386 start
vc_migrate_context(): Function not implemented
/proc/uptime can not be accessed. Usually, this is caused by
procfs-security. Please read the FAQ for more details
http://linux-vserver.org/Proc-Security


Failed to start vserver 'i386'

[I hadn't tried that recently but I think that that behaviour wasn't there
a few weeks ago.  Also, last time I booted the host system, all vservers
started fine.]


# vserver-info
Versions:
                   Kernel: 2.6.25.11-vs2.3.0.34.14+g1
                   VS-API: 0x00020303
             util-vserver: 0.30.215; Aug  1 2008, 13:20:16

Features:
                       CC: gcc, gcc (Debian 4.3.1-8) 4.3.1
                      CXX: g++, g++ (Debian 4.3.1-8) 4.3.1
                 CPPFLAGS: ''
                   CFLAGS: '-Wall -g  -O2 -std=c99 -Wall -pedantic -W
-funit-at-a-time'
                 CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W
-fmessage-length=0 -funit-at-a-time'
               build/host: x86_64-pc-linux-gnu/x86_64-pc-linux-gnu
             Use dietlibc: yes
       Build C++ programs: yes
       Build C99 programs: yes
           Available APIs: v13,net,v21,v22,v23,netv2
            ext2fs Source: e2fsprogs
    syscall(2) invocation: alternative
      vserver(2) syscall#: 236/glibc
               crypto api: beecrypt

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


Assumed 'SYSINFO' as no other option given; try '--help' for more
information.


Best,
Gilles